public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mirko Caserta" <mirko@mcaserta.com>
To: "OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>
Cc: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Re: 8139too not working in 2.6
Date: Mon, 26 Apr 2004 16:46:37 +0200	[thread overview]
Message-ID: <opr62jbzk9psnffn@mail.mcaserta.com> (raw)
In-Reply-To: <87oeperj4y.fsf@devron.myhome.or.jp>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

On Mon, 26 Apr 2004 21:58:05 +0900, OGAWA Hirofumi  
<hirofumi@mail.parknet.co.jp> wrote:

> "Mirko Caserta" <mirko@mcaserta.com> writes:
>
>> eth0: Transmit timeout, status 0c 0005 c07f media 10.
>
> This problem looks like miss configuration of level/edge-triggerd, or
> IRQ-routing problem.
>
> The attached script may clarify the problem. Also "lspci -vvvxxx" and
> output of dmesg would be useful.

I have attached a tarball with output from dmesg, lspci -vvvxxx, cat  
/proc/interrupts and your dump_pirq.pl utility.

Please note that before booting the 2.6.6-rc2-mm2 kernel I got into the  
BIOS and disabled "Assign IRQ for USB" which is why lspci and dmesg show  
irq 0 assigned to the USB chips.

Besides that change in the BIOS, everything is just the same between the  
reboots, apart from the card not properly working in 2.6.6-rc2-mm2 :/

Anyway, it doesn't look like an irq problem to me. It looks more like a  
wrong detection of the TX triggering level in the driver.

Thanks again, Mirko.


[-- Attachment #2: carbon-kernel-debug.tar.bz2 --]
[-- Type: application/bzip2, Size: 12964 bytes --]

  reply	other threads:[~2004-04-26 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 11:35 8139too not working in 2.6 Mirko Caserta
2004-04-26 11:41 ` David Johnson
2004-04-26 12:14   ` MNH
2004-04-26 13:29   ` Gene Heskett
2004-04-26 14:26   ` David Johnson
2004-04-26 15:53     ` OGAWA Hirofumi
2004-04-26 12:05 ` Jorge Bernal (Koke)
2004-04-26 12:13   ` David Johnson
2004-04-26 16:01     ` Jorge Bernal
2004-04-26 12:41 ` Derek Chen-Becker
2004-04-26 12:58 ` OGAWA Hirofumi
2004-04-26 14:46   ` Mirko Caserta [this message]
2004-04-26 15:14     ` OGAWA Hirofumi
2004-04-26 15:37       ` 8139too not working in 2.6 (works now) Mirko Caserta
2004-04-26 16:11         ` OGAWA Hirofumi

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=opr62jbzk9psnffn@mail.mcaserta.com \
    --to=mirko@mcaserta.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --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