On Wednesday 05 January 2005 18:12, David Brownell wrote:
> On Wednesday 05 January 2005 3:58 am, Pedro Venda wrote:
> > David Brownell wrote:
> > | OK, try this slightly modified version. Looks like
> > | the Intel chip sets the HALT bit then spontaneously
> > | clears it, while the ALI may never
On Wednesday 05 January 2005 3:58 am, Pedro Venda wrote:
> David Brownell wrote:
> |
> | OK, try this slightly modified version. Looks like
> | the Intel chip sets the HALT bit then spontaneously
> | clears it, while the ALI may never set it.
>
> this one has a different output, although I don't
On Wednesday 05 January 2005 6:40 am, Christian Iversen wrote:
> I've been running with this patch for some time now (well, at least 10 days),
> and I haven't had any problems of any kind. USB just seems to work for me
> now. Of course, that could be pure luck, but since David and I looked at
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Iversen wrote:
| On Wednesday 05 January 2005 12:58, Pedro Venda wrote:
|
|>David Brownell wrote:
|>| On Tuesday 04 January 2005 4:31 am, Pedro Venda wrote:
|>|>David Brownell wrote:
|>|>| On Monday 03 January 2005 5:05 pm, you wrote:
|>|>|>Da
On Wednesday 05 January 2005 12:58, Pedro Venda wrote:
> David Brownell wrote:
> | On Tuesday 04 January 2005 4:31 am, Pedro Venda wrote:
> |>David Brownell wrote:
> |>| On Monday 03 January 2005 5:05 pm, you wrote:
> |>|>David Brownell wrote:
> |>|>| It's something wierd that started a while back,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Brownell wrote:
| On Tuesday 04 January 2005 4:31 am, Pedro Venda wrote:
|
|>David Brownell wrote:
|>| On Monday 03 January 2005 5:05 pm, you wrote:
|>|
|>|>David Brownell wrote:
|>|>| It's something wierd that started a while back, and so far
|>|
On Tuesday 04 January 2005 4:31 am, Pedro Venda wrote:
> David Brownell wrote:
> | On Monday 03 January 2005 5:05 pm, you wrote:
> |
> |>David Brownell wrote:
> |>| It's something wierd that started a while back, and so far
> |>| it doesn't make sense to me. But see below, and please
> |>| try the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Brownell wrote:
| On Monday 03 January 2005 5:05 pm, you wrote:
|
|>David Brownell wrote:
|>| It's something wierd that started a while back, and so far
|>| it doesn't make sense to me. But see below, and please
|>| try the patch I've attached.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Brownell wrote:
| It's something wierd that started a while back, and so far
| it doesn't make sense to me. But see below, and please
| try the patch I've attached. If it fails, please send
| the full CONFIG_USB_DEBUG output showing the error (a
On Monday 03 January 2005 12:49 pm, David Brownell wrote:
> It's something wierd that started a while back, and so far
> it doesn't make sense to me. But see below, and please
> try the patch I've attached.
And it _still_ doesn't make sense to me -- why should any
chip issue bogus "fatal" error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pedro Venda wrote:
| hi everyone,
|
| just subscribed.
|
| I'm using an ACER travelmate 4001WLMi and someone showed me that it has
| some
| problems with the ehci usb driver.
|
| without debug, i get the following:
|
| Dec 20 00:41:04 archon ehci_hcd 00
It's something wierd that started a while back, and so far
it doesn't make sense to me. But see below, and please
try the patch I've attached. If it fails, please send
the full CONFIG_USB_DEBUG output showing the error (as
below) and contents of /sys/class/usb_host/usb4/registers
after the fault.
On Mon, 01 Mar 2004 21:40:58 +0100
bastian roessler <[EMAIL PROTECTED]> wrote:
> but the speed was very low and then i saw that only usb-uhci was loaded.
> so i recompiled my kernel with ehci-hcd support and then everything went
> fine, too. but suddenly, when i tryed to get more traffic on the hd
Stefan Neuwirth wrote:
>
> 2.4.21-rc7-ac1...
Yes, some very important EHCI patches never made it into
the 2.4.21 tree. I've reposted them a few times, and
they're in Greg's USB tree, ready to appear as soon
as 2.4.22-pre starts.
- Dave
-
[EMAIL PROTECTED] writes:
> Quoting Stefan Neuwirth <[EMAIL PROTECTED]>:
>
> > when loading usb-uhci (2.4.21-rc7-ac1) my 6in1 cardreader (bcm 3230,
> > Vendor-ID 0x0aec,
> > Produkt-ID 0x3050) is present. It's listed in /proc/bus/ucb/devices:
>
> This is how the device presented itself for iden
Quoting Stefan Neuwirth <[EMAIL PROTECTED]>:
> Hi there,
>
> when loading usb-uhci (2.4.21-rc7-ac1) my 6in1 cardreader (bcm 3230,
> Vendor-ID 0x0aec,
> Produkt-ID 0x3050) is present. It's listed in /proc/bus/ucb/devices:
This is how the device presented itself for identification,
Spd=12, bus-p
On Tue, Oct 08, 2002 at 11:26:21PM +0200, Martin Diehl wrote:
> - modprobe ehci-hcd: works just fine without a problem
> - rmmod ehci-hcd
There's a problem right now with unloading usb host controller drivers
in that the root hub isn't getting properly cleaned up from driverfs.
This causes a prob
> I assume you are merely refering to the detailed init-script activities
> than to particular runlevel. I don't have the ehci-hcd included anywhere
> for automated loading. So the system came up with usbcore and ohci-hcd
> loaded. I've rmmod'ed the ohci-hcd and modprobed the ehci-hcd which wa
On Mon, 7 Oct 2002, David Brownell wrote:
> It looks exactly like the oops I've seen sometimes when re-initializing
> a host controller after rmmod ... usually ohci, since that's what I
> was testing when I saw that. Curious that you see it even before
> that first initialization, that changing
On Mon, Oct 07, 2002 at 04:00:55PM -0700, David Brownell wrote:
>
> I've seen a _lot_ of usbfs or driverfs problems in 2.5.40. So many
> that I've stopped trying to use a CardBus adapter -- too many things
> want to oops for me -- or unplugging/replugging USB devices more than
> a couple times b
Martin Diehl wrote:
> Maybe it's not expected to work this way - but if so, it should return
> error, not crash when ehci-hcd is loaded befor ohci-hcd. If I load
> ohci-hcd first, it's all working fine.
>
> After this the ehci-hcd module gets stuck unremoveable in module-init,
> but the box rem
> I forgot to mention that most of the debugging steps you suggested had
> already been applied - USB debug, USB storage debug, DEBUG_KERNEL,
> DEBUG_SLAB, DEBUG_IOVIRT. None of these alters the failure mode in any
> perceptible way.
OK, that's useful to know. The first several wouldn't aff
David Brownell wrote:
> I'll repeat that advice here ... you're not yet providing usable info
> about your failure mode, unfortunately!
Indeed! I wish I had something useful to say about the failure mode,
other than (A) it triggers an instant reboot, and (B) it only occurs
when transfering b
Kristofer T. Karas wrote:
> I sent a bug report some time ago to linux-kernel about the EHCI-HCD
> driver triggering an instant reboot. Greg KH suggested I post something
> here. Then I got side-tracked; well, finally...
I remember replying to your post, suggesting that you try a few
things fir
> > Please recommend one or two EHCI/USB 2.0 host-controllers
> > that you'd like more test converage on. I can see about buying
> > them online.
>
> Basically, any PCI card now sold as supporting "high speed USB"
> (with the red/blue logo) is going to have a NEC chip with a recent
> stepping, a
> I'd prefer to do USB 2.0 in the -ac tree or 2.5 and leave the Linus kernel
> tree USB 1.1 for now.
Actually the hub/infrastructure changes do seem quite safe (more so
than some changes that did get into 2.4.4 :) so it'd seem reasonable
to get those into Linus tree. Not essential, of course, bu
> > Related: USB 2.0 host controllers are in stores. Fry's lists
> > them for $50 (and up :), and they work fine with usb-ohci
> > (at "full" and "low" speeds) even if the "high speed" EHCI
> > support is still in development.
>
> I live in Seattle and have no Fry's Electronics to go to.
Well,
Brad Hards wrote:
>
> David Brownell wrote:
> >
> > > > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
> > > >
> > > > Yep, I think I got that problem that'd been so annoying. With
> > > > current CVS and a prototype USB 2.0 storage device, this now
> > > > hotplugs usb-storage
David Brownell wrote:
> Related: USB 2.0 host controllers are in stores. Fry's lists
> them for $50 (and up :), and they work fine with usb-ohci
> (at "full" and "low" speeds) even if the "high speed" EHCI
> support is still in development.
I live in Seattle and have no Fry's Electronics to go
On Sun, May 06, 2001, Brad Hards <[EMAIL PROTECTED]> wrote:
> > > We still need -ac patches, right? Maybe that hub code for USB 2.0 needs to go
> > > into 2.4.5?
> >
> > I'd like to see that (and the usbdevfs update too) go in before long,
> > but one can't quite argue it as a bugfix ... :)
>
>
David Brownell wrote:
>
> > > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
> > >
> > > Yep, I think I got that problem that'd been so annoying. With
> > > current CVS and a prototype USB 2.0 storage device, this now
> > > hotplugs usb-storage ... usb-storage gets past its firs
> > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
> >
> > Yep, I think I got that problem that'd been so annoying. With
> > current CVS and a prototype USB 2.0 storage device, this now
> > hotplugs usb-storage ... usb-storage gets past its first bulk request,
> > hangs on the s
David Brownell wrote:
>
> > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
>
> Yep, I think I got that problem that'd been so annoying. With
> current CVS and a prototype USB 2.0 storage device, this now
> hotplugs usb-storage ... usb-storage gets past its first bulk request,
> h
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
Yep, I think I got that problem that'd been so annoying. With
current CVS and a prototype USB 2.0 storage device, this now
hotplugs usb-storage ... usb-storage gets past its first bulk request,
hangs on the second, and then gets u
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-usb/hcd/
Thanks! I have a bunch of changes that I'll start putting back
there; having the ability to do more incremental changes is a
Good Thing, and will help move things forward.
- Dave
__
35 matches
Mail list logo
