Date: Mon, 14 May 2012 03:21:21 -0700 (PDT) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-stable@freebsd.org Subject: Re: kldload uhci lockup Message-ID: <1336990881867-5708179.post@n5.nabble.com> In-Reply-To: <1334690248353-5647339.post@n5.nabble.com> References: <1334608066241-5644899.post@n5.nabble.com> <1334690248353-5647339.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Here we go again... After attempting to load those modules xterm hang, top was locked up, couldn't select anything to buffer in xterm, bell rang consistently BUT.. Other xterm was responsive and I managed to grab screenshot and vmstat -i. After forced shutdown, journaled filesystems were marked clean, however as I saw 'free inodes' in syslog, I shut system down again and ran fsck in single user mode. As predicted inconsistencies showed up, after clearing those up, still in syslog some free inodes showed up and opera was broken (reverted to default layout, good I had bookmarks backed up) as usually in cases when not cleanly shut down. So I'm overall disappointed in journalled UFS2, there were no forced shutdown that hasn't left me without inconsistencies, and usually opera is clearly broken most times, because it's running always and using disk space.. And this could be the case with more important services too. Here is screenshot: wow... looks like it was one of those files that couldn't make it after shutdown... it's missing anyway. FWIW, vmstat -i was not showing rapidly increasing interrupts, and offending command was something like $ sudo kldload usb ums ahci uhci So still nothing new. -- View this message in context: http://freebsd.1045724.n5.nabble.com/kldload-uhci-lockup-tp5644899p5708179.html Sent from the freebsd-stable mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1336990881867-5708179.post>