Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 453259 - tulip driver oops
Summary: tulip driver oops
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-28 13:07 UTC by Trevor Cordes
Modified: 2009-01-09 06:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 06:38:44 UTC

Attachments (Terms of Use)
output from 3 different oops (deleted)
2008-06-28 13:07 UTC, Trevor Cordes
no flags Details

Description Trevor Cordes 2008-06-28 13:07:29 UTC
Description of problem:
Tulip driver is causing kernel oops.  Can't seem to tell what it triggering it.
 Happens every few days.

Version-Release number of selected component (if applicable):

How reproducible:
not on demand, but happens every couple of days.

Steps to Reproduce:
1. Boot box with tulip card present
Actual results:
oops, system becomes unstable, all network processes hang

Expected results:
no oops

Additional info:
02:01.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet
10/100 (rev 11)
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
02:05.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 02)

tulip card is the ADMtek.  This card worked fine without oops on previous
install of F8 using slightly older kernel.  Recently did fresh install.

See attached oops.

When I first reinstalled, I had 2 ADMtek cards in it, but it started oopsing
very quickly so I thought maybe it was a bad NIC and put a 8139 in place of 1
ADMtek, and the oops then started occurring less frequently, but still occurs as
you see.  I will probably replace the last ADMtek with another 8139 and I'm sure
the problem will go away.  From what I can see, I seriously doubt this is faulty
hardware (I have lots of experience with these things).

Comment 1 Trevor Cordes 2008-06-28 13:07:29 UTC
Created attachment 310499 [details]
output from 3 different oops

Comment 2 Bug Zapper 2008-11-26 10:56:12 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 3 Bug Zapper 2009-01-09 06:38:44 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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