You are not logged in.
Pages: 1
Hello all
I recently had to re-install arch on my laptop (dell xps studio 1340) after not using it for a month or so and invoking the wrath of pacman -Syu after that much time. Upon re-installation I've run into something that I've never seen before with arch, a kernel panic.
Now this is a fresh install and I frankly have no idea how to even get the information off the trace / log that is spewing information at me (can't boot in and logs don't seem to be written to file before it halts). From what i can see, lots of annotations for [ite_cir] and [scsi_mod], but nothing too descriptive. (mostly just addresses, modules and offsets with a few IRQ's thrown in for good measure)
I've attempted re-installs and fallback boots, every time getting the same thing. Searches on kernel panics in the various boards always turns up short logs with easily identifiable problems (forgetting to set locale) and systems that aren't fresh.
I have no idea where to begin with this problem or even trying to pinpoint what is suddenly wrong.
Any help at this point is greatly appreciated!
beauzeaux
Offline
Hi,
check whether the kernel and initscripts know where your root partition is. This error may indicate that your root is not mounted during boot. It might be related to those errors you are describing, indicating trouble with harddrive..
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
I tried to install arch today, and got the same problem. I did the netinstall, panic. After I tried the core install, the system worked fine until I did the update (after solving some issues with the PGP keys and the modprobe.conf). After the reboot, the kernel simply crashes. Does anyone here did a full system update today?
Last edited by Fixo (2012-04-02 02:54:22)
Offline
Ok, checked the root param passed on boot and it seemed ok. (uuid was same as the root partition). But for thoroughness' sake i changed it to /dev/sda3 to make sure. Same errors.
I'll put up a picture of the output as soon as i can find a way of getting it to fit on one screen.
Side note: if it is the hard drive failing i'd be shocked its a 5month old SSD that's worked beautifully for quite some time now
Offline
My HD is a brand new WD "caviar blue"... I think our hardware are ok.
Last edited by Fixo (2012-04-02 02:54:41)
Offline
Long (read) answer: Is it similar to what's in this thread?
Short answer: try appending 'pcie_aspm=force' to your bootloader kernel line.
Burninate!
Offline
Ok an update,
First, yes, I've tried pcie_aspm=force to no avail.
I've managed to get a bit more of the trace by tinkering with the vesa mode lines. Looks like something is amiss with udev. I've uploaded a screenshot here (sorry for the crud quality, even with a tripod i got ghosting on the characters)
I've checked the installation medium, it works fine on another computer. I've run memcheck passed 9 tests with no errors. So i'll try another os of a glass pane variety to ensure the rest of the hardware is still functional.
I'll post back here with results.
Offline
pcie_aspm=force worked for me, I saw that thread yesterday, thank you.
Offline
Hi!
I seem to have exactly the same problem with my Dell Studio XPS 1340. pcie_aspm=force didn't work for me neither.
Is there any update so far?
Best regards,
antesilvam
Offline
Ok, I found some hint in the German arch forum (https://bbs.archlinux.de/viewtopic.php?id=21136):
The IR module 'ite_cir' seems to create the problems. So blacklisting this module helped in my case.
/etc/modprobe.d/blacklist.conf:
------------------------------------------
blacklist ite_cir
Offline
Pages: 1