Bug 487954 - eth1: next frame inconsistency
eth1: next frame inconsistency
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2009-03-01 12:12 EST by Sam Varshavchik
Modified: 2009-12-18 03:56 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 03:56:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sam Varshavchik 2009-03-01 12:12:10 EST
Description of problem:

Randomly, once every couple of hours, my PCMCIA network adapter stops responding. This started happening somewhere in the 2.6.27 kernel series. The following gets logged in syslog when the card stops working:

Mar  1 11:54:13 laptop kernel: eth1: next frame inconsistency, 0xef

The hexadecimal byte varies. There's usually several hundred of these logged, within a few seconds, before the card goes dead.

ifdown eth1/ifup eth1 restores network connectivity.

dmesg at boot:

Mar  1 08:19:38 laptop kernel: pccard: PCMCIA card inserted into slot 0
Mar  1 08:19:38 laptop kernel: cs: memory probe 0xffd00000-0xffdfffff: excluding
 0xffd00000-0xffd0ffff 0xffdf0000-0xffdfffff
Mar  1 08:19:38 laptop kernel: pcmcia: registering new device pcmcia0.0
Mar  1 08:19:38 laptop kernel: eth1: Asix AX88790: io 0x300, irq 3, hw_addr 00:1
Mar  1 08:19:38 laptop kernel: Intel ICH 0000:00:1f.5: enabling device (0005 -> 
Comment 1 Chuck Ebbert 2009-03-02 14:02:47 EST
This is possibly a hardware problem, like a loose or defective cable.

If you go back to the older kernel does it work again?
Comment 2 Sam Varshavchik 2009-03-03 07:11:09 EST
Futzing with the network cable makes no difference, only ifdown/ifup.

I went back to and let it run overnight, and had some constant network activity always running. Well, so far, eight hours later, the network remains up, and syslog is clean.

It's hard to prove a negative, but with this happened about every hour, or so.
Comment 3 Bug Zapper 2009-11-18 06:15:47 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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 4 Bug Zapper 2009-12-18 03:56:01 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.