I don’t see the syslog I mentioned attached above, so I’m attaching it here. Also, the USB-related stuff just preceding the panic starts slightly earlier than what I claimed above, with this reset attempt:
Jan 7 10:45:01 saegusa kernel: [ 413.991127] usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Last week I replaced the internals of my desktop computer with a new ASUS P8H77-M PRO, Intel G2120 and 16 GB RAM. With one round of Memtest passed, I booted into my old Precise install and got bit hard by what appears to be Bug #993187: frequent hard lockups (multiple within a few hours of use). I installed linux-image-generic-lts-quantal (currently 3.5.0.22.29) and that seemed to resolve the lockups: I got more than two days of uptime (ending with an intended shutdown), half of which I was actively using the computer.
This morning, soon (half an hour?) after login, the kernel paniced with a reference to usb-storage (I’ll attach a picture). This was different from the lockups with the stock Precise (3.2) kernel: with them I never had any panics shown (only the frozen desktop) and the system had to be powered off to reboot, whereas with the panic here I could reboot using the chassis reset button.
There’s some USB activity in syslog just prior to the panic (Jan 7 at around 10:50), but I wasn’t using any USB devices at the time. I have used them with this kernel previously though, without issues, and currently am too (to transfer the panic picture from my phone). There’s a memory card reader/USB port panel (Akasa AK-ICR-17) permanently plugged into internal USB 2 and 3.
Rolling release oli muistaakseni… juu, Arch kuten muistelinkin.
From a similar question on ServerFault (and particularly one response there), one possible explanation for the disparity is that there are processes hanging on to files they’ve accessed on /tmp that have since been deleted.
# lsof | grep deleted will list such files along with the processes still attached to them.
Ahem. It now looks like non-pae + wistron doesn’t work either. But this looks more like a configuration issue on my part, I’ll have to investigate it further. It still doesn’t freeze or anything, it’s just that the wireless doesn’t go online.
Luis, there actually was a BIOS upgrade available from Fujitsu [1], thanks for prompting me to look! I flashed the latest revision S0Z in (it was S0U until now), but unfortunately this didn’t change the behavior at issue here. (There was no mention of the wireless in manufacturer’s changelog either, but those are often incomplete anyway.)
*[1] http://download.ts.fujitsu.com/download/ShowDescription.asp?SoftwareGUID=1968BB6F-7819-4C8C-A488-BAA44C111F7C
Thanks for commenting, Luis. I booted with noexec=off a couple of times with 3.2.0-24-pae, but it didn’t seem to change anything, i.e. the boot still (seemingly) froze when wistron_btns was enabled.
I was unaware of fsam7400 prior to this, so I tried that too, instead of wistron_btns. With fsam7400, the -pae kernel boots fine here even without noexec=off, apart from a ”Waiting for network” , and the wireless network never coming up (can’t bring it up from the desktop either). So here, at least, the noexec=off workaround isn’t needed with fsam7400, though it isn’t much good wrt the wireless either.
To reiterate: the only way currently to have this system boot with the wireless working is to have wistron_btns enabled and to use a non-pae kernel.
I should mention that I’ve upgraded the laptop to Quantal.
I should also mention that Precise’s mainstream installation media refused to boot on the laptop. I believe the message was ”This kernel requires the following features not present on the CPU: pae”. This despite the fact that the -pae kernels, once a system has been installed, *do* boot and work just fine, albeit not with wistron_btns loaded. So currently I’m unsure whether the CPU actually supports pae or not.
I’ve just hit the Oops (__ticket_spin_lock+0x9/0x30) with apw’s kernel. I’ll attach the syslog from after reboot to this comment. Had been running the apw build since Monday this week (7 days now) without problems.
Just to note here also that I’ve today switched to apw’s build of 3.2.0-23 [1] linked to from bug 922906. I had been running the upstream 3.3 for more than 7 weeks without hitting this (#917668). The GPU lockup I mentioned in #13 also never reoccurred since that one time.
I’ll report back, should #917668 resurface with the kernel I’m currently running.
* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922906/comments/11
Bryce; no problem (and thanks for your working on this), for me the fbdev workaround is good enough to work and live with on this setup. If others affected by this feel differently, do take over with upstream.