Repeatable r8169 kernel oops testcase
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
[root@gordon ~]#
cat /sys/devices/system/clocksource/clocksource0/available_clocksource acpi_pm jiffies tsc
Since I don't have hpet in my available_clocksources I tried notsc and clocksource=acpi_pm. I also tried the two ethtool commands below.
None of these changes made any difference. Networking is dead until the r8169 module is unloaded and reloaded. Also, while the network is up but "dead", mouse input is erratic. Moving the mouse is not smooth at all. Something is severely wrong while the r8169 module is in this state.
See attached .config.
Quoted 13 lines
Jay Cliburn <[email protected]> :
[...]Quoted 3 lines
Does booting with clocksource=hpet change anything? What about the others in
/sys/devices/system/clocksource/clocksource0/available_clocksourceOnce this is done, can your send your .config and tell if simply issuing an 'ethtool -s eth0 autoneg off' then 'ethtool -s eth0 autoneg on' makes a difference ?
Signature · 1 line
Ueimor
Dale Ogilvie <[email protected]> :
[...]
Quoted 4 lines
None of these changes made any difference. Networking is dead until the r8169 module is unloaded and reloaded. Also, while the network is up but "dead", mouse input is erratic. Moving the mouse is not smooth at all. Something is severely wrong while the r8169 module is in this state.
Is it possible for you to log 'mii-tool -v -v eth0' output:
- before the watchdog fires
- after it fires and before the module removal
- after the module removal / insertion, when everything seems right
Signature · 1 line
Ueimor