Re: tail -f kernel panic
> In article >[EMAIL PROTECTED]> you >write: > >I found it is quite easy to panic a -current kernel with 2 login windows. > > > >In window 1 do a "tail -f /tmp/world.out" > >In window 2 do a "tail -f /tmp/world.out" > >In window 2 do "^C" to break out of tail -f > >In window 1 do "^C" to break out of tail -f > >The box panic immediately. > > I just commited a fix for this. Yes, no more panic. Thanks. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tail -f kernel panic
In article [EMAIL PROTECTED]> you write: >I found it is quite easy to panic a -current kernel with 2 login windows. > >In window 1 do a "tail -f /tmp/world.out" >In window 2 do a "tail -f /tmp/world.out" >In window 2 do "^C" to break out of tail -f >In window 1 do "^C" to break out of tail -f >The box panic immediately. I just commited a fix for this. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tail -f kernel panic
In article [EMAIL PROTECTED]> you write: >I found it is quite easy to panic a -current kernel with 2 login windows. > >In window 1 do a "tail -f /tmp/world.out" >In window 2 do a "tail -f /tmp/world.out" >In window 2 do "^C" to break out of tail -f >In window 1 do "^C" to break out of tail -f >The box panic immediately. Hmm. I reproduced this here; the panic is in SLIST_REMOVE() when it is removing the second event. Funny enough, this does not happen on -stable. Did something change in the list macros recently that would cause this? -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
tail -f kernel panic
I found it is quite easy to panic a -current kernel with 2 login windows. In window 1 do a "tail -f /tmp/world.out" In window 2 do a "tail -f /tmp/world.out" In window 2 do "^C" to break out of tail -f In window 1 do "^C" to break out of tail -f The box panic immediately. I can't get a coredump at the moment because the kernel just stops while doing the "syncing disks... 7 7"... Maybe it is related to kern/25309? Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc023175a stack pointer = 0x10:0xc8fe5db4 frame pointer = 0x10:0xc8fe5dc0 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 = 347 (tail) trap number = 12 panic: page fault cpuid = 1; lapic.id = boot() called on cpu#1 syncing disks... 7 7 c02312e8 t ufs_advlock c0231310 T ufs_vinit c02313bc t ufs_makeinode c023159c t ufs_missingop c02315b4 t ufs_kqfilter c02316d4 t filt_ufsdetach c02317dc t filt_ufsread c0231808 t filt_ufsvnode c023182c T ufs_vnoperate John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message