In my case I installed the new kernel on a desktop and on a laptop. On the desktop the nvidia driver worked fine until I tried to use bzflag, which runs in, I think it is, framebuffer mode. On the laptop, the wifi stopped working.
I didn't have time to investigate what was happening. Reverting to the old kernel solved the problems. My 2 cents. On Sat, Jan 19, 2013 at 11:43 PM, AL13N <[email protected]> wrote: > Op vrijdag 18 januari 2013 21:30:58 schreef Luca Olivetti: > > Al 18/01/13 19:00, En/na Morgan Leijström ha escrit: > > > Analysis and workaround: > > > https://bugs.mageia.org/show_bug.cgi?id=8738 > > a different kernel bug? > > after updates on mga2, i had quite some strangeness: first of all, after a > little while of not yet rebooting, i got a complete hang of my system, > SysRq > keys worked, it appeared to be a CPU stall... > > after reboot, my mouse didn't work. i replugged and then it did work. > > looking through the logs on what happend, i saw the kswapd0 info, and later > the hang in the form of continuous CPU stall INFO. but keyb/mouse hadn't > worked (keyboard is PS2) > > I did however note the following when booting up: > > Jan 19 22:20:25 localhost kernel: [ 2.229050] ohci_hcd: USB 1.1 'Open' > Host > Controller (OHCI) Driver > Jan 19 22:20:25 localhost kernel: [ 2.229121] ohci_hcd 0000:00:12.0: > OHCI > Host Controller > Jan 19 22:20:25 localhost kernel: [ 2.229152] ohci_hcd 0000:00:12.0: new > USB bus registered, assigned bus number 1 > Jan 19 22:20:25 localhost kernel: [ 2.229186] ohci_hcd 0000:00:12.0: irq > 16, io mem 0xfcefe000 > ... > Jan 19 22:20:25 localhost kernel: [ 2.230887] ehci_hcd: USB 2.0 > 'Enhanced' > Host Controller (EHCI) Driver > Jan 19 22:20:25 localhost kernel: [ 2.230889] Warning! ehci_hcd should > always be loaded before uhci_hcd and ohci_hcd, not after > ... > Jan 19 22:20:25 localhost kernel: [ 3.059594] usb 3-1: new low-speed USB > device number 2 using xhci_hcd > ... > Jan 19 22:20:25 localhost kernel: [ 8.059817] xhci_hcd 0000:04:00.0: > Timeout while waiting for address device command > > > hmm... could the loading of ohci before ehci explain that mouse issue? > > > now, i admit to not rebooting right away, but this is likely less than an > hour > after doing the updates... >
