Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)

From: Alan Stern
Date: Mon Oct 20 2008 - 10:02:37 EST


On Sun, 19 Oct 2008, Justin Piszcz wrote:

> > You should turn on the usbfs_snoop module parameter for usbcore and see
> > what shows up in the system log.
>
> > Alan Stern
>
> Tried this, kernel would not boot up any further when I had that enabled
> alongside the 'extra' debugging options in the kernel:
>
> http://home.comcast.net/~jpiszcz/20081019/2.6.27.2-usb-extra-debug.txt

I'm not interested in your config file; I need to see the dmesg log.

> > Please get sysrq-t of a hang.
> >
> > Regards
> > Oliver
> >
>
> Before I tried the above, I was able to get a sysrq-t of the hang:
>
> http://home.comcast.net/~jpiszcz/20081019/trace_before_trigger.txt
> http://home.comcast.net/~jpiszcz/20081019/trace_after_trigger.txt

Your trace is incomplete. You might need to increase the size of the
kernel log buffer (CONFIG_LOG_BUF_SHIFT) or the size of the buffer used
by dmesg (the -s option).

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/