Hi!
In 2.6.0-test4, USB ELSA modem no longer works. This is UHCI (on
toshiba 4030cdt).
Relevant messages seem to be:
PM: Adding info for usb:1-1.2
drivers/usb/class/cdc-acm.c: need inactive config#2
PM: Adding info for usb:1-1.2:0
drivers/usb/class/cdc-acm.c: need inactive config#2
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
Hi!
> > In 2.6.0-test4, USB ELSA modem no longer works. This is UHCI (on
> > toshiba 4030cdt).
> >
> > Relevant messages seem to be:
> >
> > PM: Adding info for usb:1-1.2
> > drivers/usb/class/cdc-acm.c: need inactive config#2
> > PM: Adding info for usb:1-1.2:0
> > drivers/usb/class/cdc-acm.c: need inactive config#2
>
> And this worked just fine in 2.6.0-test3?
It worked okay in 2.5.62, and probably in many later versions, but I'm
not sure if I specificaly tested it with -test3.
Pavel
--
Horseback riding is like software...
...vgf orggre jura vgf serr.
On Wed, Sep 03, 2003 at 09:17:01PM +0200, Pavel Machek wrote:
> Hi!
>
> In 2.6.0-test4, USB ELSA modem no longer works. This is UHCI (on
> toshiba 4030cdt).
>
> Relevant messages seem to be:
>
> PM: Adding info for usb:1-1.2
> drivers/usb/class/cdc-acm.c: need inactive config#2
> PM: Adding info for usb:1-1.2:0
> drivers/usb/class/cdc-acm.c: need inactive config#2
And this worked just fine in 2.6.0-test3?
thanks,
greg k-h
On Thu, Sep 04, 2003 at 12:44:12AM +0200, Pavel Machek wrote:
> Hi!
>
> > > In 2.6.0-test4, USB ELSA modem no longer works. This is UHCI (on
> > > toshiba 4030cdt).
> > >
> > > Relevant messages seem to be:
> > >
> > > PM: Adding info for usb:1-1.2
> > > drivers/usb/class/cdc-acm.c: need inactive config#2
> > > PM: Adding info for usb:1-1.2:0
> > > drivers/usb/class/cdc-acm.c: need inactive config#2
> >
> > And this worked just fine in 2.6.0-test3?
>
> It worked okay in 2.5.62, and probably in many later versions, but I'm
> not sure if I specificaly tested it with -test3.
2.5.62??? You are going to have to help narrow it down a bit more :)
thanks,
greg k-h
Pavel Machek wrote:
> Hi!
>
> In 2.6.0-test4, USB ELSA modem no longer works. This is UHCI (on
> toshiba 4030cdt).
>
> Relevant messages seem to be:
>
> PM: Adding info for usb:1-1.2
> drivers/usb/class/cdc-acm.c: need inactive config#2
> PM: Adding info for usb:1-1.2:0
> drivers/usb/class/cdc-acm.c: need inactive config#2
Try the usb_set_configuration() patch I just posted this morning
(to linux-usb-devel).
Apply it, and you'll still get these messages ... but then you'll
be able to
# echo 2 > /sys/bus/usb/devices/1-1.2/bConfigurationValue
and then it should work as before. Granted that works as I expect,
I'll submit a cdc-acm patch later to get rid of the need for the
manual workaround. And meanwhile, a hotplug script could automate
this for you, in /etc/hotplug/usb/cdc-acm ...
- Dave
Greg KH wrote:
> 2.5.62??? You are going to have to help narrow it down a bit more :)
It worked fine in 2.5.75 too. I have the same problem as Pavel, with
a different USB modem in -test4.
-- Jamie
On Thu, Sep 04, 2003 at 10:24:17PM +0100, Jamie Lokier wrote:
> Greg KH wrote:
> > 2.5.62??? You are going to have to help narrow it down a bit more :)
>
> It worked fine in 2.5.75 too. I have the same problem as Pavel, with
> a different USB modem in -test4.
Again, that was a while ago. Care to help narrow it down some?
thanks,
greg k-h
Jamie Lokier wrote:
> Greg KH wrote:
>
>>2.5.62??? You are going to have to help narrow it down a bit more :)
>
>
> It worked fine in 2.5.75 too. I have the same problem as Pavel, with
> a different USB modem in -test4.
And ... does my suggestion to Pavel then improve things?
http://marc.theaimsgroup.com/?l=linux-kernel&m=106263361810553&w=2
referring to this patch
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106260875713372&w=2
Same symptoms should in this case mean same fix ...
- Dave
David Brownell wrote:
> >It worked fine in 2.5.75 too. I have the same problem as Pavel, with
> >a different USB modem in -test4.
>
> And ... does my suggestion to Pavel then improve things?
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106263361810553&w=2
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106260875713372&w=2
Yes it does.
When loading the controller, these are some of the messages:
PM: Adding info for usb:1-1:0
PM: Adding info for usb:1-1:1
drivers/usb/class/cdc-acm.c: need inactive config #2
drivers/usb/class/cdc-acm.c: need inactive config #2
On loading cdc_acm:
usb 1-1: control timeout on ep0in
When I do the echo 2 >/sys/bus/usb/devices/1-1/bConfigurationValue:
acm: probe of 1-1:1 failed with error -5
I am able to open the modem device and use it after the echo, and not
before. (I'm using it now).
> I'll submit a cdc-acm patch later to get rid of the need for the
> manual workaround. And meanwhile, a hotplug script could automate
> this for you, in /etc/hotplug/usb/cdc-acm ...
So many other things don't work automatically for me in 2.6 that one
little echo for cdc_acm is a little thing. Besides, hotplug doesn't
work either - something about the arguments to /sbin/hotplug has
changed since 2.4 and I am in no rush to install a new version.
Thanks for the modem fix. I can now test the futex bug without going
offline :)
Cheers,
-- Jamie
On Sat, Sep 06, 2003 at 05:02:00PM +0100, Jamie Lokier wrote:
>
> So many other things don't work automatically for me in 2.6 that one
> little echo for cdc_acm is a little thing. Besides, hotplug doesn't
> work either - something about the arguments to /sbin/hotplug has
> changed since 2.4 and I am in no rush to install a new version.
Sorry, but if you want hotplug to work in 2.6, you will have to install
a new version due to some changes to the network arguments, and due to a
bug in the older versions of the scripts.
thanks,
greg k-h
On Sat, Sep 06, 2003 at 10:44:18AM -0700, Greg KH wrote:
> On Sat, Sep 06, 2003 at 05:02:00PM +0100, Jamie Lokier wrote:
> >
> > So many other things don't work automatically for me in 2.6 that one
> > little echo for cdc_acm is a little thing. Besides, hotplug doesn't
> > work either - something about the arguments to /sbin/hotplug has
> > changed since 2.4 and I am in no rush to install a new version.
>
> Sorry, but if you want hotplug to work in 2.6, you will have to install
> a new version due to some changes to the network arguments, and due to a
> bug in the older versions of the scripts.
What release date should the hotplug scripts be? I still have that hotplug
related oops that I told you about a while ago...
On Sun, Sep 07, 2003 at 11:20:28PM -0700, Mike Fedyk wrote:
> On Sat, Sep 06, 2003 at 10:44:18AM -0700, Greg KH wrote:
> > On Sat, Sep 06, 2003 at 05:02:00PM +0100, Jamie Lokier wrote:
> > >
> > > So many other things don't work automatically for me in 2.6 that one
> > > little echo for cdc_acm is a little thing. Besides, hotplug doesn't
> > > work either - something about the arguments to /sbin/hotplug has
> > > changed since 2.4 and I am in no rush to install a new version.
> >
> > Sorry, but if you want hotplug to work in 2.6, you will have to install
> > a new version due to some changes to the network arguments, and due to a
> > bug in the older versions of the scripts.
>
> What release date should the hotplug scripts be? I still have that hotplug
> related oops that I told you about a while ago...
Try the latest :)
But that oops should have nothing to do with the scripts, that's a
kernel oops that I could never duplicate :(
thanks,
greg k-h
On Mon, Sep 08, 2003 at 09:06:31AM -0700, Greg KH wrote:
> On Sun, Sep 07, 2003 at 11:20:28PM -0700, Mike Fedyk wrote:
> > On Sat, Sep 06, 2003 at 10:44:18AM -0700, Greg KH wrote:
> > > On Sat, Sep 06, 2003 at 05:02:00PM +0100, Jamie Lokier wrote:
> > > >
> > > > So many other things don't work automatically for me in 2.6 that one
> > > > little echo for cdc_acm is a little thing. Besides, hotplug doesn't
> > > > work either - something about the arguments to /sbin/hotplug has
> > > > changed since 2.4 and I am in no rush to install a new version.
> > >
> > > Sorry, but if you want hotplug to work in 2.6, you will have to install
> > > a new version due to some changes to the network arguments, and due to a
> > > bug in the older versions of the scripts.
> >
> > What release date should the hotplug scripts be? I still have that hotplug
> > related oops that I told you about a while ago...
>
> Try the latest :)
>
> But that oops should have nothing to do with the scripts, that's a
> kernel oops that I could never duplicate :(
Are the kksymoops reports parsable by the userspace ksymoops? Whenever I
run the 2.6 kernel resolved oops through the user space ksymoops, it points
to a different part of the kernel, leading me to suspect that i shouldn't be
doing that.
Is that right? Also I use modules a lot, will that affect this?
I'd like to get this fixed. Any instructions / patches would be helpful.