linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Ivo Couckuyt <iv0co@yahoo.co.uk>, linux-usb@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
Date: Fri, 4 Jul 2008 19:56:32 +0200	[thread overview]
Message-ID: <200807041956.34051.chunkeey@web.de> (raw)
In-Reply-To: <486BE592.6040006@yahoo.co.uk>

On Wednesday 02 July 2008 22:31:14 Ivo Couckuyt wrote:

(Please keep the CC if you want to answer, Thanks!)

> Chr wrote:
> > On Wednesday 02 July 2008 19:07:32 Ivo Couckuyt wrote:
> [...]
> >> In the very beginning I used ndiswrapper without any problem (still
> >> works now), but at the moment i'm using the old islsm driver together
> >> with kernel 2.6.9 and firmware 2.5.6.0 (only one that works), [...]
> I also added some prints to narrow it down (tedious work, have to
> restart everytime i make a change). dmesg log is attached (ILM:
> statements were added).
>
> snippet of changed code where it seems to fail, it is in p54usc.c
> function p54u_upload_firmware_net2280:
> ...
>     printk(KERN_INFO "ILM: usb_interrupt...\n" );
>
>     err = usb_interrupt_msg(priv->udev,
>                 usb_rcvbulkpipe(priv->udev, P54U_PIPE_INT),
>                 buf, sizeof(__le32), &alen, 1000);
>     printk(KERN_INFO "ILM: call finished (error %i)
> (sizeof(__le32)=%i=%i)...\n", err, sizeof(__le32), alen );
>     if (err || alen != sizeof(__le32))
>         goto fail;
> [...]
>-> dmesg output: <-
>ILM: usb_interrupt...
>ehci_hcd 0000:00:02.2: HC died; cleaning up
>usb 1-1: USB disconnect, address 4
> ...
>
> so the usb_interrupt thing might be related somehow (causes the HC
> failed), or it is just that the usb stick should send 'keep-alive' irq's
> but doesn't because initialization before that has actually failed ?
> (don't know anything about kernel dev, just guessing here).
>

Well, since the USB stack from 2.6.9 differs a lot from the current 2.6.25  
and the p54usb is a _copy_ of islsm (in that regard) and unless my eyes are 
really that bad. the p54usb driver "should" work as good as islsm/ndiswrapper.

So, maybe someone of the linux-usb people knows why this happens?!
How to fix it, or how to DEBUG?! (any tips/hints? or is there a util like 
strace/usbsnopper which can monitor/compare the function-calls and
the resulting traffic of ndiswrapper AND the p54usb driver?)
(Chipset seems to be a nForce 2 OHCI/EHCI):

ehci_hcd 0000:00:02.2: HC died; cleaning up
irq 11: nobody cared (try booting with the "irqpoll" option) 
Pid: 0, comm: swapper Not tainted 2.6.25-gentoo-r4-BARTON #1 
[<c0149ee7>] __report_bad_irq+0x27/0x90
[<c014a218>] note_interrupt+0x2c8/0x300
[<c01493e1>] ? handle_IRQ_event+0x31/0x70
[<c014aced>] handle_level_irq+0xdd/0x110
[<c0105e26>] do_IRQ+0x46/0x80
[...]
handlers:
[<c02fef00>] (usb_hcd_irq+0x0/0x60) 
[<c02fef00>] (usb_hcd_irq+0x0/0x60) Disabling IRQ #11
(full: http://article.gmane.org/gmane.linux.kernel.wireless.general/15841)
"

More References (including lsusb -v, lspci -v and many more):
http://www.spinics.net/lists/linux-wireless/msg15834.html
http://article.gmane.org/gmane.linux.kernel.wireless.general/11525
http://article.gmane.org/gmane.linux.kernel.wireless.general/17170

Regards,
	Chr.

  reply	other threads:[~2008-07-04 17:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 17:07 PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter Ivo Couckuyt
2008-07-02 17:26 ` Chr
2008-07-02 20:31   ` Ivo Couckuyt
2008-07-04 17:56     ` Chr [this message]
2008-07-04 18:21       ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2008-02-10 22:25 Ivo Couckuyt
2008-02-20 18:40 ` Johannes Berg
2008-06-06 21:06   ` Ivo Couckuyt
2008-06-08 11:54     ` Johannes Berg
2008-06-08 20:03       ` Chr
2008-06-08 21:23         ` Ivo Couckuyt
2008-02-20 20:09 ` John W. Linville
2008-02-11  2:04   ` Ivo Couckuyt

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=200807041956.34051.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=iv0co@yahoo.co.uk \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@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).