USB critically broken under RELENG_7 on amd64
Hi, Since jhb@ committed the fixes for ULi SATA, I updated my kernel+world on my amd64 desktop machine. So far so good. I updated again Tuesday. Unfortunately I am now seeing USB warnings during boot: uhub1: device problem (TIMEOUT), disabling port 1 I get messages like this for any and all attempts to attach USB devices. ...It works just fine in Windows XP, and worked just fine in RELENG_7 before. What's going on? it doesn't appear to be a repeat of the HAL / libpciaccess saga from February as it happens from boot. This is an ALi OHCI + EHCI controller, fwiw. usbdevs -v spews a lot of 'addr 0 should never happen!'. Could this be an interrupt handling bug of some kind? cheers, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: USB critically broken under RELENG_7 on amd64
Bruce Simpson wrote: Hi, Since jhb@ committed the fixes for ULi SATA, I updated my kernel+world on my amd64 desktop machine. So far so good. I updated again Tuesday. If I revert to the kernel I built from RELENG_7 on June 10th, all is fine. I saw no changes in SVN to the stable/7/sys/dev/usb directory in that time which looked as though they could obviously break USB in such a complete way. Has anyone else seen this issue? It seems fairly critical as a number of folk may not be able to upgrade to FreeBSD 8.0 right away. thanks, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
dtrace_gethrtime in sys/amd64/amd64/tsc.c
sys/amd64/amd64/tsc.c in stable/7 has dtrace_gethrtime at the end. It was added in rev 182231, which claims to do MFC for dtrace but doesn't list any specific revisions. But in head I do not see any relevant commit and the function is not present in the file. John, could you please comment? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS Assertion Fault with FreeBSD 7.2
Good Evening, This is a heads up really, I think I've got this sorted. I'm writing this as my system backs up data to another array in case it all explodes. This afternoon I was performing some MPEG4 encoding with ffmpeg source file and destination file where both located on the same ZFS partition. Part way through the ffmpeg encode the process went to the zfs:lo state and hung, all processes that attempted to browse to the partition data/domains hung immediately. I attempted to reboot the machine in order to restore normality however the system stuck half way through shutting down. In the end a hard power off was issued to shut the machine down. Upon reboot during the ZFS rc.d init script I saw the following: panic: solaris assert: 0 == dmu_bonus_hold(zfsvfs-z_os, *oid, NULL, dbp), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c, line: 472 Apologies for single character errors that's typed from an image. Through diagnosis I was able to determine the error was being caused by a mirror zpool called store. I booted into single user mode, /etc/rc.d/hostname and /etc/rc.d/hostid. Looking at the ZFS rc.d file I was able to zfs volinit with no issues, the panic was reproducable on zfs mount -a. I then began to load each mount point one by one until I found the one causing the issue. This is store/sara/unix/Maildir, it is a compressed volume, otherwise nothing custom. Following my ancient ufs logic I attempted to mount it read only, this worked and spat out the following kernel warning: Solaris: WARNING: ZFS replay transaction error 30, dataset store/sara/unix/Maildir, seq 0x77001, txtype 5 To aid diagnosis and because I'd damaged rc environment while debugging, I rebooted, single user-ed, and mounted the whole of store as read only. However this time the warning did not show. I am currently in the process of copying the entirety of store to data, I was planning to attempt remounting the entire volumes mount points read/write once the backup is done. Is there anything else that I should be doing to a) attempt to ensure my data structures are now okay and b) help find the problem. I understand a) will probably prevent b), but the data is too important to risk, sorry. A scrub of the volume came to mind as a double check. Any thoughts are greatly appreciated, apologies if this email comes out badly, my email is on this server, so I'm webmailing and scrounging through mqueue's on the upstream. Peter. -- Peter Wood :: pe...@alastria.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS Assertion Fault with FreeBSD 7.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Peter, Peter Wood wrote: Good Evening, Upon reboot during the ZFS rc.d init script I saw the following: panic: solaris assert: 0 == dmu_bonus_hold(zfsvfs-z_os, *oid, NULL, dbp), file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_znode.c, line: 472 This seems to come from ZFSv6 code which was shipped with 7.2-RELEASE. A lot of improvements has been done with the recent ZFSv13 merge (into 7.2-STABLE), which maybe helpful. Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkpECHAACgkQi+vbBBjt66AiQQCfQFIV0Ooif4nck57TET/EUjcD N/0AoLs7PhKLUq4kcKSqta494AVrsqvH =ulbg -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: USB critically broken under RELENG_7 on amd64
On Thu, Jun 25, 2009 at 12:34:01PM +0100, Bruce Simpson wrote: Since jhb@ committed the fixes for ULi SATA, I updated my kernel+world on my amd64 desktop machine. So far so good. I updated again Tuesday. Unfortunately I am now seeing USB warnings during boot: uhub1: device problem (TIMEOUT), disabling port 1 I get messages like this for any and all attempts to attach USB devices. That's about the timeframe that I started having problems with my USB-connected drives. I posted about it last week on -stable, but didn't get any replies. The symptoms weren't exactly the same though. It's not something that is easy for me to fiddle with, because the system is my main server and I like it to stay up... Cheers, -- Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
