> You forgot to pass it through ksymoops.
>
> But I can tell that the device won't work if the oops is fixed.
> The root cause is a firmware lockup.
>
> -- Pete
Sorry about that. I passed it through now, but I guess its just more of the
same.
Since this has been happening to me on two different
Hi all,
with the 2.4.23 kernel the FX2 is no longer able to
enumerate in high speed mode. In full speed mode everything
is fine. Any suggestions where I could have a look to
suggest a patch?
/Bernd
Dec 20 12:05:14 snoopy kernel: hub.c: new USB device
00:10.3-1, assigned address 13
Dec 20 12:
Seems like the essence of as163 is to shift costs around a bit,
using device_register (instead of device_initialize + device_add)
because interface->dev.complete only fires on paths where the
refcount goes to zero ... and since that's the only mechanism
provided in the driver core to handle problem
!!! GREEN CARD BASVURU SISTEMI TAMAMEN DEGISTI !!! ---
ABD Gocmenlik Burosu'nun tum dunyaya yaptigi resmi aciklamaya gore,
bu yil DV-2005 basvurulari sadece internet uzerinden yapilabilecek,
kesinlikle mektupla basvuru kabul edilmeyecek.
Bu sene Turkiye'den yaklasik 4,000 kisi
> Try this. I haven't got a patch for you, but you can easily make the
> change by hand.
>
> In the kernel source file drivers/usb/storage/scsiglue.c, somewhere around
> lines 315 to 330, you'll see a couple of lines that say:
>
> /* limit the total size of a transfer to 120 KB */
> .m
On Sat, Dec 20, 2003 at 12:06:17PM +0100, [EMAIL PROTECTED] wrote:
> > You forgot to pass it through ksymoops.
> >
> > But I can tell that the device won't work if the oops is fixed.
> > The root cause is a firmware lockup.
> Sorry about that. I passed it through now, but I guess its just more of
On Fri, Dec 19, 2003 at 05:52:00PM -0800, David Mosberger wrote:
> The ipaq USB driver in 2.6.0 didn't work for me. I got the attached
> "Badness in local_bh_enable" backtrace when ppp tried to connect to my
> iPaq. The quick and dirty patch to avoid the problem is this patch:
See Paul's patch o
On Sat, 20 Dec 2003, David Brownell wrote:
> Seems like the essence of as163 is to shift costs around a bit,
> using device_register (instead of device_initialize + device_add)
> because interface->dev.complete only fires on paths where the
> refcount goes to zero ... and since that's the only mec
