B nv onnkppilw?
Sent from Outlook
On Sun, Jul 12, 2015 at 5:00 AM -0700, <freebsd-stable-request at
freebsd.org> wrote:
Send freebsd-stable mailing list submissions to
freebsd-stable at freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-stable-request at freebsd.org
You can reach the person managing the list at
freebsd-stable-owner at freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. ZFS Woes... Guru needed (Holm Tiffe)
2. Re: ZFS Woes... Guru needed (Bob Bishop)
3. FreeBSD 10.2-BETA1 Now Available (Glen Barber)
4. Re: OFED on stable/9 is not buildable at least on stable/10
(Dmitry Morozovsky)
5. r284665 causes MSI problems -> ahcich2: Timeout in slot 11
port 0 (Harald Schmalzbauer)
6. Re: OFED on stable/9 is not buildable at least on stable/10
(Hans Petter Selasky)
7. Slow frame rate running stable running r285364M with Radeon
3850 (Leonard Rucker)
8. Jenkins build is back to normal : Build-UFS-image #1949
(jenkins-admin at FreeBSD.org)
9. Re: Will 10.2 also ship with a very stale NTP? (Chris Nehren)
10. Re: Will 10.2 also ship with a very stale NTP? (Peter Jeremy)
11. Re: Will 10.2 also ship with a very stale NTP? (Tomoaki AOKI)
12. Re: Will 10.2 also ship with a very stale NTP? (Matt Smith)
13. Re: Will 10.2 also ship with a very stale NTP? (Xin LI)
14. Re: r284665 causes MSI problems -> ahcich2: Timeout in slot
11 port 0 (Edward Tomasz Napiera?a)
15. Re: Will 10.2 also ship with a very stale NTP? (Tomoaki AOKI)
16. Re: r284665 causes MSI problems -> ahcich2: Timeout in slot
11 port 0 (Harald Schmalzbauer)
----------------------------------------------------------------------
Message: 1
Date: Sat, 11 Jul 2015 15:19:21 +0200
From: Holm Tiffe
To: freebsd-stable at freebsd.org
Subject: ZFS Woes... Guru needed
Message-ID: <20150711131921.GA34566 at beast.freibergnet.de>
Content-Type: text/plain; charset=iso-8859-1
Hi Guys,
I have a FreeBSD9.3-stable system with 3x 68GB IBM Disks (Cheeta)
configured wirh gpt and zfs as pool zroot. In the last days one of the
disks was dying and I've disconnected the bad going drive to connect
an other one. The "new" disk is physically identical but replacing the
bad
disk with the new one failed, since the new disk reported only 65 insted of
68GByte free space (other firmware, IBMAS400 in the inquiry string).
So I looked at the bad disks and found one with defective electronics
and one with defective platters and exchanged the controllers (all Disks
are in "real life ST373453LC disks, original with 534 Byte sector size
or so).
I've rebooted the system, set up a camcontrol cmd for changing the sector
size to 512Byte and begun to format the disk with camcontrol format.
While formating for a while the system apniced with an adaptec register
dump and would'nt boot anymore with the infamous "ZFS: i/o error - all
block
copies unavailabe", kernel booted but mountroot failed.
I've found out that I could boot the system when I manually load the zfs.ko
module at the loader prompt.
The filesystem is somewhat broken now, /boot/loader.conf isn't readable and
so are other files, /etc/rc.conf for example, /usr/home is empty.
I've tried to reformat the disk a 2nd time, but it never finished. Tried
the next disk and this worked, tried a replace in the with zpool but I have
an unclear state here:
# zpool status -v
pool: zroot
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: resilvered 42.4G in 1h25m with 2 errors on Sat Jul 11 12:28:53 2015
config:
NAME STATE READ WRITE CKSUM
zroot DEGRADED 0 0 86
raidz1-0 DEGRADED 0 0 344
gpt/disk0 ONLINE 0 0 0
gpt/disk1 ONLINE 0 0 0
replacing-2 DEGRADED 0 0 0
6329731321389372496 OFFLINE 0 0 0 was
/dev/gpt/disk
2/old
gpt/disk2 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
zroot:<0x0>
zroot/var/db:<0x0>
#
I'm unable to remove thedisk with that id 6329731321389372496 and don't
know what replacing-2 could mean at all.
I do have an tar backup from my /home from almost a week ago, but in the
meantime I've done some serious work with Kicad (PCB's) tat I really
don't
want to loose. The Backups from the system itselves are really old...
How can I repair this trouble? Can I get my data back at all?
zpool scrub ran several times, resilvering too. I can't remove that
loader.conf file or others. (cat /etc/rc.conf .. unknown error 122)
I think I need ZFS Guru here...please help..
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741
------------------------------
Message: 2
Date: Sat, 11 Jul 2015 15:00:44 +0100
From: Bob Bishop
To: holm at freibergnet.de
Cc: freebsd-stable at freebsd.org
Subject: Re: ZFS Woes... Guru needed
Message-ID: <3DB65FC2-B614-45E3-AB32-9D3A16E6434E at gid.co.uk>
Content-Type: text/plain; charset=windows-1252
Hi,
> On 11 Jul 2015, at 14:19, Holm Tiffe wrote:
>
> So I looked at the bad disks and found one with defective electronics
> and one with defective platters and exchanged the controllers (all Disks
> are in "real life ST373453LC disks, original with 534 Byte sector size
> or so).
Can?t comment on the ZFS aspects, but I?m not sure you can rely on swapping
drive electronics these days. I believe that in at least some cases boards are
parameterised for the particular platters and heads during production.
--
Bob Bishop
rb at gid.co.uk
------------------------------
Message: 3
Date: Sat, 11 Jul 2015 16:38:23 +0000
From: Glen Barber
To: freebsd-stable at FreeBSD.org
Cc: FreeBSD Release Engineering Team
Subject: FreeBSD 10.2-BETA1 Now Available
Message-ID: <20150711163823.GA40083 at FreeBSD.org>
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The first BETA build of the 10.2-RELEASE release cycle is now available.
Installation images are available for:
o amd64 GENERIC
o i386 GENERIC
o ia64 GENERIC
o powerpc GENERIC
o powerpc64 GENERIC64
o sparc64 GENERIC
o armv6 BEAGLEBONE
o armv6 CUBOX-HUMMINGBOARD
o armv6 RPI-B
o armv6 WANDBOARD
Installer images and memory stick images are available here:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/
The image checksums follow at the end of this email.
If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.
If you would like to use SVN to do a source based update of an existing
system, use the "stable/10" branch.
A list of changes since 10.1-RELEASE are available on the stable/10
release notes:
https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html
Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 10.2-RELEASE cycle progresses.
=== Virtual Machine Disk Images ==
VM disk images are available for the amd64 and i386 architectures.
Disk images may be downloaded from the following URL (or any of the
FreeBSD FTP mirrors):
ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-BETA1/
The partition layout is:
~ 512k - freebsd-boot GPT partition type (bootfs GPT label)
~ 1GB - freebsd-swap GPT partition type (swapfs GPT label)
~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label)
The disk images are available in QCOW2, VMDK, and raw disk image formats
The image download size is approximately 135 MB, which decompress to a
20GB sparse image.
Note: A last-minute issue was discovered with the VHD-formatted images,
and they have been pulled from the mirrors as a result.
=== Amazon EC2 AMI Images ==
FreeBSD/amd64 EC2 AMIs are available in the following regions:
us-east-1 region: ami-df1dd5b4
us-west-1 region: ami-8f8b78cb
us-west-2 region: ami-61a6a651
sa-east-1 region: ami-d7a62aca
eu-west-1 region: ami-18f1bc6f
eu-central-1 region: ami-e8211bf5
ap-northeast-1 region: ami-a0d67fa0
ap-southeast-1 region: ami-02f3f350
ap-southeast-2 region: ami-712c6b4b
=== Azure / VM Depot Images ==
FreeBSD/amd64 images are available for use within the Microsoft Azure
hosting platform through VM Depot. For deployment instructions, see:
https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718&version=59022
=== Vagrant Images ==
FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:
% vagrant init freebsd/FreeBSD-10.2-BETA1
% vagrant up --provider vmware_desktop
Note: At this time, support exists only for the vmware_desktop
provider.
=== Upgrading ==
The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases. Systems running earlier
FreeBSD releases can upgrade as follows:
# freebsd-update upgrade -r 10.2-BETA1
During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before
continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:
# freebsd-update install
It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 9.x. Alternatively, the user can install misc/compat9x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:
# shutdown -r now
Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:
# freebsd-update install
== ISO CHECKSUMS =
o 10.2-BETA1 amd64 GENERIC:
SHA256 (FreeBSD-10.2-BETA1-amd64-bootonly.iso) =
36e01ce780a777f4cfd091f10572dfa0d2af2d0e076d1dec13dacc1db7465f67
SHA256 (FreeBSD-10.2-BETA1-amd64-bootonly.iso.xz) =
12bcee785d24d04ee919e5848b491ad56064c5f18f4bda102ab1436e8f13902d
SHA256 (FreeBSD-10.2-BETA1-amd64-disc1.iso) =
be2db9c92da93b4b0d810b081e29efbc8f119a8cb1032393fe8215d6288d2071
SHA256 (FreeBSD-10.2-BETA1-amd64-disc1.iso.xz) =
299a6f79f4f83819cb68016bc85365d6c8e306945eca558a3845ab5148575053
SHA256 (FreeBSD-10.2-BETA1-amd64-dvd1.iso) =
55f74425f78e7fd4ece91ce0af22e7dfab74a7e7fa6063d0329256fe06b213bf
SHA256 (FreeBSD-10.2-BETA1-amd64-dvd1.iso.xz) =
1edbbc8e59a2ad717141e24a59e50866c0990a2aa1f41b59f6ad340924f97894
SHA256 (FreeBSD-10.2-BETA1-amd64-memstick.img) =
d47e5d59dc8b212b11483992bc46534b474627e10e89bbce69460df45da3cd5e
SHA256 (FreeBSD-10.2-BETA1-amd64-memstick.img.xz) =
97beb17192a2f99bd9efd5d60128adc13f757ba7fefc990cc79a3246ce4fdd71
SHA256 (FreeBSD-10.2-BETA1-amd64-mini-memstick.img) =
4ecdc7d0ab0af91d2864703179c5b1722bb4528a8cdbf13158478e29b98702ec
SHA256 (FreeBSD-10.2-BETA1-amd64-mini-memstick.img.xz) =
090f91a4a731d8a0f784f7ccc4d075506f29961040a4eb2ce990b4d9efe3063a
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-bootonly.iso) =
9c062b8d1b837bc8d745777020f429fe811c720d67cde36cfc10e955c4e03e3f
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-bootonly.iso.xz) =
528b766632e7af2725adf2cb83d5228f90edfbdd2008789c284486b110f9d7aa
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-disc1.iso) =
03b7c86e2643528c531a01659769724a13b74b896156166becf65ee002650044
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-disc1.iso.xz) =
356514a651208ab342fd2d5ab998190fd3a0a887ab108f38018f86327069b042
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-dvd1.iso) =
e69ac074ede17c0b6c40d26c4a90b18b1a723c3d4a278aae07252dbbd82fe3fd
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-dvd1.iso.xz) =
4d0bbba475c76bbfa4b47ad8ea5fd2333c848217bcfee52d2f9d330125040e9f
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-memstick.img) =
edc386b172d672e4cd583547f88ea134919151f95c84ebdb3940f3ec82fb2a37
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-memstick.img.xz) =
60c7e9f9656f3490bb511720233628a5fd9f7b0a92dc572a90120c80c906bbf5
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-mini-memstick.img) =
64cc9f67af6aa060d2f8e739614265a913a44d1c466f8506d436ab24131eee45
SHA256 (FreeBSD-10.2-BETA1-amd64-uefi-mini-memstick.img.xz) =
e352fe4ffbf4ebcc25e34bb3059c1114891012b42712969484995112506d377e
MD5 (FreeBSD-10.2-BETA1-amd64-bootonly.iso) =
c49b0602c9bfcb520b29e93a29112fd2
MD5 (FreeBSD-10.2-BETA1-amd64-bootonly.iso.xz) =
c5f3fd678769445287f058b3675c4a9c
MD5 (FreeBSD-10.2-BETA1-amd64-disc1.iso) =
f3d393a44d602ea596123d3dcdd17f83
MD5 (FreeBSD-10.2-BETA1-amd64-disc1.iso.xz) =
e7e2c9c3e49fb4d975c612c26f95cb2b
MD5 (FreeBSD-10.2-BETA1-amd64-dvd1.iso) =
98b33ec03897b5a2fc4502f05e833169
MD5 (FreeBSD-10.2-BETA1-amd64-dvd1.iso.xz) =
5ee352dfc039e946aa72ee425dc87e65
MD5 (FreeBSD-10.2-BETA1-amd64-memstick.img) =
819a5b3af2113ce77ec2c5ef34b7f34c
MD5 (FreeBSD-10.2-BETA1-amd64-memstick.img.xz) =
2e563503544e4b0edb7d8dabd219e32c
MD5 (FreeBSD-10.2-BETA1-amd64-mini-memstick.img) =
9e5a752df2e0b62a599fa96b89d148c5
MD5 (FreeBSD-10.2-BETA1-amd64-mini-memstick.img.xz) =
9715624eeaa3108be094b5bdffa4c397
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-bootonly.iso) =
2676877b5257b159cae5050ea45b4e54
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-bootonly.iso.xz) =
d7e1c53be1d2aef657d2f697dd0086dc
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-disc1.iso) =
72fdf6409aee71f1d7c423cea5b02550
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-disc1.iso.xz) =
8ea00f4cd59c1670fc3d4e3059164228
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-dvd1.iso) =
dd4a3269d7c30221e84161fcee270506
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-dvd1.iso.xz) =
2fb7387f614760d2448b6f51bc7d4b22
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-memstick.img) =
e879344dd567d290f1d24acdb7f916fc
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-memstick.img.xz) =
fa94d03eb74dad5ab0dd22b30878a39a
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-mini-memstick.img) =
8e565532849cdd309895b3f556a4dca5
MD5 (FreeBSD-10.2-BETA1-amd64-uefi-mini-memstick.img.xz) =
9c2916ccc62563db22e1996a83aeb422
o 10.2-BETA1 i386 GENERIC:
SHA256 (FreeBSD-10.2-BETA1-i386-bootonly.iso) =
dbd13d3b522a423e12bc06bedbd90966abe6befa75b047c04f592e930d4fe4ce
SHA256 (FreeBSD-10.2-BETA1-i386-bootonly.iso.xz) =
4e35a4d5eaf4965d7fc2c5a7a762b1abfcb6d9cca39ff8a37345987014326c11
SHA256 (FreeBSD-10.2-BETA1-i386-disc1.iso) =
490421a74839655bb50dad98aa1bb8daaa7106cfddb3747fe439a1ec5d7aace3
SHA256 (FreeBSD-10.2-BETA1-i386-disc1.iso.xz) =
f36904198ecc509198ece7d650fc45608f17dbfc67e6d49357ab5f99469896b7
SHA256 (FreeBSD-10.2-BETA1-i386-dvd1.iso) =
62d40fd780aafa77b60563161ca2370bc91fc169502e065733537b5cc11132ed
SHA256 (FreeBSD-10.2-BETA1-i386-dvd1.iso.xz) =
ed8b7506f610da86c9784ecd33fcfbf02540efa3cd6eafdc843e3cca0cbbc26e
SHA256 (FreeBSD-10.2-BETA1-i386-memstick.img) =
40368508862db73f77eb917f84802c1559167a2b89bf97fa1862afc3db7af555
SHA256 (FreeBSD-10.2-BETA1-i386-memstick.img.xz) =
daae34c2a9b5b22e1ccc25b0a3b8c59659ec9fc3f6db6c87068792e7763395a3
SHA256 (FreeBSD-10.2-BETA1-i386-mini-memstick.img) =
860f925de67bbd36a336fd36438f9f3be1407b66eb71a0520fa4172a684c9a06
SHA256 (FreeBSD-10.2-BETA1-i386-mini-memstick.img.xz) =
f279639f35ffe3b300632e8388918c52dfdbccafee54be87c6a3de1e598052c5
MD5 (FreeBSD-10.2-BETA1-i386-bootonly.iso) =
94690c4a5334efbebfa666880a6a306c
MD5 (FreeBSD-10.2-BETA1-i386-bootonly.iso.xz) =
ae21b2ac1c1714c411223ab9aa6734e8
MD5 (FreeBSD-10.2-BETA1-i386-disc1.iso) =
83ff9892583fa50dbee6f87c6e2c498b
MD5 (FreeBSD-10.2-BETA1-i386-disc1.iso.xz) =
10dbf578fa3a76fad6cd6db687374ca9
MD5 (FreeBSD-10.2-BETA1-i386-dvd1.iso) =
27f5a9611534d551b185386d0beab5a0
MD5 (FreeBSD-10.2-BETA1-i386-dvd1.iso.xz) =
e26e707ac354746c20f0e8c064a4475a
MD5 (FreeBSD-10.2-BETA1-i386-memstick.img) =
b84dafcd06dcc9c29d947f05056beca5
MD5 (FreeBSD-10.2-BETA1-i386-memstick.img.xz) =
f3a263b69fcd25c7ca93acb461cdbbac
MD5 (FreeBSD-10.2-BETA1-i386-mini-memstick.img) =
c09a3487fa0b278894717ec2e3809336
MD5 (FreeBSD-10.2-BETA1-i386-mini-memstick.img.xz) =
e76293d37eb22e32badf9ed6fc6d8dd7
o 10.2-BETA1 ia64 GENERIC:
SHA256 (FreeBSD-10.2-BETA1-ia64-bootonly.iso) =
99350b651990921958d50769834c3ae894b73fa5d911b35f6f4c1eddc27141f2
SHA256 (FreeBSD-10.2-BETA1-ia64-bootonly.iso.xz) =
709f2b13504af125437a09e595d536b2dd7ec8303346fda811e299cee2028e48
SHA256 (FreeBSD-10.2-BETA1-ia64-disc1.iso) =
a453842983cf364a37801595f240d6229c5997df01fff702ac8cdfb1a7aa9217
SHA256 (FreeBSD-10.2-BETA1-ia64-disc1.iso.xz) =
54f00ee13398b8c0714aa0ce55a77caa989e3f27ea9cfd77e594aec06b7c35fb
SHA256 (FreeBSD-10.2-BETA1-ia64-dvd1.iso) =
507a111f7ee405a462351d02f17062e0731f57ba64792f745e09494e20ce78b5
SHA256 (FreeBSD-10.2-BETA1-ia64-dvd1.iso.xz) =
d5916133db7011e868965ae767bcc914416b8b2f7b3ce4416d1859123439d148
SHA256 (FreeBSD-10.2-BETA1-ia64-memstick.img) =
01d51f8180c2a5471da8e47ed1a488e159b062265ea515433137ba899f90bcd8
SHA256 (FreeBSD-10.2-BETA1-ia64-memstick.img.xz) =
07a732f2ca78bfca11b95df6c9d20b0cc818142793cf8872131dd27ad9e10ef8
SHA256 (FreeBSD-10.2-BETA1-ia64-mini-memstick.img) =
492636c8ec8a7ec746d05a5692f8e0145307a307ed4aa9b8d8eb9a93998d539b
SHA256 (FreeBSD-10.2-BETA1-ia64-mini-memstick.img.xz) =
6475a09266914e1cd454d97adcfd8bbfefe448fa4cc98e068c0baf322afc9d3d
MD5 (FreeBSD-10.2-BETA1-ia64-bootonly.iso) =
1c87b94cae188f610e316ac4813b1df9
MD5 (FreeBSD-10.2-BETA1-ia64-bootonly.iso.xz) =
e41f0ffea201c084fb4f6c874edc7c5a
MD5 (FreeBSD-10.2-BETA1-ia64-disc1.iso) =
5891e5ee42a125220bc2db270d47c2b7
MD5 (FreeBSD-10.2-BETA1-ia64-disc1.iso.xz) =
e10fc71df8a0355b0e8727654f7d99af
MD5 (FreeBSD-10.2-BETA1-ia64-dvd1.iso) =
1fc33ba2d6d6704ec775a32cb7d6b053
MD5 (FreeBSD-10.2-BETA1-ia64-dvd1.iso.xz) =
ef4c4f355b039445a58fd8de2e6493c9
MD5 (FreeBSD-10.2-BETA1-ia64-memstick.img) =
4008508c9834814b83a43e606a2b68b5
MD5 (FreeBSD-10.2-BETA1-ia64-memstick.img.xz) =
71a011732e0109f3d38c972faecba492
MD5 (FreeBSD-10.2-BETA1-ia64-mini-memstick.img) =
e8c3b613141c4dcc0ed64afd645ebc4e
MD5 (FreeBSD-10.2-BETA1-ia64-mini-memstick.img.xz) =
a2dc3b38325be4717db78ce8a5a2a900
o 10.2-BETA1 powerpc GENERIC:
SHA256 (FreeBSD-10.2-BETA1-powerpc-bootonly.iso) =
10af9c9c5350781c66572550e6a52e641fd387f76c2c4803984b215e44499efa
SHA256 (FreeBSD-10.2-BETA1-powerpc-bootonly.iso.xz) =
cf4806d19d920dfda14f50875012bfaafd7c94761471e8a60e0d7c76c082c3ef
SHA256 (FreeBSD-10.2-BETA1-powerpc-disc1.iso) =
75868200a517dfd3eba43c609a740c6734284139ac3fcbfe6159de5eec19df14
SHA256 (FreeBSD-10.2-BETA1-powerpc-disc1.iso.xz) =
db12d5bb51df9bd8f2e09a739b4d1ba08d532539427ba2eeab60d96a30fa7239
SHA256 (FreeBSD-10.2-BETA1-powerpc-dvd1.iso) =
0bf86f7c6d480fc4c4d95c667fdff2a8f1f727e68f362e94fae879442414b9cf
SHA256 (FreeBSD-10.2-BETA1-powerpc-dvd1.iso.xz) =
543f0bde3432fe260b6d2713c95c3195896d692276790eda1749aaf3b7aecb70
SHA256 (FreeBSD-10.2-BETA1-powerpc-memstick.img) =
d07590356f2eb124e8c20cdadbbca15e708e905df0854b01ded3be40e4bd184b
SHA256 (FreeBSD-10.2-BETA1-powerpc-memstick.img.xz) =
1b1bfb90b076909c1590587fa64fe44635d8f23d4a978b7d1f5eef68dfbc4ad4
SHA256 (FreeBSD-10.2-BETA1-powerpc-mini-memstick.img) =
1419fbd3992fbb1ef2406f835a694d09892e7147cd87f81ed0e21a1bc583998c
SHA256 (FreeBSD-10.2-BETA1-powerpc-mini-memstick.img.xz) =
04f42b08dcfa884db5afb14e50adcb092cf379ecb4169c065667dab33c1e1795
MD5 (FreeBSD-10.2-BETA1-powerpc-bootonly.iso) =
5c74a4836e8eb1720e7c743fef01fee2
MD5 (FreeBSD-10.2-BETA1-powerpc-bootonly.iso.xz) =
eee5d7391978931d6dca2d7c91a45f57
MD5 (FreeBSD-10.2-BETA1-powerpc-disc1.iso) =
a00acf359f8620384939f592cbb655ca
MD5 (FreeBSD-10.2-BETA1-powerpc-disc1.iso.xz) =
4c9af65a61fb3a68ec747360431319d2
MD5 (FreeBSD-10.2-BETA1-powerpc-dvd1.iso) =
ac573bc4d717fc2eae2ab91c5e11e95a
MD5 (FreeBSD-10.2-BETA1-powerpc-dvd1.iso.xz) =
18a5a3ab22a7b2945ef99c97a5de4989
MD5 (FreeBSD-10.2-BETA1-powerpc-memstick.img) =
21f5bff7606f87493bf4c023b31ff561
MD5 (FreeBSD-10.2-BETA1-powerpc-memstick.img.xz) =
d2307ae8cd0938007924c0927e210873
MD5 (FreeBSD-10.2-BETA1-powerpc-mini-memstick.img) =
da5bb9db81abdcdf19132035bacf5e3e
MD5 (FreeBSD-10.2-BETA1-powerpc-mini-memstick.img.xz) =
9e43e4cd86f4cd1c3c4a4b27f5deada2
o 10.2-BETA1 powerpc64 GENERIC64:
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-bootonly.iso) =
4580c320c0d584eead2a2ec9bce558477f04d5d659ed2bbba273c0cae9b0ab42
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-bootonly.iso.xz) =
0507c8371b9617121b1c24e3c2e03ee6dc95e27e892cff7fc121854475bfab8b
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-disc1.iso) =
d538d84af9a669e9df78b43dedaca10e8fe93af0c69a93c83bc4f378bbf1d2b0
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-disc1.iso.xz) =
145e89f90fef5423e0226a50a4148efd2690fc343cccfb772fd189661893151c
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-dvd1.iso) =
8df562f90293420f887aabc77cacf977637f6c340e76c646ddfbf33241c3c5fd
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-dvd1.iso.xz) =
5da9daa4728f7d7dcab8111874f6960f502c15bc2acf4829b4ede424494dd943
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-memstick.img) =
e4fdc1fd9786f43f747bceb27db59c241689933d90f711806e9e39fb83680958
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-memstick.img.xz) =
6ef87a8da98ce9f5586f6f46d76123123d585682f8b2a7cbe62153a7809a61b1
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-mini-memstick.img) =
c12db6c8dfa86a749b5337019e6bea1597a9cf372a19f7f3319b53a137479924
SHA256 (FreeBSD-10.2-BETA1-powerpc-powerpc64-mini-memstick.img.xz) =
ee65d328d3d0fcd912db9b5739be2b97ea23fabc277b6973bb9eac00018bc173
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-bootonly.iso) =
aad91ccddc95d691e1a97becab88e054
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-bootonly.iso.xz) =
4df1814ccc6e1e2001e591e6c97a4606
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-disc1.iso) =
67ca3f8f216be72cbfcc34e24702daa0
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-disc1.iso.xz) =
d1b1f280b61f5e4f66d2b19be1dd16f8
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-dvd1.iso) =
c5fc5767558f55e0a1fdbc62ecf1fd11
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-dvd1.iso.xz) =
694aa938920ac912ad2aa75f20e8e62c
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-memstick.img) =
7075f70552e79e0043df20cc4755d02f
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-memstick.img.xz) =
ef919fd959bf6d6de1346f2eeaa13f74
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-mini-memstick.img) =
4f37e03151bc7c287f1d1a1355893c12
MD5 (FreeBSD-10.2-BETA1-powerpc-powerpc64-mini-memstick.img.xz) =
77b18c67daf7c3ff7690e2c7629e1fe9
o 10.2-BETA1 sparc64 GENERIC:
SHA256 (FreeBSD-10.2-BETA1-sparc64-bootonly.iso) =
011a30bd319ab36693dcb7ef40c1390678e11addfcf24f65e8787e06d016ae66
SHA256 (FreeBSD-10.2-BETA1-sparc64-bootonly.iso.xz) =
c4ba3d24cd605747afb986abeaf45ea1d2a82bddcb195e2951e60d7c1126ccb4
SHA256 (FreeBSD-10.2-BETA1-sparc64-disc1.iso) =
c47e5e4adc27cd5cfbce7c317998671c82e86ae8538a2355737df6d6b79b8cfb
SHA256 (FreeBSD-10.2-BETA1-sparc64-disc1.iso.xz) =
95fe22d8e933361c52c115d16cb5434d1c56b8d6d6522a255d2b083ee106c395
SHA256 (FreeBSD-10.2-BETA1-sparc64-dvd1.iso) =
2a3f3893d54738fa8b80be58542c43fdf8edf51ceb9fc914c7559358e3d08406
SHA256 (FreeBSD-10.2-BETA1-sparc64-dvd1.iso.xz) =
62e66b88fad0621d2e39875611d5f4c0f74654d5e8e3a7193d9dc8d4942f74d3
MD5 (FreeBSD-10.2-BETA1-sparc64-bootonly.iso) =
9e6ba9f447b17d89734619ef30fa563a
MD5 (FreeBSD-10.2-BETA1-sparc64-bootonly.iso.xz) =
017ac59ae281d41d12ee49e8ee21d7f4
MD5 (FreeBSD-10.2-BETA1-sparc64-disc1.iso) =
4e34af86e3516ab058285cfe529cf2d4
MD5 (FreeBSD-10.2-BETA1-sparc64-disc1.iso.xz) =
9e457a422622c58542a73f3ebb6cc941
MD5 (FreeBSD-10.2-BETA1-sparc64-dvd1.iso) =
88d99d54946605459b48bfb01f2611a8
MD5 (FreeBSD-10.2-BETA1-sparc64-dvd1.iso.xz) =
ee4e02a0b12eb95d67de8dd4e943fe57
o 10.2-BETA1 armv6 BEAGLEBONE:
SHA256 (FreeBSD-10.2-BETA1-arm-armv6-BEAGLEBONE.img.xz) =
fbd487fdee1d1a9a23b56ea624c318343654c1435b4e7871904bfb6e0dc088ac
MD5 (FreeBSD-10.2-BETA1-arm-armv6-BEAGLEBONE.img.xz) =
6562c862f9de6598bb4df750a8aa5aa3
o 10.2-BETA1 armv6 CUBOX-HUMMINGBOARD:
SHA256 (FreeBSD-10.2-BETA1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) =
d746e6a588f3bede70860d9ea32732abe6041b3ef5d8c96771264cb1ecb825c2
MD5 (FreeBSD-10.2-BETA1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) =
b52ceddeb23428e3d9cd5c177593aaf7
o 10.2-BETA1 armv6 RPI-B:
SHA256 (FreeBSD-10.2-BETA1-arm-armv6-RPI-B.img.xz) =
4ca806f269819376e6bb773d7bb86cc4d772dc3b1073463c79d2f7f5ed65ec58
MD5 (FreeBSD-10.2-BETA1-arm-armv6-RPI-B.img.xz) =
a4b4a89237777aa61c7e04dc9fed7cb7
o 10.2-BETA1 armv6 WANDBOARD:
SHA256 (FreeBSD-10.2-BETA1-arm-armv6-WANDBOARD.img.xz) =
408dcd8b40c118476199e52519dbc2bbd6abc305b878284577aedb42bc65a1c2
MD5 (FreeBSD-10.2-BETA1-arm-armv6-WANDBOARD.img.xz) =
0e5c03eb0629996b79cd02e1352594ba
== VM IMAGE CHECKSUMS =
o 10.2-BETA1 amd64:
SHA256 (FreeBSD-10.2-BETA1-amd64.qcow2.xz) =
6ba7367a56dd66b60a0563d07ec7ad80b27954cca694183cecd5272771876849
SHA256 (FreeBSD-10.2-BETA1-amd64.raw.xz) =
ee471f7b7e34b8e5c2cb54f173b408d829757cfdc54b67506cbecf930648c9bd
SHA256 (FreeBSD-10.2-BETA1-amd64.vmdk.xz) =
103c789737d0435eea3c9378899320079c1ff4780e794f288902ff6c462e5fc2
MD5 (FreeBSD-10.2-BETA1-amd64.qcow2.xz) =
a496f2a7b0bc554a46ff76d7bdde428b
MD5 (FreeBSD-10.2-BETA1-amd64.raw.xz) = 60ce5de492184aeb09601a24b9f15168
MD5 (FreeBSD-10.2-BETA1-amd64.vmdk.xz) =
fa02af9f3cc7161fcb41e74d404acf74
o 10.2-BETA1 i386:
SHA256 (FreeBSD-10.2-BETA1-i386.qcow2.xz) =
510e9182606fcf1d61c4c269b5dab5f14b25e7eb6d3374cb66c87b1c9b825727
SHA256 (FreeBSD-10.2-BETA1-i386.raw.xz) =
5d3fe3a5676caffce6f0b8ff81865c4c2435c63867c58befa7365b01c54b7190
SHA256 (FreeBSD-10.2-BETA1-i386.vmdk.xz) =
b919761d1d3dfd8c19375d14caf1847b5f2846d26ee521dd7c006f1a1d08331e
MD5 (FreeBSD-10.2-BETA1-i386.qcow2.xz) =
a76d12da373543b90c137367cd3fa909
MD5 (FreeBSD-10.2-BETA1-i386.raw.xz) = bcf5c865ffdbb6cb029f48a6042e563b
MD5 (FreeBSD-10.2-BETA1-i386.vmdk.xz) = d1889f6dc022987c47df2ef5fd967ba1
Regards,
Glen
Love FreeBSD? Support this and future releases with a donation to
the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVoUZ/AAoJEAMUWKVHj+KT4BUQAJiEX9dME51LReWesp0BS0Nb
iwRxWPDNGwme7BDSiyD0RjCRjTMxc0EaniNFFkExMpKJTmH1DHa7+jmg5RmrSrSP
8L8j5pdUOnVU723YqP1ixh3fMeVZ+i+zEpRI9k6B6q6t2+/IZ+LPjsAYgcY2/wav
kIMUP1MZEAEeeb23tTRmvsQtwP9TPP6FiYgFSLPRYFxgbCPcaX90B5Y8rOYACmGM
vlhOEDHZiTi+dZ3HwY3fHYqsHsf4OSqGnsm9FCyVW1XBYe6+7yNVfu9VAf/uB289
VBAJr3YKe5bSMGc31aIARV8eL13cOJtyhZx0JV3oXrySm/ssUqDxSJ9ANRPaJDJy
CAH0Rx3WGhPUR0bfAq/bIU7d06UwToSJLdQBKs5ZPkZA6/8Qy3/DFKjQPN/SHLTK
YiMkKyUNHEzEgh9euRkSoL0PHmEzJdQDY89y+ovkoL2cBz8HJ8+cILP/44QPAxFP
WFYtmGiS0g+iwpnz1jBd8wkLnscqz9Aqr1yZP5k37dVCX/wFycDiCPbD4i6/zlDM
BB+LbX4N/fkr4EZY3fbY13Hh2NV4QWA4G57tQfBGhlr/MCfR70ERaBF0pkSGzdSt
xz/D7qgNDu1XRXQ24/EG+4U6hogRUz50iFzCrFRTSSFizcx0FKiKS3TE4Q9tuHVu
4ljz4OYuKZGIhPkemLFb
=Hvv+
-----END PGP SIGNATURE-----
------------------------------
Message: 4
Date: Sat, 11 Jul 2015 20:14:24 +0300 (MSK)
From: Dmitry Morozovsky
To: Hans Petter Selasky
Cc: freebsd-stable at freebsd.org
Subject: Re: OFED on stable/9 is not buildable at least on stable/10
Message-ID:
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hans Petter,
On Sat, 4 Jul 2015, Dmitry Morozovsky wrote:
> > > on stable/10 trying to buildkernel with ALL_MODULES chokes at
OFED
> > > (actually,
> > > for quite a few months already):
> > >
> > > Could you please take a look at this?
> >
> > Does this patch fix the problem for you:
> >
> > https://svnweb.freebsd.org/changeset/base/285088
>
> yes it does, thank you!
could you please MFC this small change to reduce burden of local patches a bit?
:)
Thans!
--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: marck at FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------
------------------------------
Message: 5
Date: Sat, 11 Jul 2015 19:56:49 +0200
From: Harald Schmalzbauer
To: freebsd-stable at freebsd.org
Cc: Edward Tomasz Napiera?a , kib at freebsd.org
Subject: r284665 causes MSI problems -> ahcich2: Timeout in slot 11
port 0
Message-ID: <55A158E1.3000905 at omnilan.de>
Content-Type: text/plain; charset="utf-8"
Hello,
r284665 causes ahci(4) to fail with timeouts when using MSI (the default).
'hint.ahci.0.msi=0' is one way to make ahci(4) working with r284665, but
obviously not the desired solution, it just disables usage of an MSI.
I can't find suspicious code in r282213 which could cause this strange
regression, but I verified carefully that problem arises with r284665.
Actually, r282901
(https://svnweb.freebsd.org/base?view=revision&sortby=date&revision=282901)
is the real trigger, verified by putting
nooptions RACCT
nooptions RACCT_DEFAULT_TO_DISABLED
nooptions RCTL
into my kernel config -> problem vanishes!
Setting "kern.racct.enable=1" doesn't make any difference, as soon
as
'kern.features.racct' exists, there's the ahci(4)/ahcich2 timeout
and
machine doesn't finish booting.
Unfortunately, I don't have any idea how to track this down to the
actual culprit, but I hope the RACCT hackers do have ;-)
Shall I open a bugzilla ticket?
Thanks,
-Harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL:
------------------------------
Message: 6
Date: Sun, 12 Jul 2015 00:01:15 +0200
From: Hans Petter Selasky
To: Dmitry Morozovsky
Cc: freebsd-stable at freebsd.org
Subject: Re: OFED on stable/9 is not buildable at least on stable/10
Message-ID: <55A1922B.60500 at selasky.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 07/11/15 19:14, Dmitry Morozovsky wrote:> Hans Petter,
>
> On Sat, 4 Jul 2015, Dmitry Morozovsky wrote:
>
>>>> on stable/10 trying to buildkernel with ALL_MODULES chokes at
OFED
>>>> (actually,
>>>> for quite a few months already):
>>>>
>>>> Could you please take a look at this?
>>>
>>> Does this patch fix the problem for you:
>>>
>>> https://svnweb.freebsd.org/changeset/base/285088
>>
>> yes it does, thank you!
>
> could you please MFC this small change to reduce burden of local patches a
bit? :)
>
Here you go:
https://svnweb.freebsd.org/changeset/base/285410
--HPS
------------------------------
Message: 7
Date: Sat, 11 Jul 2015 22:08:55 +0000
From: Leonard Rucker
To: freebsd-stable at freebsd.org
Subject: Slow frame rate running stable running r285364M with Radeon
3850
Message-ID:
Content-Type: text/plain; charset=UTF-8
Hi,
I am running stable on a HTPC and I was running 10.1 with no problems the
frame rate was around 28-30 fps. I updated to 10.2 and now the frame rate
went down to 10-12 fps.
uname -a
FreeBSD mediamaster 10.2-BETA1 FreeBSD 10.2-BETA1 #1 r285364M: Fri Jul 10
20:01:48 PDT 2015 root at FileKeeper:/usr/obj/usr/src/sys/MEDIAMASTER
amd64
Has anyone else seen this?
------------------------------
Message: 8
Date: Sat, 11 Jul 2015 23:53:37 +0000 (GMT)
From: jenkins-admin at FreeBSD.org
To: freebsd-stable at freebsd.org, lwhsu at FreeBSD.org
Subject: Jenkins build is back to normal : Build-UFS-image #1949
Message-ID:
<1862359418.16.1436658817077.JavaMail.jenkins at jenkins-9.freebsd.org>
Content-Type: text/plain; charset=UTF-8
See
------------------------------
Message: 9
Date: Sat, 11 Jul 2015 23:22:56 -0400
From: Chris Nehren
To: freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID: <20150712032256.GB19305 at satori.lan>
Content-Type: text/plain; charset=us-ascii
On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall
wrote:> It's me again with my annual NTP whinge.
The answer to the perennial "will release $foo ship with old / insecure
/ otherwise deficient $bar?" is still "install $bar from ports".
--
Chris Nehren
------------------------------
Message: 10
Date: Sun, 12 Jul 2015 15:04:43 +1000
From: Peter Jeremy
To: freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID: <20150712050443.GA22240 at server.rulingia.com>
Content-Type: text/plain; charset="us-ascii"
On 2015-Jul-11 23:22:56 -0400, Chris Nehren wrote:>On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
>> It's me again with my annual NTP whinge.
>
>The answer to the perennial "will release $foo ship with old / insecure
>/ otherwise deficient $bar?" is still "install $bar from
ports".
That's a non-answer. It just changes the question to "why bother to
include $bar in base when I need to install the port anyway".
--
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL:
------------------------------
Message: 11
Date: Sun, 12 Jul 2015 15:44:16 +0900
From: Tomoaki AOKI
To: freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID: <20150712154416.b9f3713893fe28bfab1dd4d7 at dec.sakura.ne.jp>
Content-Type: text/plain; charset=US-ASCII
As I already mentioned in another post, head has 4.2.8 p3 in-tree.
So the answer should be MFC before creation of releng/10.2 is planned
or not.
On Sun, 12 Jul 2015 15:04:43 +1000
Peter Jeremy wrote:
> On 2015-Jul-11 23:22:56 -0400, Chris Nehren wrote:
> >On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
> >> It's me again with my annual NTP whinge.
> >
> >The answer to the perennial "will release $foo ship with old /
insecure
> >/ otherwise deficient $bar?" is still "install $bar from
ports".
>
> That's a non-answer. It just changes the question to "why bother
to
> include $bar in base when I need to install the port anyway".
>
> --
> Peter Jeremy
--
Tomoaki AOKI junchoon at dec.sakura.ne.jp
------------------------------
Message: 12
Date: Sun, 12 Jul 2015 09:54:51 +0100
From: Matt Smith
To: freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID: <20150712085451.GA1284 at xtaz.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
On Jul 11 23:22, Chris Nehren wrote:>On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
>> It's me again with my annual NTP whinge.
>
>The answer to the perennial "will release $foo ship with old / insecure
>/ otherwise deficient $bar?" is still "install $bar from
ports".
>
I completely agree with this, however my NTP whinge is that the NTP port
needs to have its own RC init script that is independant of the base. If
you use WITHOUT_NTP=yes in /etc/src.conf to remove the base version and
just use the port then there is no RC script. You have to copy the
version from /usr/src/etc/rc.d/ntp into /usr/local/etc/rc.d. This should
be fixed. I guess this wouldn't be too difficult to do. I said six
months ago that I might look at submitting a patch to do this, maybe I
should actually do it.
--
Matt
------------------------------
Message: 13
Date: Sun, 12 Jul 2015 08:56:26 +0000
From: Xin LI
To: Tomoaki AOKI ,
freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID:
Content-Type: text/plain; charset=UTF-8
I've spent some time on the MFC, the testing would still take some time
(likely a day or two) and once that's finished I'll ask re@ for
approval.
On Sat, Jul 11, 2015 at 11:44 PM Tomoaki AOKI
wrote:
> As I already mentioned in another post, head has 4.2.8 p3 in-tree.
>
> So the answer should be MFC before creation of releng/10.2 is planned
> or not.
>
>
> On Sun, 12 Jul 2015 15:04:43 +1000
> Peter Jeremy wrote:
>
> > On 2015-Jul-11 23:22:56 -0400, Chris Nehren <
> cnehren+freebsd-stable at pobox.com> wrote:
> > >On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
> > >> It's me again with my annual NTP whinge.
> > >
> > >The answer to the perennial "will release $foo ship with old
/ insecure
> > >/ otherwise deficient $bar?" is still "install $bar from
ports".
> >
> > That's a non-answer. It just changes the question to "why
bother to
> > include $bar in base when I need to install the port anyway".
> >
> > --
> > Peter Jeremy
>
>
> --
> Tomoaki AOKI junchoon at dec.sakura.ne.jp
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>
------------------------------
Message: 14
Date: Sun, 12 Jul 2015 11:41:53 +0200
From: Edward Tomasz Napiera?a
To: Harald Schmalzbauer
Cc: freebsd-stable at freebsd.org, kib at freebsd.org
Subject: Re: r284665 causes MSI problems -> ahcich2: Timeout in slot
11 port 0
Message-ID: <20150712094153.GA1549 at brick>
Content-Type: text/plain; charset=us-ascii
On 0711T1956, Harald Schmalzbauer wrote:> Hello,
>
> r284665 causes ahci(4) to fail with timeouts when using MSI (the default).
What's the hardware?
> 'hint.ahci.0.msi=0' is one way to make ahci(4) working with
r284665, but
> obviously not the desired solution, it just disables usage of an MSI.
>
> I can't find suspicious code in r282213 which could cause this strange
> regression, but I verified carefully that problem arises with r284665.
> Actually, r282901
>
(https://svnweb.freebsd.org/base?view=revision&sortby=date&revision=282901)
> is the real trigger, verified by putting
> nooptions RACCT
> nooptions RACCT_DEFAULT_TO_DISABLED
> nooptions RCTL
> into my kernel config -> problem vanishes!
>
> Setting "kern.racct.enable=1" doesn't make any difference, as
soon as
> 'kern.features.racct' exists, there's the ahci(4)/ahcich2
timeout and
> machine doesn't finish booting.
>
> Unfortunately, I don't have any idea how to track this down to the
> actual culprit, but I hope the RACCT hackers do have ;-)
>
> Shall I open a bugzilla ticket?
That's... curious. I don't see how those two things could be related.
What's the FreeBSD version? How reproducible it is? Have you tried
compiling with and without those three lines a couple of times?
------------------------------
Message: 15
Date: Sun, 12 Jul 2015 18:49:10 +0900
From: Tomoaki AOKI
To: freebsd-stable at freebsd.org
Subject: Re: Will 10.2 also ship with a very stale NTP?
Message-ID: <20150712184910.2d8d5f085ae659d5b9a2aba0 at dec.sakura.ne.jp>
Content-Type: text/plain; charset=US-ASCII
Wow! Thanks for your time and quick response.
I'm looking forward to seeing it MFCed. :-)
On Sun, 12 Jul 2015 08:56:26 +0000
Xin LI wrote:
> I've spent some time on the MFC, the testing would still take some time
> (likely a day or two) and once that's finished I'll ask re@ for
approval.
> On Sat, Jul 11, 2015 at 11:44 PM Tomoaki AOKI
> wrote:
>
> > As I already mentioned in another post, head has 4.2.8 p3 in-tree.
> >
> > So the answer should be MFC before creation of releng/10.2 is planned
> > or not.
> >
> >
> > On Sun, 12 Jul 2015 15:04:43 +1000
> > Peter Jeremy wrote:
> >
> > > On 2015-Jul-11 23:22:56 -0400, Chris Nehren <
> > cnehren+freebsd-stable at pobox.com> wrote:
> > > >On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote:
> > > >> It's me again with my annual NTP whinge.
> > > >
> > > >The answer to the perennial "will release $foo ship with
old / insecure
> > > >/ otherwise deficient $bar?" is still "install $bar
from ports".
> > >
> > > That's a non-answer. It just changes the question to
"why bother to
> > > include $bar in base when I need to install the port
anyway".
> > >
> > > --
> > > Peter Jeremy
> >
> >
> > --
> > Tomoaki AOKI junchoon at dec.sakura.ne.jp
> > _______________________________________________
> > freebsd-stable at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
> >
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>
--
Tomoaki AOKI junchoon at dec.sakura.ne.jp
------------------------------
Message: 16
Date: Sun, 12 Jul 2015 11:59:17 +0200
From: Harald Schmalzbauer
To: Edward Tomasz Napiera?a , FreeBSD Stable
, kib at freebsd.org
Subject: Re: r284665 causes MSI problems -> ahcich2: Timeout in slot
11 port 0
Message-ID: <55A23A75.8050003 at omnilan.de>
Content-Type: text/plain; charset="utf-8"
Bez?glich Edward Tomasz Napiera?a's Nachricht vom 12.07.2015 11:41
(localtime):> On 0711T1956, Harald Schmalzbauer wrote:
>> Hello,
>>
>> r284665 causes ahci(4) to fail with timeouts when using MSI (the
default).
> What's the hardware?
Thanks for your attention,
it's Intel Cougar Point (C204, 2x SATA6G+4xSATAII), via PCIe-Passthrough
in an ESXi guest.
Several of these setups have been in production with 9.2 and 10.1 for 2
years+ without ahcich timeouts.
>> 'hint.ahci.0.msi=0' is one way to make ahci(4) working with
r284665, but
>> obviously not the desired solution, it just disables usage of an MSI.
>>
>> I can't find suspicious code in r282213 which could cause this
strange
>> regression, but I verified carefully that problem arises with r284665.
>> Actually, r282901
>>
(https://svnweb.freebsd.org/base?view=revision&sortby=date&revision=282901)
>> is the real trigger, verified by putting
>> nooptions RACCT
>> nooptions RACCT_DEFAULT_TO_DISABLED
>> nooptions RCTL
>> into my kernel config -> problem vanishes!
>>
>> Setting "kern.racct.enable=1" doesn't make any
difference, as soon as
>> 'kern.features.racct' exists, there's the ahci(4)/ahcich2
timeout and
>> machine doesn't finish booting.
>>
>> Unfortunately, I don't have any idea how to track this down to the
>> actual culprit, but I hope the RACCT hackers do have ;-)
>>
>> Shall I open a bugzilla ticket?
> That's... curious. I don't see how those two things could be
related.
> What's the FreeBSD version? How reproducible it is? Have you tried
> compiling with and without those three lines a couple of times?
Yes, I tried several times, and falsified that with r284665 the timeouts
reproducably show up (which blocks the booting process, a major issue in
my case).
I also verified that several different revisions <284665 don't lead to
that problem, and also that the changes in ahci code paths for the last
year are not involved.
I also can't see any relation, wich doesn't mean much since I don't
have
the kernel skills, but I'm sure the symptoms start with "options
RACCT"
Thanks,
-Harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL:
------------------------------
Subject: Digest Footer
_______________________________________________
freebsd-stable at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
------------------------------
End of freebsd-stable Digest, Vol 624, Issue 6
**********************************************