http://qa.mandrakesoft.com/show_bug.cgi?id=4924
Product: kernel
Component: default
Summary: via-rhine deadlocks kernel 2.4.22.1
Product: kernel
Version: 2.4.22-0.7mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: default
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I've been running 9.2b2 plus kernel 2.4.21.6mdk on a VIA EPIA M10000N (C3,
Nehemiah) motherboard for a week or so, using the integrated via-rhine ethernet
just fine.
I just upgraded to 2.4.22.1, and as soon as the init scripts brought up eth0,
the system hung solid (dead even to magic sysreq keys).
I rebooted in the old kernel, removed ifcfg-eth0 to disable ethernet startup,
and rebooted in 2.4.22.1 again.
Everything ran fine - dmesg showed the via being detected etc. I did a (manual)
ifconfig eth0 x.x.x.x, which seemed OK, and then I did another ifconfig to
correct the netmask and broadcast and about 1-2 seconds later, the system was
hung again.
I don't think it was setting up the interface that killed it, but more probably
the actual transmission or reception of a packet. The dmesg showed the MII
negotiating ok in the first step, but nothing after that.
(eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.)
2.4.21-6 shows this as:
via-rhine.c:v1.10-LK1.1.17 March-1-2003 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT6102 Rhine-II at 0xec00, 00:40:63:d3:5b:f9, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
Without sysreq, I can't get a trace of where it's stuck. Is there any other easy
way to get more debug info on this?
Hope it's an easily fixed, as I'm looking forward to 9.2 final on this little box...
Cheers
Cris
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
