mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kaweth fails to work on 2.6.12-rc[56]
Date: Sat, 11 Jun 2005 00:11:36 -0400	[thread overview]
Message-ID: <20050611041136.GA5617@animx.eu.org> (raw)
In-Reply-To: <200506081308.39450.oliver@neukum.org>

Oliver Neukum wrote:
> Am Mittwoch, 8. Juni 2005 12:42 schrieb Wakko Warner:
> > > have you tried recompiling with debug enabled?
> > > It does show the status codes in the interrupt handler.
> > 
> > I have not. ?My keyboard and mouse (on a hub) are plugged in beside the
> > kaweth device so they would be on the same interrupt.
> 
> Sorry, I should be more specific. It will print out the error codes
> internal to the USB layer which are meaningful even if interrupts are shared.
> Also, are you seeing tx errors in the error count?

Unless I did something wrong, it's apparently not in the USB subsystem.

I have 2.6.12-rc3 and rc4 compiled.  Same config file on a test system.
again, rc3 works, rc4 does not.  I booted rc3 and force loaded the usb
modules from rc4 into rc3.  It tainted the kernel, but it worked.

I booted into rc4.  I do have ACPI compiled so I added acpi=off.  This did
not work, same problem as before.  I left a ping running, the usb controller
was on IRQ 9.  The test system is an old NEC notebook with an Intel chipset
(thus uhci-hcd usb1.1).  I plugged in a Belkin USB2.0 cardbus card (USB1.1
is serviced by ohci-hcd) and plugged the ethernet adapter into that.  Same
problem.

As far as controllers, ALL except 1 (The cardbus USB2.0) has been some
version of Intel.  I have tested this on 4 different systems with the same
results.  An MSI 6163 board, a Supermicro X5DA8 board, a Dell Inspiron 8100,
and the NEC Versa FX.  The Supermicro is running SMP, but I doubt that
matters.

At this time, it's late.  I'll see about reverting files from rc4 back to
rc3 to see which one causes it to work again.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2005-06-11  4:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  2:11 Wakko Warner
2005-06-08  3:11 ` Wakko Warner
2005-06-08  6:59   ` Oliver Neukum
2005-06-08  8:48     ` [linux-usb-devel] " David Brownell
2005-06-08 10:43       ` Wakko Warner
2005-06-08 10:42     ` Wakko Warner
2005-06-08 11:08       ` Oliver Neukum
2005-06-11  4:11         ` Wakko Warner [this message]
2005-06-11 11:13           ` Oliver Neukum
2005-06-11 12:52             ` Wakko Warner
2005-06-11 14:39               ` Oliver Neukum

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=20050611041136.GA5617@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oliver@neukum.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

Powered by JetHome