Re: panic at boot in ffs_valloc
Hi. On Wed, Jul 03, 2002 at 09:36:24PM +0200, Rasmus Skaarup wrote: I'm also suddenly having a panics - every 5 minutes actually, since my latest cvsup a few hours ago. They seem to be related to some ufs and ffs calls.. I'm not able to read my core dumps for some reason (gdb says kernel symbol 'cpuhead' not found.) and I don't have the time to scratch a backtrace down by hand just now. The panicstring is: bremfree: bp 0xc77e8670 not locked Sincerely, Rasmus Skaasrup On Wed, 3 Jul 2002, Andrew R. Reiter wrote: :I cvsup'd and built world+kernel a few hours ago and was happy to see :KDE working again, but I got a spontaneous reboot while trying to track :down a segfault in a mozilla build component. I boot -v'ed and as :soon as the login prompt came up I hit a panic. I'm guessing the :backgorund fsck had something to do with it. I'll hand-copy the trace :here; any debugging info needed while my box is stuck at the debugger, :lemme know: I don't have the output to show people since I was trying to reproduce but couldnt, but i got essentially the same panic, but it came only from a syscall to open() that called ufs_create() - ufs_makeinode - ffs_valloc() - panic. I can try and reproduce (tho, mine occured when just running cscope) and get a dump. same here, and I can reproduce the panic by: $ cd /tmp $ for i in `jot 300 1`; do touch $i; done this panics when $i reaches around 128 on my machine. However, the next one doesn't: $ mkdir /tmp/foo $ cd /tmp/foo $ for i in `jot 300 1`; do touch $i; done I have a 256Mbytes of swap-backed /tmp configured in /etc/rc.local as follows: $ cat /etc/rc.local mdmfs -p 1777 -s 256M md0 /tmp According to a post on an anonymous BBS in Japan, malloc-backed /tmp doesn't seem to trigger the panic. Regards. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic at boot in ffs_valloc
I cvsup'd and built world+kernel a few hours ago and was happy to see KDE working again, but I got a spontaneous reboot while trying to track down a segfault in a mozilla build component. I boot -v'ed and as soon as the login prompt came up I hit a panic. I'm guessing the backgorund fsck had something to do with it. I'll hand-copy the trace here; any debugging info needed while my box is stuck at the debugger, lemme know: -- Anthony Jenkins Additional TCP options:. Starting background filesystem checks Wed Jul 3 13:24:09 EDT 2002 FreeBSD/i386 (foo) (ttyv0) login: mode = 041777, inum = 12871, fs = /usr panic: ffs_valloc: dup alloc cpuid = 0; lapic.id = Debugger(panic) Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db trace Debugger(c02d9eda) at Debugger+0x46 panic(c02e9a21,c02e9a00,43ff,3247,c41c58d4) at panic+0xd6 ffs_valloc(c4284100,8100,c159a180,d6afd6f0) at ffs_valloc+0x141 ufs_makeinode(8100,c4284100,d6afda20,d6afda34) at ufs_makeinode+0x58 ufs_create(d6afd94c,d6afda68,c0248a68,d6afd94c,c0346b78) at ufs_create+0x26 ufs_vnoperate(d6afd94c) at ufs_vnoperate+0x13 ffs_snapshot(c41b7600,80b2ba0,d6afda94,c41db700,c0346bf0) at ffs_snapshot+0x2a0 ffs_mount(c41b7600,c4421200,bfbffcc0,d6afdbf8,c159f300) at ffs_mount+0x48 vfs_mount(c159f300,c41b2eb0,c4421200,1211000,bfbffcc0) at ffs_mount+0x6dc mount(c159f300,d6afdd14,4,1,202) at mount+0x6a syscall(2f,2f,2f,0,bfbffde0) at syscall+0x23c syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (21, FreeBSD ELF, mount), eip = 0x80549d7, esp = 0xbfbffbdc, ebp = 0xbfbffd48 --- db -- Anthony Jenkins http://www.mindspring.com/~abjenkins/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic at boot in ffs_valloc
:I cvsup'd and built world+kernel a few hours ago and was happy to see :KDE working again, but I got a spontaneous reboot while trying to track :down a segfault in a mozilla build component. I boot -v'ed and as :soon as the login prompt came up I hit a panic. I'm guessing the :backgorund fsck had something to do with it. I'll hand-copy the trace :here; any debugging info needed while my box is stuck at the debugger, :lemme know: I don't have the output to show people since I was trying to reproduce but couldnt, but i got essentially the same panic, but it came only from a syscall to open() that called ufs_create() - ufs_makeinode - ffs_valloc() - panic. I can try and reproduce (tho, mine occured when just running cscope) and get a dump. Cheers, Andrew :FreeBSD/i386 (foo) (ttyv0) : :login: mode = 041777, inum = 12871, fs = /usr :panic: ffs_valloc: dup alloc :cpuid = 0; lapic.id = :Debugger(panic) :Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 :db trace :Debugger(c02d9eda) at Debugger+0x46 :panic(c02e9a21,c02e9a00,43ff,3247,c41c58d4) at panic+0xd6 :ffs_valloc(c4284100,8100,c159a180,d6afd6f0) at ffs_valloc+0x141 :ufs_makeinode(8100,c4284100,d6afda20,d6afda34) at ufs_makeinode+0x58 :ufs_create(d6afd94c,d6afda68,c0248a68,d6afd94c,c0346b78) at ufs_create+0x26 :ufs_vnoperate(d6afd94c) at ufs_vnoperate+0x13 :ffs_snapshot(c41b7600,80b2ba0,d6afda94,c41db700,c0346bf0) at :ffs_snapshot+0x2a0 :ffs_mount(c41b7600,c4421200,bfbffcc0,d6afdbf8,c159f300) at ffs_mount+0x48 :vfs_mount(c159f300,c41b2eb0,c4421200,1211000,bfbffcc0) at ffs_mount+0x6dc :mount(c159f300,d6afdd14,4,1,202) at mount+0x6a :syscall(2f,2f,2f,0,bfbffde0) at syscall+0x23c :syscall_with_err_pushed() at syscall_with_err_pushed+0x1b :--- syscall (21, FreeBSD ELF, mount), eip = 0x80549d7, esp = 0xbfbffbdc, :ebp = 0xbfbffd48 --- :db : :-- :Anthony Jenkins :http://www.mindspring.com/~abjenkins/ : : : :To Unsubscribe: send mail to [EMAIL PROTECTED] :with unsubscribe freebsd-current in the body of the message : -- Andrew R. Reiter [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic at boot in ffs_valloc
I'm also suddenly having a panics - every 5 minutes actually, since my latest cvsup a few hours ago. They seem to be related to some ufs and ffs calls.. I'm not able to read my core dumps for some reason (gdb says kernel symbol 'cpuhead' not found.) and I don't have the time to scratch a backtrace down by hand just now. The panicstring is: bremfree: bp 0xc77e8670 not locked Sincerely, Rasmus Skaasrup On Wed, 3 Jul 2002, Andrew R. Reiter wrote: :I cvsup'd and built world+kernel a few hours ago and was happy to see :KDE working again, but I got a spontaneous reboot while trying to track :down a segfault in a mozilla build component. I boot -v'ed and as :soon as the login prompt came up I hit a panic. I'm guessing the :backgorund fsck had something to do with it. I'll hand-copy the trace :here; any debugging info needed while my box is stuck at the debugger, :lemme know: I don't have the output to show people since I was trying to reproduce but couldnt, but i got essentially the same panic, but it came only from a syscall to open() that called ufs_create() - ufs_makeinode - ffs_valloc() - panic. I can try and reproduce (tho, mine occured when just running cscope) and get a dump. Cheers, Andrew :FreeBSD/i386 (foo) (ttyv0) : :login: mode = 041777, inum = 12871, fs = /usr :panic: ffs_valloc: dup alloc :cpuid = 0; lapic.id = :Debugger(panic) :Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 :db trace :Debugger(c02d9eda) at Debugger+0x46 :panic(c02e9a21,c02e9a00,43ff,3247,c41c58d4) at panic+0xd6 :ffs_valloc(c4284100,8100,c159a180,d6afd6f0) at ffs_valloc+0x141 :ufs_makeinode(8100,c4284100,d6afda20,d6afda34) at ufs_makeinode+0x58 :ufs_create(d6afd94c,d6afda68,c0248a68,d6afd94c,c0346b78) at ufs_create+0x26 :ufs_vnoperate(d6afd94c) at ufs_vnoperate+0x13 :ffs_snapshot(c41b7600,80b2ba0,d6afda94,c41db700,c0346bf0) at :ffs_snapshot+0x2a0 :ffs_mount(c41b7600,c4421200,bfbffcc0,d6afdbf8,c159f300) at ffs_mount+0x48 :vfs_mount(c159f300,c41b2eb0,c4421200,1211000,bfbffcc0) at ffs_mount+0x6dc :mount(c159f300,d6afdd14,4,1,202) at mount+0x6a :syscall(2f,2f,2f,0,bfbffde0) at syscall+0x23c :syscall_with_err_pushed() at syscall_with_err_pushed+0x1b :--- syscall (21, FreeBSD ELF, mount), eip = 0x80549d7, esp = 0xbfbffbdc, :ebp = 0xbfbffd48 --- :db : :-- :Anthony Jenkins :http://www.mindspring.com/~abjenkins/ : : : :To Unsubscribe: send mail to [EMAIL PROTECTED] :with unsubscribe freebsd-current in the body of the message : -- Andrew R. Reiter [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message