Bug 9965 – new_tulip (actually LiteOn) likes to stall

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 9965 - new_tulip (actually LiteOn) likes to stall

Summary:	new_tulip (actually LiteOn) likes to stall

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-03-04 15:02 EST by Richard Hyde
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-10-26 22:06:53 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Richard Hyde 2000-03-04 15:02:36 EST

Ocasionally (more like often) my DLINK NIC likes to stall /proc/kmsg tells
me :
<4>eth0: Transmit timed out, status e4660000, CSR12 000050ca, resetting...

Best workaround is a /etc/rc.d/init.d/network restart.

This only seems to happen when I'm activly using this computer.  Hasn't
happened when I'm not (a couple machines using this one as a masq gateway).

Using IP aliasing to connect to private and public networks on the same NIC
(I know, slow).  Nothing else is real interesting with this config.
(2.2.14).

Don't know how much of a redhat problem this is but....

Comment 1 Richard Hyde 2000-10-26 22:06:50 EDT

This appears to be related to a buggy CPU/motherboard combo (K62-400, Fic
2013).  Problems went away after swaping systems.

Comment 2 Michael K. Johnson 2001-02-16 14:43:59 EST

Sorry, missed closing this when you reported it as a hardware issue...

Note You need to log in before you can comment on or make changes to this bug.