Re: panic: mutex vm not owned...
Hello Alfred, hello everybody, On Sat, May 19, 2001 at 10:08:25PM -0400, Alfred Perlstein wrote: * Alfred Perlstein [EMAIL PROTECTED] [010519 21:57] wrote: * Szilveszter Adam [EMAIL PROTECTED] [010519 16:53] wrote: Hello everybody, I guess I was just being too happy so it had to get me this time:-) I was building Mozilla when it struck. Today's -CURRENT, kernel world in sync, no softupdates. panic: mutex vm not owned at ../../vm/vm_page.h:328 Debugger(panic) ... Thanks for the traceback, can you apply this patch then try to get your machine to swap? Oh, yeah, thanks for being brave, I've got a lot of other developers telling me they're not upgrading past the vm mutex patch point which is pretty stupid as it's doing to more harm then good without a thorough workout. :( I'm afraid I don' understand this one exactly. Did other developers oppose that you give this patch to me? Why? If they have not yet upgraded, that's fine. I was not asking to solve this problem here and now (although a solution is great:-) I was trying to help narrow it down since appearently I am the one with this problem right now. There is no hurry, this machine is play-box, which normally does nothing important, just a surf terminal. Being able to use X would be nice however, but more on that later:-) So, anyways, thanks for trying to help, I applied the patch nevertheless. I have since discovered a sure-fire method to cause a freeze and reboot, however, and maybe this may shed some light. Unfortunately, the method involves starting X, which makes debugging difficult. As soon as I attempt to start it, the screen enters SVGA mode and turns dark but the X server is never actually started it seems or at least never comes but the whole machine hangs for a couple of secs and then reboots itself. Unfortunately, while in this wedged state, it doesn't seem to be interested in me:-( Note that this effect is not dependent on the patch, but only appeared with yesterday's build, earlier X always worked fine. What effect, if any, the patch will have will show hopefully during the course of the day. Another interesting nit: - It seems that if I power-cycle the machine and start up clean, it can do approx 1-1,5 hours of compiling at which point it will panic like posted. This time the trace was: Debugger panic _mtx_assert swp_pager_async_iodone _iodone bufdone bufdonebio ad_interrupt ata_intr ithread_loop fork_exit fork_trampoline and it did not even attempt to dump, just froze at synching disks I had to reset it. - However, if after this I bring it up in single-user, do a manual fsck, and continue in multi-user, than it could do compiles and more (eg I restarted the Mozilla build after my initial report and hit the hay, and by morning the machine was still up, the compile finished successfully and even the periodic script runs caused apperently no problem.) So this seems rather interesting of a locking issue... however, some other info I did not give: this is an UP system, which may be important. As usual, I am more than happy to provide info, test, etc. BTW this appears to be recent and possibly related to the problem: -snip from kernel build log.--- cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstri ct-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fform at-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h - elf -mpreferred-stack-boundary=2 ../../ddb/db_watch.c In file included from ../../ddb/db_watch.c:41: ../../vm/vm_map.h: In function `_vm_map_lock_upgrade': ../../vm/vm_map.h:265: warning: implicit declaration of function `mtx_lock' and cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstri ct-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fform at-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h - elf -mpreferred-stack-boundary=2 ../../kern/link_elf.c In file included from ../../kern/link_elf.c:52: ../../vm/vm_map.h: In function `_vm_map_lock_upgrade': ../../vm/vm_map.h:265: warning: implicit declaration of function `mtx_lock' -end of snippet it also happens in the ibcs2 and fpu modules. Of course this may be pure BS, I am not a kernel hacker, just speculate. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned...
Hello, I am back with more information. The machine had been up mostly idle for about 1 1/2 hours again. I am starting to suspect that it is being idle that may also trip the wire here... maybe, given my 128megs of RAM and 300 megs of swap, that's when my computer decides that it's time to swap some stuff and boom. Alfred's patch indeed seems to have changed things a bit: It paniced after 1h37m uptime during a CVS checkout, with the following: panic: sleeping with vm_mtx held trace: Debugger panic msleep swap_pager_getpages vm_fault1 vm_fault trap_pfault trap calltrap ---trap 0xc, eip= 0x2824dc2e, esp=0xbfbfe16c, ebp=0xbfbfe160 then after 'c': syncing disks... panic: mutex vm owned at ../../kern/vfs_bio:2998 nice long trace: Debugger panic _mtx_assert vfs_busy_pages bwrite vfs_bio_awrite spec_fsync spec_vnoperate ffs_sync sync boot panic msleep swap_pager_getpages vm_fault1 vm_fault trap_pfault trap calltrap and again the same trap message like above. After hitting 'c', it freezes at the dumping: resetting devices part. This starts to become interesting... will follow up with more when found. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel trap 12 with interrupts disabled
On Sat, 19 May 2001 22:48:51 -0400, Alfred Perlstein [EMAIL PROTECTED] said: You'll have to provide more info before anyone can help you. Well, that would require the kernel offering me more information. Can you at least get a DDB traceback? I have never succeeded in getting that to work, but I'll try once again ... -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel trap 12 with interrupts disabled
This may not help much unless there is some common ground to be found. I have been having problems with my old K6-2 300Mhz laptop hanging in X with linux-communicator. From there I have not been able to get any debugging info. Last night I did a power off/on reset and went to bed. This morning I had a login with a nice bold kernel trap 12 with interrupts disabled that happened a couple of hours later after cvsuping and initiating a make world. I'm going to see if I can get it to do it again although I was able to do a make world and kernel yesterday with no problem. The only problem that I was able to see before was with X and netscape. ed Quoting Michael Harnois [EMAIL PROTECTED]: On Sat, 19 May 2001 22:48:51 -0400, Alfred Perlstein [EMAIL PROTECTED] said: You'll have to provide more info before anyone can help you. Well, that would require the kernel offering me more information. Can you at least get a DDB traceback? I have never succeeded in getting that to work, but I'll try once again ... -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel trap 12 with interrupts disabled
I forgot to add that I'm not seeing any of this with the PIII's that I have running current and usually updated daily. This may not help much unless there is some common ground to be found. I have been having problems with my old K6-2 300Mhz laptop hanging in X with linux-communicator. From there I have not been able to get any debugging info. Last night I did a power off/on reset and went to bed. This morning I had a login with a nice bold kernel trap 12 with interrupts disabled that happened a couple of hours later after cvsuping and initiating a make world. I'm going to see if I can get it to do it again although I was able to do a make world and kernel yesterday with no problem. The only problem that I was able to see before was with X and netscape. ed Quoting Michael Harnois [EMAIL PROTECTED]: On Sat, 19 May 2001 22:48:51 -0400, Alfred Perlstein [EMAIL PROTECTED] said: You'll have to provide more info before anyone can help you. Well, that would require the kernel offering me more information. Can you at least get a DDB traceback? I have never succeeded in getting that to work, but I'll try once again ... -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message --- The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn and relearn. --Alvin Toffler To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: mutex vm not owned
The machine is up for about one minute and then I ran `startx' and the screen turned black and it appeared to lockup, after about 30 seconds plus some banging on the keyboard it rebooted. I have 256mb ram, so it shouldn't be swapping at this point. The kernel and world are cvsupd to about 12am May 20 EDT, the following is the panic message: panic: mutex vm not owned at /usr/src/sys/vm/vm_object.c:330 This was the first time I've tried getting a crashdump and analyzing it, however when I follow the directions in the handbook, gdb seg. faults (could this be because it panic'd in the vm system ??) : enterprise# pwd /usr/obj/usr/src/sys/BUTTER enterprise# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd. (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 Segmentation fault (core dumped) I also have DDB in my kernel config, but it didn't drop into DDB. Is there anything else I can test? I'm willig to test any patches or whatever. Thanks, Mike -- Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA [EMAIL PROTECTED] http://filebox.vt.edu/users/mheffner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
another new vm/swap panic
The follow fatal trap seems to be caused by the vm locking changes: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3a fault code = supervisor write, page not present instruction pointer = 0x8:0xc027a13e stack pointer = 0x10:0xc35f0db8 frame pointer = 0x10:0xc35f0e58 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 3 (vmdaemon) kernel: type 12 trap, code=0 Stopped at vm_fault1+0x122:incw0x3a(%eax) db t vm_fault1(c033bd0c,c38a5000,1,0,c325adc0) at vm_fault1+0x122 vm_fault(c033bd0c,c38a5000,1,0,c325adc0) at vm_fault+0x8e trap_pfault(c35f0ee4,0,c38a5bfc,0,bfc0) at trap_pfault+0x1ce trap(18,10,10,0,bfc0) at trap+0x430 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc02ac284, esp = 0xc35f0f24, ebp = 0xc35f0f24 --- get_ptbase(c325faac,c325fa40,c325fa40,0,0) at get_ptbase+0x8 pmap_remove(c325faac,0,bfc0) at pmap_remove+0x5c vm_pageout_map_deactivate_pages(c325fa40,0) at vm_pageout_map_deactivate_pages+0xb0 vm_daemon(0,c35f0fa8) at vm_daemon+0x230 fork_exit(c0287834,0,c35f0fa8) at fork_exit+0x50 fork_trampoline() at fork_trampoline+0x8 db sh r cs 0x8 ds0x10 es0x10 fs0x18 ss0x10 eax 0 ecx 0xc35f0e04 edx0x7 ebx 0 esp 0xc35f0db8 ebp 0xc35f0e58 esi0x1 edi 0xc38a5000 eip 0xc027a13e vm_fault1+0x122 efl0x10286 vm_fault1+0x122:incw0x3a(%eax) db This is with some missing locks added to swap_pager.c. To duplicate this, try dd if=/dev/zero of=/dev/null bs=N, where N is about 12MB less than the memory size (just enough to use a few MB of swap). vm_fault() gets called with map == kernel_map for a pagefault in get_ptbase(). This shouldn't happen and is soon fatal. (The final fault address of 0x3a is irrelevant. It is just for the incw instruction. %eax is fs.first_object which is null. vm_map_lookup() refuses to create a non-null object because the map is a system map.) I once got a panic a little earlier in vm_pageout_map_deactivate_pages() for attempting to access a vm_map_entry of ZENTRY_FREE. atadump() always locked up attempting to dump from here. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
On Sun, May 20, 2001 at 12:59:51PM -0400, Mike Heffner wrote: The machine is up for about one minute and then I ran `startx' and the screen turned black and it appeared to lockup, after about 30 seconds plus some banging on the keyboard it rebooted. I have 256mb ram, so it shouldn't be swapping at this point. The kernel and world are cvsupd to about 12am May 20 EDT, the following is the panic message: I'm getting a panic whenever I start X too (with a kernel from earlier today). I managed to get a DDB trace from a serial console. David. panic: mutex vm not owned at ../../vm/vm_object.c:330 Debugger(panic) Stopped at Debugger+0x44: pushl %ebx db t Debugger(c02fdbbb) at Debugger+0x44 panic(c02fcc07,c0313f10,c0315234,14a,c038fe40) at panic+0x70 _mtx_assert(c03bfb80,1,c0315234,14a) at _mtx_assert+0x49 vm_object_deallocate(c038fe40,c0de4030,c863d300,c8692f38,c01e59f3) at vm_object_ deallocate+0x1e shm_deallocate_segment(c0de4030,c8692f80,c863d300,4,c863d300) at shm_deallocate_ segment+0x12 shmctl(c863d300,c8692f84,c863d300,0,c8692fa0) at shmctl+0x117 shmsys(c863d300,c8692f80,2838d9f4,1,bfbffc80) at shmsys+0x43 syscall(2f,2f,2f,bfbffc80,1) at syscall+0x7f9 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
David Malone [EMAIL PROTECTED] writes: On Sun, May 20, 2001 at 12:59:51PM -0400, Mike Heffner wrote: The machine is up for about one minute and then I ran `startx' and the screen turned black and it appeared to lockup, after about 30 seconds plus some banging on the keyboard it rebooted. I have 256mb ram, so it shouldn't be swapping at this point. The kernel and world are cvsupd to about 12am May 20 EDT, the following is the panic message: I'm getting a panic whenever I start X too (with a kernel from earlier today). I managed to get a DDB trace from a serial console. Please try the attached patch. I make no claims of its correctness, but this e-mail is coming to you via X on -current updated a few hours ago so it works here :-). I had to manually edit out some unrelated local changes, so if you have trouble applying it fetch the full one from http://www.unixfreak.org/~dima/home/shm-full.diff. That one has local changes (new sysctls), but they (probably) won't hurt you. Thanks, Dima Dorfman [EMAIL PROTECTED] Index: sysv_shm.c === RCS file: /stl/src/FreeBSD/src/sys/kern/sysv_shm.c,v retrieving revision 1.56 diff -u -r1.56 sysv_shm.c --- sysv_shm.c 2001/05/19 01:28:03 1.56 +++ sysv_shm.c 2001/05/20 20:26:28 @@ -182,7 +186,9 @@ size_t size; shm_handle = shmseg-shm_internal; + mtx_lock(vm_mtx); vm_object_deallocate(shm_handle-shm_object); + mtx_unlock(vm_mtx); free((caddr_t)shm_handle, M_SHM); shmseg-shm_internal = NULL; size = round_page(shmseg-shm_segsz); @@ -203,7 +209,9 @@ segnum = IPCID_TO_IX(shmmap_s-shmid); shmseg = shmsegs[segnum]; size = round_page(shmseg-shm_segsz); + mtx_lock(vm_mtx); result = vm_map_remove(p-p_vmspace-vm_map, shmmap_s-va, shmmap_s-va + size); + mtx_unlock(vm_mtx); if (result != KERN_SUCCESS) return EINVAL; shmmap_s-shmid = -1; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: I broke swapping
I broke swapping with the vm mutex. Hopefully I should have this fixed up within a couple of days tops. No, I'm not heading off to Aruba or someplace after this intrusive change, I am working on it. Your kernel may panic, but I hope you all keep a level head about this and don't follow suit. :) Patches, suggestions and crashdumps would be helpful. Bruce has been giving me some helpful tracebacks that I'm planning to use to stabilize the system. thanks, -- -Alfred Perlstein [[EMAIL PROTECTED]] Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
On Sun, May 20, 2001 at 01:29:22PM -0700, Dima Dorfman wrote: David Malone [EMAIL PROTECTED] writes: On Sun, May 20, 2001 at 12:59:51PM -0400, Mike Heffner wrote: The machine is up for about one minute and then I ran `startx' and the screen turned black and it appeared to lockup, after about 30 seconds plus some banging on the keyboard it rebooted. I have 256mb ram, so it shouldn't be swapping at this point. The kernel and world are cvsupd to about 12am May 20 EDT, the following is the panic message: I'm getting a panic whenever I start X too (with a kernel from earlier today). I managed to get a DDB trace from a serial console. Please try the attached patch. I make no claims of its correctness, but this e-mail is coming to you via X on -current updated a few hours ago so it works here :-). OK, I've just tried this and would like to report that it works. Of course, using X without swapping is not practically possible:-) but as a demonstration it's all right. Now I hope the other problems with swapping can also be sorted out. I have sent Alfred some traces, unfortunately this is about all, dumping is not possible... let's hope for the best. Luckily, console based CD players also exist.grin -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
On 20-May-2001 Dima Dorfman wrote: | Please try the attached patch. I make no claims of its correctness, | but this e-mail is coming to you via X on -current updated a few hours | ago so it works here :-). Thanks, it works so far (I'm running X). I'll see where it breaks next. Mike -- Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA [EMAIL PROTECTED] http://filebox.vt.edu/users/mheffner PGP signature
Re: panic: mutex vm not owned
[cc's trimmed] aol Same problem, this fixed me too. /aol On Sun, May 20, 2001 at 05:23:11PM -0400, Mike Heffner wrote: On 20-May-2001 Dima Dorfman wrote: | Please try the attached patch. I make no claims of its correctness, | but this e-mail is coming to you via X on -current updated a few hours | ago so it works here :-). Thanks, it works so far (I'm running X). I'll see where it breaks next. Mike -- Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA [EMAIL PROTECTED] http://filebox.vt.edu/users/mheffner -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
* Szilveszter Adam [EMAIL PROTECTED] [010520 17:07] wrote: On Sun, May 20, 2001 at 01:29:22PM -0700, Dima Dorfman wrote: Please try the attached patch. I make no claims of its correctness, but this e-mail is coming to you via X on -current updated a few hours ago so it works here :-). OK, I've just tried this and would like to report that it works. Of course, using X without swapping is not practically possible:-) but as a demonstration it's all right. Now I hope the other problems with swapping can also be sorted out. I have sent Alfred some traces, unfortunately this is about all, dumping is not possible... let's hope for the best. Luckily, console based CD players also exist.grin That patch was committed to -current several hours ago. you should have version 1.57 of sys/kern/sysv_shm.c. Of course this only fixes sysv shm, not swapping. -- -Alfred Perlstein [[EMAIL PROTECTED]] Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Boot time memory issue
I was curious whether the memory limitation on the Sony VAIO Z505 machines was an actual hardware limitation or a marketing issue. I just tried adding a 256MB module to my machine. The BIOS seemed to mostly recognize it. It did see 320MB of RAM, but had problems when testing all of it. Current (from a couple of weeks ago) boots, but gives me: Too many holes in the physical address space, giving up and comes up showing 64MB of RAM. Is this something that can be worked around, or have I run up against an actual hardware limit on the machine? barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src Makefile.inc1
Bruce Evans [EMAIL PROTECTED] writes: Debian CDs on FreeBSD with linux emulation way better than you can build say a -STABLE release on a -CURRENT box... ) I just tried a Linux fdisk binary built in 1997 under FreeBSD-current. It seemed to run perfectly except it couldn't determine the disk geometry automatically. some times ago, I've ported linux fdisk to native freebsd. if you really need it, I could make it a port ? Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src Makefile.inc1
Bruce Evans [EMAIL PROTECTED] writes: Debian CDs on FreeBSD with linux emulation way better than you can build say a -STABLE release on a -CURRENT box... ) I just tried a Linux fdisk binary built in 1997 under FreeBSD-current. It seemed to run perfectly except it couldn't determine the disk geometry automatically. some times ago, I've ported linux fdisk to native freebsd. if you really need it, I could make it a port ? Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: /usr/src/usr.bin/login
On Wed, 16 May 2001, Terry Lambert wrote: This patch adds the prompt and passwd_prompt fields to the /etc/login.conf, which makes lgoin more like getty in its ability to be configured. Cool, I used to hack mine by hand to look like OpenVMS... Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: workitem_free: still on list
I sent a similar crash trace to Kirk recently, and he claimed to have fixed it (look for a commit crediting me as a source of information sometime in the last few days). However, given the currently VM problems, you'll want to pull in those FFS patches carefully :-). Since I'm 500 miles from the box that crashed and haven't had a chance to reset it yet, I can't confirm if Kirk's fix works. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Sat, 19 May 2001, Bob Bishop wrote: Hi, This happened during a buildworld with a kernel built from: cvsup Fri May 18 04:06:02 BST 2001 On reboot, I got the manual fsck jive with the bad superblock: values disagree ,,with,, first alternate, and had to re-enable softupdates on / Config is basically GENERIC + SMP. dmesg is appended. Abridged backtrace: panic() workitem_free() free_newdirblk() handle_written_inodeblock() softdep_disk_write_complete() bufdone() bufdonebio() dadone() camisr() ithread_loop() fork_exit() fork_trampoline() dmesg: FreeBSD 5.0-CURRENT #20: Wed May 16 00:24:36 BST 2001 [EMAIL PROTECTED]:/source/cleansrc/sys/compile/BLUDNOK_MP Timecounter i8254 frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (349.07-MHz 686-class CPU) Origin = GenuineIntel Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO V,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) config enable ed0 config port ed0 0x300 config irq ed0 10 config iomem ed0 0xd8000 config flags ed0 0 config disable cs0 config disable fe0 config disable ie0 config disable lnc0 config disable sn0 config quit avail memory = 124653568 (121732K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc05bb000. Preloaded userconfig_script /boot/kernel.conf at 0xc05bb09c. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 7 entries at 0xc00fda90 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard IOAPIC #0 intpin 16 - irq 2 IOAPIC #0 intpin 19 - irq 16 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 11 at de vice 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter PIIX frequency 3579545 Hz pci0: bridge, PCI-unknown at 7.3 (no driver attached) ahc0: Adaptec 2940 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xea00-0xea00 0fff irq 2 at device 8.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: display, VGA at 11.0 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 drq 0 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 ad0: 1222MB QUANTUM FIREBALL_TM1280A [2484/16/63] at ata0-master WDMA2 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s2a cd0 at ahc0 bus 0 target 6 lun 0 cd0: PIONEER DVD-ROM DVD-303 1.09 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size
