Anna kun arvaan: Tatsun? ;)

Mukavaa luettavaa.

Olivatko Serry ja Sani niminä muunnelmia Nissan-malleista vai onko se vain sattumaa?

My summary’s crap because this is difficult to summarize, hopefully the explanation below makes it clearer. I have little understanding of kernel internals, so I’ll first just try and describe the symptom as it appears.

I’ve come across an issue on my Fujitsu Siemens Amilo M7400 laptop with wistron_btns that is triggered by certain kernels, and once triggered, seems to affect all subsequent attempts to reboot with -pae kernels until a non-pae kernel is booted. I initially reported this on Launchpad [1].

I can currently trigger the issue by (cold or re-) booting 3.2.0-14-pae (these are Ubuntu’s packaged kernels) or by booting (for example) 3.3.0-030300rc4-generic-pae in recovery mode (= ”ro recovery nomodeset”). The recovery boot seems to work normally, but the 3.2.0-14-pae boot already exhibits the failure: it seemingly freezes. (More about the exact nature of ”failure” below.)

Once I’ve triggered the issue, rebooting with any -pae kernel fails similar to how 3.2.0-14-pae behaves irregardless of preceding boots.

I can ”fix” this by booting a non-pae kernel (which never fails). After that subsequent reboots with -pae kernels (apart from 3.2.0-14-pae) no longer fail — not until I do any of the triggering actions again.

Now, the ”failure” looks like a freeze, but it’s actually just an extreme slowdown. With patience, I can actually have the boot finish and can inspect logs. Dmesg reveals that wistron_btns is repeating ”Unknown key code 10” over and over.

If I comment wistron_btns out of /etc/modules so that it isn’t loaded, the issue goes away, meaning I can no longer trigger it.

As I said, I have little understanding of kernel bugs, so what I say next may be completely off, but the way I’ve interpreted this is that the ”brokenness” is actually hidden in the hardware, in something controlled by wistron_btns. Booting 3.2.0-14-pae/recovery booting any -pay puts the controller(?) in a ”broken” state from which a -pae kernel can’t recover, but a non-pae kernel can. And although -pae kernels later than 3.2.0-14 can’t recover a ”broken” controller, they also cannot put it into that ”broken” state (which is a good turn of development).

I’ll be happy to provide more info as requested. I’m attaching dmesg output for
starters.

* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926012

With persistent booting I was able to get a panic [1] showing with 3.3.0-030300rc4, and it looks the same as what the dmesg I posted in #29 [2] showed: print_bad_pte+0x187/0x1e0 is on top the Trace. Despite the numerous boots I was still unable to reproduce the initial printk+0x2d/0x2f, so it may be fixed in Main or masked by the print_bad_pte+0x187/0x1e0 (though this still is based only on two datapoints in a frustratingly random issue).

Whether RC6 is enabled or disabled doesn’t seem to have bearing on this. 3.2.0-17 produces printk+0x2d/0x2f either way [3], and 3.2.0-18.28 also panics, though less consistently: I was only able to produce a sure printk+0x2d/0x2f once [4], with 3.2.0-18.28 non-pae. Mostly the errors fail to reveal themselves, and when they do, they are different from printk+0x2d/0x2f but also from each other: a couple of times a warn_slowpath_common+0x72/0xa0 (as in Bug #917668, though the hardware and pointers are different) occurred [5], and once it was a Bad page map [6] in unity-greeter.

* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/32
* [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/29
* [3] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/33
* [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/34
* [5] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/35
* [6] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/926007/comments/36

I’ll upload a bunch of new screenshots for reference. They’re all related to testing this so bear with me, I’ll explain them further after uploading.

Still present in upstream 3.3.0-030300rc4 as it was in 3.2.0-17.27.

I tested 3.3.0-030300rc4 and couldn’t verify that the panic that all the 3.2’s above have is still present. Unfortunately I couldn’t prove it doesn’t either: with -intel, the first boot resulted in the ’low graphics mode’ failsafe dialog with Traces in dmesg (I’m attaching it). All subsequent boots resulted in panics that didn’t reveal a Trace, so they may or may not have been the one at hand. The panics still occurred when LDM should’ve launched, visually it either just showed the last lines of boot log or that with the mouse cursor. (The what’s-that-key was also blinking on the keyboard.)

Oho hei Syksyinen! Kaappaanpa härskisti tämän langan, ja kysyn, että oletko vaihtanut tyylilajia, vai onko joku napannut vanhan blogiosoitteesi uusiokäyttöön?

I’ve been waiting for an i386 build of RC5 to appear in the directory but it hasn’t. Should I try RC4 instead or keep waiting until a newer i386 build appears? AMD64 isn’t supported by the processor.

Unfortunately I didn’t make a note of when exactly the issue began. But I can give you a timeframe: it wasn’t there when I filed Bug #903831 on 2011-12-13, probably still not there on 2011-12-16 when I made comment #5 on the bug, and probably was there when I made comment #7 on that bug on 2012-01-06. (I’m being cautious with the ’probablies’ because of all the overlapping issues here.)

Again, thanks for the effort you put into your answers. After leaving the previous comments I felt slightly worried whether I’m too eager to dish out my kitchen psychology. These are deeply personal issues for you and for me to label you as this or that based on the little I (really) know about you is just my typical self-centeredness: I tend to get too fascinated with my own mental constructs to take into account that people I involve in them might not be as enthusiastic about them.

(Thanks for the video link btw, haven’t had time to properly watch it yet but I will.)