From: Peter Matthias <espi@epost.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ACM USB modem on Kernel 2.6.0-test
Date: Sun, 19 Oct 2003 11:34:38 +0200 [thread overview]
Message-ID: <erltmb.re.ln@127.0.0.1> (raw)
In-Reply-To: I1Yg.6oy.11@gated-at.bofh.it
Peter Matthias schrieb:
> David Brownell schrieb:
>
>> David Brownell wrote:
>>>
>>> Hmm ... maybe usbcore would be better off with a less
>>> naive algorithm for choosing defaults. Like, preferring
>>> configurations without proprietary device protocols.
>>> That'd solve every cdc-acm case, and likely others.
>>
>> 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
printing eip:
c023d9c3
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[usb_driver_claim_interface+67/112] Tainted: P
EFLAGS: 00010202
EIP is at usb_driver_claim_interface+0x43/0x70
eax: c02ffe72 ebx: dddcf200 ecx: 00000004 edx: dddfa2ec
esi: dddfa120 edi: 00000000 ebp: dddce3c0 esp: c15b1dd8
ds: 007b es: 007b ss: 0068
Process khubd (pid: 5, threadinfo=c15b0000 task=ddf8e040)
Stack: c030a460 c02ff409 c02ffe72 00001388 dddcf200 c025141c c033a8e0
dddfa2ec
dddce3c0 dddce3d8 00000007 00000094 dddcf200 00000000 00000020
dddfa120
c1796ac0 c1796ad4 dddddc00 c033a968 c033a900 c033a8e0 dddfa240
c023d713
Call Trace:
[acm_probe+1228/1408] acm_probe+0x4cc/0x580
[usb_probe_interface+115/160] usb_probe_interface+0x73/0xa0
[bus_match+63/112] bus_match+0x3f/0x70
[device_attach+65/160] device_attach+0x41/0xa0
[bus_add_device+91/160] bus_add_device+0x5b/0xa0
[device_add+167/272] device_add+0xa7/0x110
[usb_set_configuration+456/576] usb_set_configuration+0x1c8/0x240
[usb_new_device+690/992] usb_new_device+0x2b2/0x3e0
[hub_port_connect_change+461/816] hub_port_connect_change+0x1cd/0x330
[hub_events+773/848] hub_events+0x305/0x350
[hub_thread+53/224] hub_thread+0x35/0xe0
[default_wake_function+0/48] default_wake_function+0x0/0x30
[hub_thread+0/224] hub_thread+0x0/0xe0
[kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
Code: 8b 41 04 89 54 24 10 89 44 24 0c e8 1d b6 ed ff b8 f0 ff ff
Peter
next parent reply other threads:[~2003-10-19 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
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=erltmb.re.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).