From: "Shawn Starr" <shawn.starr@rogers.com>
To: "'Feldman, Scott'" <scott.feldman@intel.com>,
"'Brown, Len'" <len.brown@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@oss.sgi.com>
Subject: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout - Related to i2c interface?
Date: Sat, 10 Apr 2004 02:23:06 -0400 [thread overview]
Message-ID: <000001c41ec4$5b937430$0200080a@panic> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0103AF5FB7@orsmsx402.jf.intel.com>
Ok, did disable ACPI but still get these errors. I have noticed that if I
start loading/unloading any i2c drivers I start getting eth0 timeouts....the
question is why?
coredump kernel: i2c_adapter i2c-2: Transaction (post): CNT=08, CMD=3a,
ADD=50, DAT0=3e, DAT1=00
Apr 10 01:56:44 coredump kernel: i2c-core: unregister_driver - looking for
clients.
Apr 10 01:56:44 coredump kernel: i2c_adapter i2c-2: examining adapter
Apr 10 01:56:44 coredump kernel: i2c-core.o: detaching client lm80:
Apr 10 01:56:44 coredump kernel: i2c-core.o: detaching client lm80:
Apr 10 01:56:44 coredump kernel: i2c-core: driver unregistered: lm80
Apr 10 01:56:48 coredump kernel: i2c_adapter i2c-2: Adapter unregistered
Apr 10 01:56:48 coredump kernel: i2c_adapter i2c-2: adapter unregistered
Apr 10 01:56:55 coredump kernel: eth0: wait_for_cmd_done timeout!
Apr 10 01:56:55 coredump kernel: Command 00ff never accepted (201 polls)!
Apr 10 01:56:55 coredump kernel: Command 0006 was not accepted after 20001
polls! Current status ffffffff.
Apr 10 01:56:55 coredump kernel: Command 00ff never accepted (201 polls)!
Apr 10 01:56:55 coredump kernel: Command 0060 was not accepted after 20001
polls! Current status ffffffff.
Apr 10 01:56:55 coredump kernel: eth0: wait_for_cmd_done timeout!
Apr 10 01:56:55 coredump kernel: Command 00ff never accepted (201 polls)!
Apr 10 01:56:55 coredump kernel: Command 0001 was not accepted after 20001
polls! Current status ffffffff.
Apr 10 01:56:55 coredump kernel: Command 00ff never accepted (201 polls)!
Apr 10 01:56:56 coredump kernel: Command 0070 was not accepted after 20001
polls! Current status ffffffff.
Apr 10 01:56:56 coredump kernel: eth0: wait_for_cmd_done timeout!
Apr 10 01:57:27 coredump last message repeated 26 times
Apr 10 01:57:29 coredump last message repeated 3 times
-----Original Message-----
From: Feldman, Scott [mailto:scott.feldman@intel.com]
Sent: Wednesday, April 07, 2004 02:31 PM
To: Brown, Len; Shawn Starr
Subject: RE: [BUG][2.6.5 final][e100] NETDEV_WATCHDOG Timeout - Was not a
problem with 2.6.5-rc3
> >Shawn, try turning off ACPI for interrupt routing. Load the kernel
> >with the kernel parameter "noapci" set.
>
> You mean "acpi=off", or "pci=noacpi". If either of these fix
> the problem, please let me know. (and send me the dmesg and
> /proc/interrupts for both cases)
Yes, sorry. Can't believe I posted that to lkml. Oh well.
-scott
parent reply other threads:[~2004-04-10 6:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <C6F5CF431189FA4CBAEC9E7DD5441E0103AF5FB7@orsmsx402.jf.intel.com>]
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='000001c41ec4$5b937430$0200080a@panic' \
--to=shawn.starr@rogers.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
/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).