Bug 9300
Summary: | via-rhine driver stalls with: PHY status 786d, resetting... | ||
---|---|---|---|
Product: | Drivers | Reporter: | Martin J. Bligh (mbligh) |
Component: | Network | Assignee: | Jeff Garzik (jgarzik) |
Status: | REJECTED INVALID | ||
Severity: | normal | CC: | rl, spam |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.23 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Martin J. Bligh
2007-11-03 11:28:03 UTC
Stalling and watchdog timeouts are common symptoms for various errors (depending on the exact chip set used, duplex settings, etc.). In the past few years, I fixed several problems that resulted in bug reports just like this one. By now, the driver seems to work fine for most people. The remaining problems are hard for me to reproduce. I can push a steady 10 MB/s through my test gear. I'm not saying the driver is anywhere near perfect, but if an e1000 card on the very same box has similar issues, what makes you think via-rhine is the culprit? Maybe the machine's interrupt delivery is flaky!? Yup, maybe this motherboard is just crap. After wasting a few more days on experiments, I've got the e1000 to work fine in another box. I guess I'll just scrap this motherboard ;-( Sorry. Exact same problem here with e1000 and via rhine (6106H) on a Dell PowerEdge sc1420 with Redhat EL 4.5. Besides that, the card is dropping ip packet fragments. try: ping -s 1750 xxx.xxx.xxx.xxx on a via rhine card. Could this be related, or should I open a new bug report for this? Redhat kernel version: 2.6.9-55.0.12 |