Two changes, one big one not:
- check before traversing a null pointer, removing oops
- always do bandwidth checks, no point in allowing overcommit
That oops possibility has been there for a bit over two months,
but something changed recently which made me see it. Maybe
sme other folk have see
> - it's called after usblp_write() did an illegal (racey) thing, looking
> at urb->status outside the completion function. (does anyone know
> why usblp_write() isn't just issuing a single write for that buffer?)
It's safe because we previously check for wcomplete==1.
The completion h
On Fri, Nov 01, 2002 at 01:06:43AM +0100, Pedro Lopez-Cabanillas wrote:
> Hi,
>
> On Tuesday 29 October 2002 23:14, Lars Doelle wrote:
> > Perhaps, Pedro, you can manage to get a recent 2.5 up enough for a try?
>
> After some compile problems i can finally boot with 2.5.45, but with some more
>
Linus Torvalds wrote:
On Fri, 1 Nov 2002, David Brownell wrote:
Oct 31 22:58:47 tove kernel: drivers/usb/core/message.c: usb_control/bulk_msg: timeout
Oct 31 22:58:47 tove kernel: drivers/usb/host/ohci-dbg.c: UNLINK dc8e2b1c dev:4,ep=0-I,CTRL,flags:0,len:0/1,stat:-2
Oct 31 22:58:47 tove kerne
On Fri, 1 Nov 2002, David Brownell wrote:
>
> >>Oct 31 22:58:47 tove kernel: drivers/usb/core/message.c: usb_control/bulk_msg:
>timeout
> >>Oct 31 22:58:47 tove kernel: drivers/usb/host/ohci-dbg.c: UNLINK dc8e2b1c
>dev:4,ep=0-I,CTRL,flags:0,len:0/1,stat:-2
> >>Oct 31 22:58:47 tove k
Did 2.5.44 work, but 2.5.45 not work for the printer?
Nope. That machine ran 2.5.42 (or maybe 41) before that, and failed
similarly. I updated it to BK as of an hour ago, and since it still failed
I did the report. So it's been going on for at least a few weeks.
Ok, so it wasn't a recent thin
Mahlzeit
I'm currently test concurrent usage of multiple USB smart card
readers, currently in a 32 device configuration. I'm doing my
testing with 2.4.20-pre11 because of these kernels I tried out
it is the best working one. The hostcontroller is UHCI and
I am using usb-uhci.
When using these re
On Thu, 31 Oct 2002, Dirk van den Brink Jr wrote:
> My bad, copy/pasted the bits from /var/log/messages, instead of
> /var/log/syslog. Sorry! Along with the ability to program, please add "common
> sense" to the list of things I lack. ;) Please find attached the following
> files:
>
> module.txt -
On Mon, Oct 28, 2002 at 04:13:01PM -0800, Christopher Hoover wrote:
> [ Sorry; this time without patch mangling ... ]
>
>
> Dereferencing hcd.pdev will always oops with SA-. It has to be
> treated as a cookie, not a pointer in any common OHCI HCD code.
>
> Apparently we need a clean way to
