From: Jorge Nerin <comandante@zaralinux.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP, APIC and networking issues...
Date: Sat, 01 Sep 2001 22:59:29 +0200 [thread overview]
Message-ID: <3B914C31.3080804@zaralinux.com> (raw)
In-Reply-To: <E15cxsH-0004F6-00@the-village.bc.nu>
Alan Cox wrote:
>>The supposed trick is to boot with a "noapic"
>>option, since this is believed to be a APIC issue,
>>not a driver issue (as mentioned, this problem
>>has been seen for both 3com and intel cards).
>>
>>Is "noapic" still the recommended approach for SMP
>>kernels or is it advisable to use 2.4.9 to solve
>>this specific issue ?
>>
>
> If you are still seeing the problem then yes try noapic, but also let
> me know if its happening with current kernels. The apic has multiple effects
> and not all of them are necessarily hardware issues at all
>
> The big one is that interrupts can get delayed and become much more
> asynchronous which can obviously have impacts on driver races
I'm having nic hangs with recent kernels, the last one in wich I saw
this is with 2.4.9-ac3, and I'm currently running 2.4.9-ac5, the nic is
a 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 64) linked with a
twisted cable to another computer.
I have a dual 200mmx, motherboard is a gigabyte 586dx, lots of apic
errors, but so far not a lot of hangs, is home machine, no server.
Aug 27 15:50:26 quartz kernel: NETDEV WATCHDOG: eth0: transmit timed out
Aug 27 15:50:26 quartz kernel: eth0: transmit timed out, tx_status 00
status e601.
Aug 27 15:50:26 quartz kernel: diagnostics: net 0cf2 media 8880 dma
0000003a.
Aug 27 15:50:26 quartz kernel: eth0: Interrupt posted but not delivered
-- IRQ blocked by another device?
Aug 27 15:50:26 quartz kernel: Flags; bus-master 1, dirty 149028(4)
current 149028(4)
Aug 27 15:50:26 quartz kernel: Transmit list 00000000 vs. c51cf300.
Aug 27 15:50:26 quartz kernel: 0: @c51cf200 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 1: @c51cf240 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 2: @c51cf280 length 80000062 status
80010062
Aug 27 15:50:26 quartz kernel: 3: @c51cf2c0 length 80000062 status
80010062
Aug 27 15:50:26 quartz kernel: 4: @c51cf300 length 8000006e status
0001006e
Aug 27 15:50:26 quartz kernel: 5: @c51cf340 length 8000006e status
0001006e
Aug 27 15:50:26 quartz kernel: 6: @c51cf380 length 8000006e status
0001006e
Aug 27 15:50:26 quartz kernel: 7: @c51cf3c0 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 8: @c51cf400 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 9: @c51cf440 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 10: @c51cf480 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 11: @c51cf4c0 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 12: @c51cf500 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 13: @c51cf540 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 14: @c51cf580 length 80000062 status
00010062
Aug 27 15:50:26 quartz kernel: 15: @c51cf5c0 length 80000062 status
00010062
BTW I switched to a rtl8139 from a rtl8029 for speed upgrade, but it was
slow as a dog in my system, due to (as someone said) bad motherboard
chipset for busmaster transfer, and nic hangs, so switched to a 3com
905, with the same results, speed is somewhat better, but it also hangs.
--
Jorge Nerin
<comandante@zaralinux.com>
next prev parent reply other threads:[~2001-09-11 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 22:40 [ANNOUNCE] Hardware detection tool 0.2 Carlos E Gorges
2001-08-30 23:18 ` Greg KH
2001-08-31 22:58 ` jeff millar
2001-08-31 23:11 ` SMP, APIC and networking issues java programmer
2001-08-31 23:38 ` Alan Cox
2001-09-01 20:59 ` Jorge Nerin [this message]
2001-08-31 23:23 ` [ANNOUNCE] Hardware detection tool 0.2 Greg KH
2001-08-31 23:46 ` jeff millar
2001-09-01 0:08 ` Greg KH
2001-09-01 10:54 ` Tim Jansen
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=3B914C31.3080804@zaralinux.com \
--to=comandante@zaralinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.