From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [2.5.70-mm8] NETDEV WATCHDOG: eth0: transmit timed out
Date: Wed, 11 Jun 2003 15:16:44 +0200 [thread overview]
Message-ID: <200306111516.46648.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <200306111356.52950.schlicht@uni-mannheim.de>
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
Hi,
it seems that whether the netdevice nor the 8139too parts of the kernel cause
my problems but there must have been some bad changes to the interrupt
routing or the IO-APIC parts.
I don't have -mm7 handy currently (but at the moment it compiles again) but I
attached the contents of /proc/interrupts of 2.4.10 (the system I currently
run) and 2.5.70-mm8 again.
As you can see there, the -mm8 code does not assign more than 16 interrupt
sinks but the 2.4.10 (and if I remember correctly -mm7, too) has 22. Perhaps
even more problematic is that -mm8 seems not to use level-triggered
interrupts...!
I could try to revert some IRQ or APIC changes if someone could tell me which
Changeset may have caused that...
Best reagrds
Thomas Schlichter
[-- Attachment #1.2: interrupts-2.4.10.txt --]
[-- Type: text/plain, Size: 646 bytes --]
CPU0
0: 184641 IO-APIC-edge timer
1: 2037 IO-APIC-edge keyboard
2: 0 XT-PIC cascade
4: 2 IO-APIC-edge serial
8: 2 IO-APIC-edge rtc
12: 78366 IO-APIC-edge PS/2 Mouse
14: 188581 IO-APIC-edge ide0
15: 6 IO-APIC-edge ide1
16: 180617 IO-APIC-level nvidia
17: 14155 IO-APIC-level eth0
18: 82091 IO-APIC-level EMU10K1
19: 457792 IO-APIC-level fcpci
21: 0 IO-APIC-level usb-uhci, usb-uhci, usb-uhci
NMI: 0
LOC: 184592
ERR: 0
MIS: 0
[-- Attachment #1.3: interrupts-2.5.70-mm8.txt --]
[-- Type: text/plain, Size: 613 bytes --]
CPU0
0: 52599 IO-APIC-edge timer
1: 1075 IO-APIC-edge i8042
2: 0 XT-PIC cascade
4: 11 IO-APIC-edge serial
5: 0 IO-APIC-edge uhci-hcd
8: 2 IO-APIC-edge rtc
9: 0 IO-APIC-edge acpi
10: 0 IO-APIC-edge ehci-hcd
11: 0 IO-APIC-edge eth0, EMU10K1, bttv0, uhci-hcd, uhci-hcd
12: 79 IO-APIC-edge i8042
14: 6217 IO-APIC-edge ide0
15: 10 IO-APIC-edge ide1
NMI: 0
LOC: 52557
ERR: 0
MIS: 0
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-11 13:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:33 2.5.70-mm8 Andrew Morton
2003-06-11 8:33 ` 2.5.70-mm8 Andrew Morton
2003-06-11 9:17 ` 2.5.70-mm8 Stefano Rivoir
2003-06-11 9:17 ` 2.5.70-mm8 Stefano Rivoir
2003-06-11 9:27 ` 2.5.70-mm8 Andrew Morton
2003-06-11 9:27 ` 2.5.70-mm8 Andrew Morton
2003-06-11 9:31 ` 2.5.70-mm8 Thomas Schlichter
2003-06-11 10:13 ` [PATCH] Compile fix for 2.5.70-mm8/drivers/usb/media/vicam.c Thomas Schlichter
2003-06-11 11:08 ` 2.5.70-mm8 - RAID1 and fb works! Helge Hafting
2003-06-11 11:08 ` Helge Hafting
2003-06-11 15:57 ` Helge Hafting
2003-06-11 15:57 ` Helge Hafting
2003-06-11 11:56 ` [2.5.70-mm8] NETDEV WATCHDOG: eth0: transmit timed out Thomas Schlichter
2003-06-11 13:16 ` Thomas Schlichter [this message]
2003-06-11 15:25 ` Thomas Schlichter
2003-06-11 18:56 ` Andrew Morton
2003-06-11 18:56 ` Andrew Morton
2003-06-12 11:59 ` Thomas Schlichter
2003-06-12 5:20 ` 2.5.70-mm8 Jordan Breeding
2003-06-12 5:20 ` 2.5.70-mm8 Jordan Breeding
2003-06-12 5:31 ` 2.5.70-mm8 Andrew Morton
2003-06-12 5:31 ` 2.5.70-mm8 Andrew Morton
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=200306111516.46648.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.