Date: Tue, 14 Jan 2003 10:03:16 -0500 From: Anish Mistry <mistry.7@osu.edu> To: Darren Pilgrim <dmp@pantherdragon.org> Cc: freebsd-hackers@freebsd.org Subject: Re: USB hub detach causing panic in 4.7p3 Message-ID: <200301141003.16160.mistry.7@osu.edu> In-Reply-To: <3E23F9A4.9030101@pantherdragon.org> References: <3E23F9A4.9030101@pantherdragon.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 14 January 2003 06:51 am, Darren Pilgrim wrote: > I have a USB hub that's built into my Viewsonic PT775 monitor. The hub= =20 > probes during boot and post-boot attach as follows: >=20 > uhub1: vendor 0x0543 product 0x00ff, class 9/0, rev 1.00/0.00, addr 2 > uhub1: 5 ports with 4 removable, self powered >=20 > The hub is connected and disconnected with the switching on and off of = the=20 > monitor. When the hub is disconnected, whether by unplugging it or tur= ning=20 > off the monitor, I get a panic in 4.7p3 if there are no devices connect= ed to=20 > the hub's downstream ports. If there are devices connected to the=20 > downstream ports, the detach/reattach process works just fine. I only = have=20 > the one hub to test this issue on. I can't say when the problem appear= ed as=20 > I hadn't used FreeBSD with this hub until a few weeks ago, and I hadn't= =20 > turned the monitor off with nothing plugged into its USB ports until th= e=20 > 12th. Here is the console output from the panics caused by disconnecti= ng=20 > the hub: >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual addres =3D 0x3 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc031fe04 > stack pointer =3D 0x10:0xc0250fb0 > frame pointer =3D 0x10:0xc0250fc4 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D Idle > interrupt mask =3D bio > trap number =3D 12 > panic: page fault >=20 >=20 > syncing disks... >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0x30 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc01c2498 > stack pointer =3D 0x10:0xc0250d98 > frame pointer =3D 0x10:0xc0250da0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D Idle > interrupt mask =3D bio > trap number =3D 12 > panic: page fault >=20 > Later on, when I was testing various configurations and boot/plug/unplu= g=20 > patterns to (try to) fix/diagnose the problem, the debug information wa= s=20 > different from the above, but the same for all the panics I induced whi= le=20 > testing. This is the output for those panics: >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual addres =3D 0x3 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc031fe04 > stack pointer =3D 0x10:0xc0250fb0 > frame pointer =3D 0x10:0xc0250fc4 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D Idle > interrupt mask =3D bio > trap number =3D 12 > panic: page fault >=20 >=20 > syncing disks... >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0x30 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc01c2498 > stack pointer =3D 0x10:0xc0250dd0 > frame pointer =3D 0x10:0xc0250dd8 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D Idle > interrupt mask =3D bio > trap number =3D 12 > panic: page fault >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >=20 >=20 Would this PR be related?=20 http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/45579 --=20 Anish Mistry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301141003.16160.mistry.7>