All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Matthias <espi@epost.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ACM USB modem on Kernel 2.6.0-test
Date: Mon, 20 Oct 2003 18:54:56 +0200	[thread overview]
Message-ID: <0141nb.o9.ln@127.0.0.1> (raw)
In-Reply-To: Inm6.60T.19@gated-at.bofh.it

David Brownell schrieb:

>>>> In fact, here's a patch with that very change.  Does
>>>> it make current 2.6.0-test kernels work "out of the box"
>>>> again with your USB modems?
>>> 
>>> Yes, it works with ELSA Microlink USB. Thanks.
>> 
>> Hmm. Too early. I get either a "acm: probe of 3-3:2.1 failed with error
-5"
>> but it works or a 
>> Unable to handle kernel NULL pointer dereference at virtual address
00000008
>>  ...
>>  EIP:    0060:[usb_driver_claim_interface+67/112]    Tainted: P
>>  ...
> 
> Well, the "it works at all (without the sysfs write)" is
> what that patch was about -- so it's still a clear win!
> 
> But cdc-acm probe() is pretty broken, and I'm told it's
> had strange behavior in various other cases for a while,
> including some oopsing.  Like this; not a new bug.
> 
> Try this cdc-acm patch.  One user reported that it made
> oopsing go away, the bogus probe() errors stopped, and
> even the /proc/bus/usb/devices listings were finally
> right (both interfaces now claimed by cdc_acm).  Plus
> it should stop the pointless hotplugging of "cdc_acm"
> for Ethernet devices (including MSFT's RNDIS).

Yes, it works. I hope it will be integrated in 2.6.0.

Peter


  parent reply	other threads:[~2003-10-20 16:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FwYB.Z9.25@gated-at.bofh.it>
2003-10-12  8:40 ` ACM USB modem on Kernel 2.6.0-test Peter Matthias
2003-10-12 12:06   ` Jamie Lokier
2003-10-12 17:52 ` Peter Matthias
2003-10-13 16:28 ` Peter Matthias
     [not found] ` <HJ5m.2Eb.23@gated-at.bofh.it>
2003-10-18 16:21   ` Peter Matthias
     [not found]   ` <Inm6.60T.19@gated-at.bofh.it>
2003-10-20 16:54     ` Peter Matthias [this message]
     [not found] <FJVJ.4PN.5@gated-at.bofh.it>
     [not found] ` <I1Yg.6oy.13@gated-at.bofh.it>
     [not found]   ` <I1Yg.6oy.11@gated-at.bofh.it>
2003-10-19  9:34     ` Peter Matthias
2003-10-11 18:53 David Brownell
2003-10-12 12:07 ` Jamie Lokier
2003-10-12 18:59   ` David Brownell
2003-10-17 20:04 ` David Brownell
2003-10-19 15:13   ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2003-10-11 12:38 Peter Matthias

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0141nb.o9.ln@127.0.0.1 \
    --to=espi@epost.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.