From: Len Brown <len.brown@intel.com>
To: Oliver Feiler <kiza@gmx.net>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Marcelo Tosatti <marcelo@hera.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: eth*: transmit timed out since .27
Date: 16 Aug 2004 15:38:29 -0400 [thread overview]
Message-ID: <1092685109.23057.27.camel@dhcppc4> (raw)
In-Reply-To: <41210098.4080904@gmx.net>
On Mon, 2004-08-16 at 14:44, Oliver Feiler wrote:
> 14: 9296 IO-APIC-edge ide0
> 15: 9078 IO-APIC-edge ide1
> 17: 24 IO-APIC-level eth1
> 18: 125085 IO-APIC-level eth0
> 21: 0 IO-APIC-level usb-uhci, usb-uhci, usb-uhci
> 22: 0 IO-APIC-level via82cxxx
> 23: 2976 IO-APIC-level eth2
> NMI: 0
> LOC: 112313
> ERR: 0
> MIS: 42
This is unusual.
MIS is a hardware workaround and should normally be 0.
>
>
> vs.
>
> 00:11.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev
> 06)
> (prog-if 8a [Master SecP PriP])
> Subsystem: Unknown device 1849:0571
> Flags: bus master, medium devsel, latency 32, IRQ 255
> I/O ports at fc00 [size=16]
> Capabilities: <available only to root>
>
> This probably has to do with this boot message:
> PCI: No IRQ known for interrupt pin A of device 00:11.1
> I have found absolutely nothing that explains if this is an error or
> just some sort of debug message one can ignore.
Yes, ignore it.
This is where that message about 255 came from.
When ACPI failed to find a PCI-routing-table entry
for this device, it looked in PCI config space
and found the 255 you see above. The only recent
change is that it dosn't try to use an obviously
bogus value. But in either case, with this device
it is moot as the hardware and the driver are hard-coded.
-Len
next prev parent reply other threads:[~2004-08-16 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C3236@hdsmsx403.hd.intel.com>
2004-08-16 17:52 ` eth*: transmit timed out since .27 (was: linux-2.4.27 released) Len Brown
2004-08-16 18:44 ` eth*: transmit timed out since .27 Oliver Feiler
2004-08-16 19:08 ` Oliver Feiler
2004-08-16 19:50 ` Len Brown
2004-08-16 23:04 ` Oliver Feiler
2004-08-16 23:42 ` Maciej W. Rozycki
2004-08-17 0:29 ` Alan Cox
2004-08-16 19:38 ` Len Brown [this message]
2004-08-16 20:11 ` Maciej W. Rozycki
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=1092685109.23057.27.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=kiza@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=marcelo@hera.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