Issue 251: Panic on -current - DragonFly issue tracker

Created on 2006-07-19.22:14:07 by wa1ter, last changed by justin.

Messages
msg1423 (view)	Author: dillon	Date: 2006-10-04.23:09:00
:Yes, there is a USB scanner plugged in, and I never unplugged it. : :What is a VCHR device? Its just the #define used to identify a CHR device, which is basically everything in /dev. In anycase, the latest HEAD should fix the issue. I'm guessing that one of those GUI programs is revoke()ing access to the device while another one has an open descriptor to it and then tries to mmap() it. -Matt Matthew Dillon <dillon@backplane.com>
msg1422 (view)	Author: wa1ter	Date: 2006-10-04.23:05:01
Yes, there is a USB scanner plugged in, and I never unplugged it. What is a VCHR device?
msg1419 (view)	Author: dillon	Date: 2006-10-04.18:25:01
I think the descriptor might have gotten revoked with revoke(). Since it is a VCHR device, that would have succeeded. But mmap() doesn't have the correct check for a revoked device descriptor so I will go ahead and add the check. -Matt Matthew Dillon <dillon@backplane.com>
msg1418 (view)	Author: dillon	Date: 2006-10-04.18:08:00
It crashed on a NULL pointer indirection trying to mmap() ucanner0. Do you have a USB scanner connected? I can do a NULL check easily enough but it should not have been able to open a descriptor in the first place if there was no scanner. Or, if there was a scanner, maybe it got unplugged at some point before the mmap (though that shouldn't have NULLed out the field either). -Matt Matthew Dillon <dillon@backplane.com>
msg1417 (view)	Author: dillon	Date: 2006-10-04.18:00:01
:Yes. I should mention that I posted a different bug with :the same title on 9-23-2006 which is not yet fixed. I'll get the second one fixed right now. I see your core on leaf. -Matt Matthew Dillon <dillon@backplane.com>
msg1385 (view)	Author: wa1ter	Date: 2006-10-02.15:38:01
Simon 'corecode' Schubert wrote: > Simon 'corecode' Schubert <corecode@fs.ei.tum.de> added the comment: > > Is this fixed? > > _______________________________________________________ > DragonFly issue tracker <issues@chlamydia.fs.ei.tum.de> > <http://bugs.dragonflybsd.org/issue251> > _______________________________________________________ Yes. I should mention that I posted a different bug with the same title on 9-23-2006 which is not yet fixed.
msg1380 (view)	Author: corecode	Date: 2006-10-02.14:06:19
Is this fixed?
msg956 (view)	Author: dillon	Date: 2006-07-20.23:52:03
:I've had two more to sudden reboots, one after >5hrs of KDE usage and one :after a few minutes. : :Thomas Try HEAD as of today. I committed a fix a little earlier in the day. -Matt Matthew Dillon <dillon@backplane.com>
msg955 (view)	Author: schlesinger	Date: 2006-07-20.20:26:02
Am Donnerstag, 20. Juli 2006 16:24 schrieb Thomas Schlesinger: > Am Donnerstag, 20. Juli 2006 00:08 schrieb walt: > > I updated world/kernel this morning and all seemed good until > > I exited from my gnome X session. Here is what kgdb says: > > > > (kgdb) bt > > #0 lwkt_switch () at thread2.h:177 > > #1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad > > address. ) at /usr/src/sys/i386/i386/trap.c:349 > > Previous frame inner to this frame (corrupt stack?) > > I've updated the kernel yesterday, too, and my machine rebooted while > working in a KDE session. Unfortunately, I do not have more informations. > Maybe it's the same as walt's problem. > > Thomas I've had two more to sudden reboots, one after >5hrs of KDE usage and one after a few minutes. Thomas
msg954 (view)	Author: dillon	Date: 2006-07-20.20:23:02
:.. :> : :> :Definitely, but not immediately after a reboot -- I need to mess :> :around for awhile in an X session, and then exit from X. :> :> I need the kernel binary as well. : :Done. I already deleted /var/crash/* so I sent /kernel instead. Fixed. My VOP vector cleanup indirected through a mount point without checking to see if the vnode was dead or not. -Matt Matthew Dillon <dillon@backplane.com>
msg951 (view)	Author: wa1ter	Date: 2006-07-20.17:29:03
On Thu, 20 Jul 2006, Matthew Dillon wrote: > > :It's in my crash directory on leaf. > : > :> Is it repeatable ? > : > :Definitely, but not immediately after a reboot -- I need to mess > :around for awhile in an X session, and then exit from X. > > I need the kernel binary as well. Done. I already deleted /var/crash/* so I sent /kernel instead.
msg945 (view)	Author: dillon	Date: 2006-07-20.15:34:02
:It's in my crash directory on leaf. : :> Is it repeatable ? : :Definitely, but not immediately after a reboot -- I need to mess :around for awhile in an X session, and then exit from X. I need the kernel binary as well. -Matt Matthew Dillon <dillon@backplane.com>
msg944 (view)	Author: schlesinger	Date: 2006-07-20.14:30:02
Am Donnerstag, 20. Juli 2006 00:08 schrieb walt: > I updated world/kernel this morning and all seemed good until > I exited from my gnome X session. Here is what kgdb says: > > (kgdb) bt > #0 lwkt_switch () at thread2.h:177 > #1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad > address. ) at /usr/src/sys/i386/i386/trap.c:349 > Previous frame inner to this frame (corrupt stack?) I've updated the kernel yesterday, too, and my machine rebooted while working in a KDE session. Unfortunately, I do not have more informations. Maybe it's the same as walt's problem. Thomas
msg942 (view)	Author: wa1ter	Date: 2006-07-20.01:05:07
Matthew Dillon wrote: > :I updated world/kernel this morning and all seemed good until > :I exited from my gnome X session. Here is what kgdb says: > : > :(kgdb) bt > :#0 lwkt_switch () at thread2.h:177 > :#1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad address. > :) at /usr/src/sys/i386/i386/trap.c:349 > :Previous frame inner to this frame (corrupt stack?) > > Hmm. Upload the core, I might be able to salvage it. It's in my crash directory on leaf. > Is it repeatable ? Definitely, but not immediately after a reboot -- I need to mess around for awhile in an X session, and then exit from X.
msg941 (view)	Author: dillon	Date: 2006-07-19.22:43:02
:I updated world/kernel this morning and all seemed good until :I exited from my gnome X session. Here is what kgdb says: : :(kgdb) bt :#0 lwkt_switch () at thread2.h:177 :#1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad address. :) at /usr/src/sys/i386/i386/trap.c:349 :Previous frame inner to this frame (corrupt stack?) Hmm. Upload the core, I might be able to salvage it. Is it repeatable ? -Matt Matthew Dillon <dillon@backplane.com>
msg940 (view)	Author: wa1ter	Date: 2006-07-19.22:14:03
I updated world/kernel this morning and all seemed good until I exited from my gnome X session. Here is what kgdb says: (kgdb) bt #0 lwkt_switch () at thread2.h:177 #1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad address. ) at /usr/src/sys/i386/i386/trap.c:349 Previous frame inner to this frame (corrupt stack?)

History
Date	User	Action	Args
2006-12-12 04:32:38	justin	set	status: chatting -> resolved
2006-10-04 23:09:01	dillon	set	messages: + msg1423
2006-10-04 23:05:02	wa1ter	set	messages: + msg1422
2006-10-04 18:25:01	dillon	set	messages: + msg1419
2006-10-04 18:08:00	dillon	set	messages: + msg1418
2006-10-04 18:00:01	dillon	set	status: resolved -> chatting messages: + msg1417
2006-10-02 17:17:48	corecode	set	status: chatting -> resolved
2006-10-02 15:38:01	wa1ter	set	messages: + msg1385
2006-10-02 14:06:19	corecode	set	messages: + msg1380
2006-10-01 02:12:45	admin	set	nosy: + wa1ter
2006-07-20 23:52:05	dillon	set	messages: + msg956
2006-07-20 20:26:05	schlesinger	set	messages: + msg955
2006-07-20 20:23:04	dillon	set	messages: + msg954
2006-07-20 17:29:05	wa1ter	set	messages: + msg951
2006-07-20 17:24:56	corecode	set	priority: bug
2006-07-20 15:34:04	dillon	set	messages: + msg945
2006-07-20 14:30:06	schlesinger	set	messages: + msg944
2006-07-20 01:05:14	wa1ter	set	messages: + msg942
2006-07-19 22:43:04	dillon	set	status: unread -> chatting messages: + msg941
2006-07-19 22:14:07	wa1ter	create

Issue251