diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/attachments/20130121')
| -rw-r--r-- | zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment-0001.html | 48 | ||||
| -rw-r--r-- | zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment.html | 48 |
2 files changed, 96 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment-0001.html b/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment-0001.html new file mode 100644 index 000000000..0bc396589 --- /dev/null +++ b/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment-0001.html @@ -0,0 +1,48 @@ +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.<br> +<br>I didn't have time to investigate what was happening. Reverting to the old kernel solved the problems.<br><br>My 2 cents.<br><br><br><div class="gmail_quote">On Sat, Jan 19, 2013 at 11:43 PM, AL13N <span dir="ltr"><<a href="mailto:alien@rmail.be" target="_blank">alien@rmail.be</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Op vrijdag 18 januari 2013 21:30:58 schreef Luca Olivetti:<br> +<div class="im">> Al 18/01/13 19:00, En/na Morgan Leijström ha escrit:<br> +> > Analysis and workaround:<br> +> > <a href="https://bugs.mageia.org/show_bug.cgi?id=8738" target="_blank">https://bugs.mageia.org/show_bug.cgi?id=8738</a><br> +<br> +</div>a different kernel bug?<br> +<br> +after updates on mga2, i had quite some strangeness: first of all, after a<br> +little while of not yet rebooting, i got a complete hang of my system, SysRq<br> +keys worked, it appeared to be a CPU stall...<br> +<br> +after reboot, my mouse didn't work. i replugged and then it did work.<br> +<br> +looking through the logs on what happend, i saw the kswapd0 info, and later<br> +the hang in the form of continuous CPU stall INFO. but keyb/mouse hadn't<br> +worked (keyboard is PS2)<br> +<br> +I did however note the following when booting up:<br> +<br> +Jan 19 22:20:25 localhost kernel: [ 2.229050] ohci_hcd: USB 1.1 'Open' Host<br> +Controller (OHCI) Driver<br> +Jan 19 22:20:25 localhost kernel: [ 2.229121] ohci_hcd 0000:00:12.0: OHCI<br> +Host Controller<br> +Jan 19 22:20:25 localhost kernel: [ 2.229152] ohci_hcd 0000:00:12.0: new<br> +USB bus registered, assigned bus number 1<br> +Jan 19 22:20:25 localhost kernel: [ 2.229186] ohci_hcd 0000:00:12.0: irq<br> +16, io mem 0xfcefe000<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 2.230887] ehci_hcd: USB 2.0 'Enhanced'<br> +Host Controller (EHCI) Driver<br> +Jan 19 22:20:25 localhost kernel: [ 2.230889] Warning! ehci_hcd should<br> +always be loaded before uhci_hcd and ohci_hcd, not after<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 3.059594] usb 3-1: new low-speed USB<br> +device number 2 using xhci_hcd<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 8.059817] xhci_hcd 0000:04:00.0:<br> +Timeout while waiting for address device command<br> +<br> +<br> +hmm... could the loading of ohci before ehci explain that mouse issue?<br> +<br> +<br> +now, i admit to not rebooting right away, but this is likely less than an hour<br> +after doing the updates...<br> +</blockquote></div><br> diff --git a/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment.html b/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment.html new file mode 100644 index 000000000..0bc396589 --- /dev/null +++ b/zarb-ml/mageia-discuss/attachments/20130121/c786eb11/attachment.html @@ -0,0 +1,48 @@ +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.<br> +<br>I didn't have time to investigate what was happening. Reverting to the old kernel solved the problems.<br><br>My 2 cents.<br><br><br><div class="gmail_quote">On Sat, Jan 19, 2013 at 11:43 PM, AL13N <span dir="ltr"><<a href="mailto:alien@rmail.be" target="_blank">alien@rmail.be</a>></span> wrote:<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Op vrijdag 18 januari 2013 21:30:58 schreef Luca Olivetti:<br> +<div class="im">> Al 18/01/13 19:00, En/na Morgan Leijström ha escrit:<br> +> > Analysis and workaround:<br> +> > <a href="https://bugs.mageia.org/show_bug.cgi?id=8738" target="_blank">https://bugs.mageia.org/show_bug.cgi?id=8738</a><br> +<br> +</div>a different kernel bug?<br> +<br> +after updates on mga2, i had quite some strangeness: first of all, after a<br> +little while of not yet rebooting, i got a complete hang of my system, SysRq<br> +keys worked, it appeared to be a CPU stall...<br> +<br> +after reboot, my mouse didn't work. i replugged and then it did work.<br> +<br> +looking through the logs on what happend, i saw the kswapd0 info, and later<br> +the hang in the form of continuous CPU stall INFO. but keyb/mouse hadn't<br> +worked (keyboard is PS2)<br> +<br> +I did however note the following when booting up:<br> +<br> +Jan 19 22:20:25 localhost kernel: [ 2.229050] ohci_hcd: USB 1.1 'Open' Host<br> +Controller (OHCI) Driver<br> +Jan 19 22:20:25 localhost kernel: [ 2.229121] ohci_hcd 0000:00:12.0: OHCI<br> +Host Controller<br> +Jan 19 22:20:25 localhost kernel: [ 2.229152] ohci_hcd 0000:00:12.0: new<br> +USB bus registered, assigned bus number 1<br> +Jan 19 22:20:25 localhost kernel: [ 2.229186] ohci_hcd 0000:00:12.0: irq<br> +16, io mem 0xfcefe000<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 2.230887] ehci_hcd: USB 2.0 'Enhanced'<br> +Host Controller (EHCI) Driver<br> +Jan 19 22:20:25 localhost kernel: [ 2.230889] Warning! ehci_hcd should<br> +always be loaded before uhci_hcd and ohci_hcd, not after<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 3.059594] usb 3-1: new low-speed USB<br> +device number 2 using xhci_hcd<br> +...<br> +Jan 19 22:20:25 localhost kernel: [ 8.059817] xhci_hcd 0000:04:00.0:<br> +Timeout while waiting for address device command<br> +<br> +<br> +hmm... could the loading of ohci before ehci explain that mouse issue?<br> +<br> +<br> +now, i admit to not rebooting right away, but this is likely less than an hour<br> +after doing the updates...<br> +</blockquote></div><br> |