public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johny <kernel@agotnes.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Johny <kernel@agotnes.com>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-acpi@kernel.org, akpm@osdl.org
Subject: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues
Date: Sun, 18 Jun 2006 21:37:00 +1000	[thread overview]
Message-ID: <44953ADC.2080305@agotnes.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0606151102220.6879-100000@iolanthe.rowland.org>

All,

I've now tested the following;

2.6.17-rc6-mm2 with the following patch applied;
---
git-acpi.patch from 
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm2/broken-out/
---

With no difference to the end-result.

Next I stripped out 802.11 generic support and acx111 drivers from the 
kernel (including the acpi patches) to check if it clashes, but the same 
errors occur....

Thirdly, I booted with acpi=off on the command line with two kernels, 
the stock 2.6.17-rc6-mm2 (no acpi patch and including acx111) and the 
one including the acpi patch and no acx111, the results were;

acpi_patch;
works a treat, picks up USB devices as expected.

stock;
works a treat, picks up USB devices as expected, and my acx111 card 
works too :)


Now I'm looking for good suggestions again, this definitely looks like 
it is related to ACPI, hence the cc' to that list too, as requested by 
Andrew M.

I'm happy to apply patches / config changes as appropriate and for those 
who may ask for my .config files, please see;

http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2

http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2git-acpi_patch

Also, I left the output of lspci there for reference;

http://www.agotnes.com/kernelStuff/lspci

Cheers,

:)Johny

Alan Stern wrote:
> [Moved to linux-usb-devel in the hope of getting additional help]
> 
> On Thu, 15 Jun 2006, Johny wrote:
> 
>> Alan,
>>
>> See comments interspersed, thanks for your assistance :)
>>
>> Alan Stern wrote:
>>> On Tue, 13 Jun 2006, Johny wrote:
>>>
>>>> Is this best suited to this mailing list?
>>> It's appropriate.
>>>
>>>> I tried the kernel list with zero responses (so far ;), let me know if there is
>>>> anywhere else this should go.
>>> ...
>>>
>>>> Johny Ågotnes wrote:
>>>>> All,
>>>>>
>>>>> My USB hub isn't recognised with the latest -mm series, whereas with
>>>>> 2.6.16 vanilla it is picked up & used immediately.
>>>>>
>>>>> The error I get in dmesg is;
>>>>>
>>>>> hub 4-0:1.0: USB hub found
>>>>> hub 4-0:1.0: 2 ports detected
>>>>> usb 1-4: new high speed USB device using ehci_hcd and address 3
>>>>> ehci_hcd 0000:00:10.3: Unlink after no-IRQ?  Controller is probably
>>>>> using the wrong IRQ.
>>> That last line is a clue.  What interrupt numbers are assigned under
>>> 2.6.16?  If you unplug the SonyEricsson DCU-11 Cable before booting (and
>>> leave it unplugged), what shows up in /proc/interrupts for both versions
>>> of the kernel?
>> See attached, both with the DCU-11 cable disconnected.
> 
> From 2.6.16:
>            CPU0       
>   0:      16101          XT-PIC  timer
>   1:        148          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   7:          0          XT-PIC  parport0
>   9:          0          XT-PIC  acpi
>  10:        151          XT-PIC  ehci_hcd:usb1, uhci_hcd:usb4
>  11:          0          XT-PIC  uhci_hcd:usb2, uhci_hcd:usb3
>  12:        138          XT-PIC  i8042
>  14:        172          XT-PIC  ide0
>  15:       2458          XT-PIC  ide1
> NMI:          0 
> ERR:          0
> 
> From 2.6.17:
>            CPU0       
>   0:      35651    XT-PIC-level    timer
>   1:        129    XT-PIC-level    i8042
>   2:          0    XT-PIC-level    cascade
>   6:          3    XT-PIC-level    floppy
>   7:          0    XT-PIC-level    parport0
>   9:          0    XT-PIC-level    acpi
>  10:          0    XT-PIC-level    ehci_hcd:usb1, uhci_hcd:usb4
>  11:       1940    XT-PIC-level    uhci_hcd:usb2, uhci_hcd:usb3, wlan0
>  12:        162    XT-PIC-level    i8042
>  14:        171    XT-PIC-level    ide0
>  15:       4251    XT-PIC-level    ide1
> NMI:          0 
> ERR:          0
> 
> There's nothing obviously wrong.
> 
>>> Most likely this is a problem with the ACPI subsystem, not a USB problem.
>>>
>> I guessed USB due to the number of USB changes in the -mm series and, 
>> obviously, my USB devices stopped registering, however, I'd not know one 
>> from the other ;)
> 
> What happens if you boot with "acpi=off" on the boot command line?
> 
> Alan Stern
> 

           reply	other threads:[~2006-06-18 11:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.44L0.0606151102220.6879-100000@iolanthe.rowland.org>]

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=44953ADC.2080305@agotnes.com \
    --to=kernel@agotnes.com \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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