Re: kldload uhci lockup
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. ___ 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"
9.0-RELEASE amd64: No Boot on VMWare Workstation
Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, then dies. Any ideas? What can I provide? And, is there an issue with 9 in general, or could I install 8.3 and then source update it to 9 or 10? Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: panic with overcommit and RACCT
On 5/14/12 12:29 AM, Mateusz Guzik wrote: On Sun, May 13, 2012 at 09:27:11PM +0400, Andrey Zonov wrote: Hi, I've got a repeatable panic on latest 9.0-STABLE and HEAD with turned on overcommit (vm.overcommit=1) and RACCT. kgdb trace on today's HEAD: #10 0x80bc3513 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #11 0x808aab71 in racct_set_locked (p=0xfe0005d684a0, resource=0, amount=2680) at /usr/src/sys/kern/kern_racct.c:372 #12 0x808ab645 in racct_proc_exit (p=0xfe0005d684a0) at /usr/src/sys/kern/kern_racct.c:615 #13 0x80880d69 in fork1 (td=0xfe0005b2c460, flags=20, pages=4, procp=0xff811a36bb00, procdescp=Variable "procdescp" is not available. ) at /usr/src/sys/kern/kern_fork.c:943 #14 0x80882362 in sys_fork (td=0xfe0005b2c460, uap=Variable "uap" is not available. ) at /usr/src/sys/kern/kern_fork.c:110 #15 0x80bd7a89 in amd64_syscall (td=0xfe0005b2c460, traced=0) at subr_syscall.c:135 #16 0x80bc37f7 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #17 0x0008024729fc in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Unread portion of the kernel message buffer: Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex racct lock (racct lock) r = 0 (0x8128a7c0) locked @ /usr/src/sys/kern/kern_racct.c:614 exclusive sleep mutex process lock (process lock) r = 0 (0xfe0005d68598) locked @ /usr/src/sys/kern/kern_racct.c:603 It looks like racct_proc_exit can be called for processes without properly initialized racct structure, which in turn results in this panic. Can you please test this patch: http://student.agh.edu.pl/~mjguzik/patches/racct-fork.patch ? I was unable to reproduce panic you describe, so it was tested only by manually injecting error. Nevertheless I think you should try it. :) Thanks, your patch fixes the panic. How to repeat: 1. add options RACCT and options RCTL to kernel config, rebuild and install kernel, reboot 2. set sysctl vm.overcommit=1 3. run as none root something that eats memory (I just run malloc() until it returns NULL) 4. swapoff -a 5. panic after sometime With patch applied instead of panic I got: "fork: Cannot allocate memory". Looks like a bug in overcommit code. -- Andrey Zonov ___ 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: 9.0-RELEASE amd64: No Boot on VMWare Workstation
On 5/14/2012 22:18, Larry Rosenman wrote: Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? Since nobody has chimed in I felt I should: I use FreeBSD 9.0 routinely under VMWare Workstation without issue (my current VMWare Workstation version is 8.0.0 which is slightly out of date, 8.0.3 is available). I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, then dies. Any ideas? What can I provide? The version of VMWare Workstation you are running. And, is there an issue with 9 in general, or could I install 8.3 and then source update it to 9 or 10? I build test VMs for 9 and do test upgrades from 6.x, 7.x and 8.x to 9 using VMWare Workstation on my desktop and laptop without issue. ___ 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"
