mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: solt@dns.toxicfilms.tv
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3com 3c59x stopped working with 2.6.13-rc[56]
Date: Mon, 22 Aug 2005 14:36:42 -0700	[thread overview]
Message-ID: <20050822143642.5686ecc8.akpm@osdl.org> (raw)
In-Reply-To: <20050822202740.9793.qmail@dns.toxicfilms.tv>

solt@dns.toxicfilms.tv wrote:
>
> i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same
> result: my 3com (3c59x driver on 3com 905c) card not working.
> Here is what I saw in the logs.
> Notice the regularity of the log barfs. They continue the same every 10secs.
> 
> The upgrade was committed using:
> cd /usr/src/linux
> patch -p1 < ../patch-2.6.13-rc5
> patch -p1 < ../patch-2.6.13-rc5-git4
> make oldconfig
> make bzImage modules modules_install install
> 
> gcc-4.0.1 from Debian testing.
> 

I assume it worked OK in 2.6.12.

There are no changes in the driver which would explain this.

> 
> 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1.
> 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out
> 18:32:02: eth1: transmit timed out, tx_status 00 status e601.
> 18:32:02:   diagnostics: net 0cfa media 8880 dma 0000003a fifo 8800
> 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device?

gargh, I have acpi feelings.  Could you please

a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6

b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6
   (dmesg -s 1000000 > foo), then do

	diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 > foo

   and send foo?

  reply	other threads:[~2005-08-22 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 20:27 solt
2005-08-22 21:36 ` Andrew Morton [this message]
2005-08-23 14:48   ` Maciej Soltysiak
2005-08-23  3:59 Steve Lee

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=20050822143642.5686ecc8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solt@dns.toxicfilms.tv \
    /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

all inboxes | Powered by JetHome®