Opened 13 years ago
Closed 11 years ago
#24 closed defect (fixed)
R8169 Driver only passes packets through in 15 secs every minute.
Reported by: | Yoda | Owned by: | |
---|---|---|---|
Priority: | Feedback Pending | Component: | r8169 |
Version: | 0.1.1 | Keywords: | |
Cc: |
Description
Hardware:
Asrock A330GC MoBo with ATOM CPU.
Onboard Realtek Gigabit LAN 8111DL chip.
(+ an extra 8139 card in PCI slot).
It seems that output goes out to network fine,
but the driver ignores input 75% of the time.
When I try to ping another PC on network, it does send
out the pings, and other PC answers all the time - but the
answers are never 'received'.
Then, after maybe 100 pings, driver suddenly works for
a little time and then stops again.
Out of 1000 pings - 75% is lost.
It looks like there is open for input in 15 secs, and then
closed again for 45 secs.
It is possible to pull a web page down, if I hit the right
moment.
Tried NETBEUI too - it is basically the same.
If I hit the right moment, I can view resources from net;
but otherwise nothing comes in.
I tried RXCHAIN=NO - but it didn't change anything.
Attachments (1)
Change History (6)
comment:1 by , 13 years ago
by , 13 years ago
Attachment: | 8169-233.txt added |
---|
comment:2 by , 13 years ago
Version: | 0.0.3 → 0.0.4 |
---|
Tried v 0.0.4 (GA)
Same thing still happens.
First 90 pings gets no answer
next 30 works
next 90 doesn't work
[..........]
comment:3 by , 12 years ago
Version: | 0.0.4 → 0.1.1 |
---|
Well, tried the latest 0.1.1 and ACPI 3.21.02
Driver now seems to work.
System can suspend and resume; but after resume,
no more network traffic is possible.
If I try to suspend/resume again, system freezes
during resume - with the activity light on the
connector blinking constantly. Only way out is power OFF.
System also has an (unused) 8139 device. If I use that
device instead, system works perfectly after suspend/resume
several times.
comment:4 by , 12 years ago
Priority: | critical → Feedback Pending |
---|
Please try the new 0.3.1 version that was just released.
comment:5 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
No response from reporter. Closing ticket.
Tried v 0.0.4 (changeset 233).
Same thing still happens.
Attached debug output for approx 300 pings,
where only 25% of the answers were received.