Bug 6353 - Incoming packets ignored in kernel 2.6.16.2; possible IO problems
Summary: Incoming packets ignored in kernel 2.6.16.2; possible IO problems
Status: REJECTED INVALID
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Arnaldo Carvalho de Melo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-08 05:13 UTC by mikedlr
Modified: 2006-11-12 03:40 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.16.2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
This is the standard environment information for a linux bug report (14.23 KB, text/plain)
2006-04-08 05:46 UTC, mikedlr
Details

Description mikedlr 2006-04-08 05:13:53 UTC
Most recent kernel where this bug did not occur: 2.6.15 (fedora kernel)
Distribution: Fedora Core 4
Hardware Environment: AMD Athlon(tm) XP 1700+ / Gigabit Mother board / 8139too /
3c59x 
Software Environment: 2.6.16 / 2.6.16.2 / 2.6.16_1.2069_FC4 / Fedora Core 4
fully upgraded.
Problem Description:
When booting into new kernel, problems are evident.

Mouse movement is very slow and jerky (this happens before network subsystem
start, so is probably not related to networking);

More importantly; no incoming packets are recieved and only a few outgoing ones
are generated.  Outgoing ARP towards the default gateway is sent, but the
response is ignored.  

More full logs are available in the fedora core bug report which mirrors this.
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187662

I will attach the standard bug reporting output as a text file.

Steps to reproduce:
Comment 1 mikedlr 2006-04-08 05:46:40 UTC
Created attachment 7814 [details]
This is the standard environment information for a linux bug report

This attachment contains the standard bug reporting information listed in the
kernel.org bug reporting instructions except that the SCSI proc file doesn't
exist on my system.  

I can't think of any specific interesting things about the system.  It's
uniprocessor / plain with two hard disks and network cards.  It has FC4 with no
really interesting changes.
Comment 2 mikedlr 2006-04-09 07:06:47 UTC
Changing motherboard from a GA-7VRXP to an ASRock K7VT4A Pro (which has changed
my eth0 ethernet driver to "via-rhine") has fixed this problem for me.  The
reason I did that is that all the kernel compiling seems to have burnt out the
capacitors on my old mother board.  One of them even de-soldered its self!! 
This means that it will be difficult for me to reproduce the problem again.  I
can try to get the capacitors replaced if anybody cares.  
Comment 3 Adrian Bunk 2006-11-12 03:40:46 UTC
I'd assue the problem are the capacitors, such problems can result in many
strange  errors.

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