http://qa.mandrakesoft.com/show_bug.cgi?id=4924
------- Additional Comments From [EMAIL PROTECTED] 2003-05-09 12:55 ------- I've the same problem on my notebook, an Acer Aspire 1310XV. When running with my old kernel, 2.4.22.0.6(with a patch for the powernow-k7 module) i boots just fine. But all the other more recent kernels i've tried, my computer hangs when loading the via-rhine module. Here's what i get with the old kernel: via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xf0008000, 00:c0:9f:24:67:8b, IRQ 11. eth0: MII PHY found at address 1, status 0x7829 advertising 01e1 Link 45e1. And here's what i get with one of the new kernels(2.4.22-0.8 i think): via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xe200, 00:c0:9f:24:67:8b, IRQ 10. eth0: MII PHY found at address 1, status 0x782d advertising 01e1 Link 45e1. eth0: via_rhine_open() irq 10. eth0: Reset succesed. eth0: setting full-duplex based on MII #1 link partner capability of 45e1. eth0: Done via_rhine_open(), status 0c1a MII status: 782d eth0: VIA Rhine monitor tick, status 0000. Running without acpi is not an option, since its a notebook. -- 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. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: 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
