Last Sunday I’ve run an update for my 12.1 x64 running off an external HDD (my internal has to be replaced) with the new btrfs File system.
It updated fine on Sunday, then I started it once on monday to get some info from the net - all went well, after I returned from Univeristy to get to answering mails I the farthest point I got with the system was the login-screen.
After that the system crashes with a lot of messages which I unfortunately can’t copy here as I can’t access the bootlogs on the drive (gonna try rescue install now that I’ve got the media).
But as I’ve hooked the drive up to my main PC running 11.4x64 and tried to mount the root partition there I get the following messages:
Message from syslogd@LinDevNV at Dec 26 11:01:10 ...
kernel:[204950.989738] ------------ cut here ]------------
Message from syslogd@LinDevNV at Dec 26 11:01:10 ...
kernel:[204950.989762] invalid opcode: 0000 #1] PREEMPT SMP
Message from syslogd@LinDevNV at Dec 26 11:01:10 ...
kernel:[204950.989934] Stack:
Message from syslogd@LinDevNV at Dec 26 11:01:10 ...
kernel:[204950.989957] Call Trace:
Message from syslogd@LinDevNV at Dec 26 11:01:10 ...
kernel:[204950.990005] Code: 89 f7 ba b0 00 00 00 e8 48 9f 02 00 48 8b 54 24 28 4c 89 fe 4c 89 f7 e8 38 a0 02 00 eb 87 66 0f 1f 44 00 00 b8 f4 ff ff ff eb a8 <0f> 0b 49 8b 54 24 09 49 8b 34 24 48 c7 c7 88 3d e5 a0 31 c0 e8
Message from syslogd@LinDevNV at Dec 26 11:01:39 ...
kernel:[204979.782328] ------------ cut here ]------------
Message from syslogd@LinDevNV at Dec 26 11:01:39 ...
kernel:[204979.782350] invalid opcode: 0000 #2] PREEMPT SMP
Message from syslogd@LinDevNV at Dec 26 11:01:39 ...
kernel:[204979.782520] Stack:
Message from syslogd@LinDevNV at Dec 26 11:01:39 ...
kernel:[204979.782543] Call Trace:
Message from syslogd@LinDevNV at Dec 26 11:01:39 ...
kernel:[204979.782739] Code: 89 f7 ba b0 00 00 00 e8 48 9f 02 00 48 8b 54 24 28 4c 89 fe 4c 89 f7 e8 38 a0 02 00 eb 87 66 0f 1f 44 00 00 b8 f4 ff ff ff eb a8 <0f> 0b 49 8b 54 24 0
I remember vividly that same Opcodes appear when I try to boot the laptop.
Switching to system-V does not help - even the failsafe mode dies after some time, though it is the only one where I can actually login into the system - sometimes.
Anybody encounter same problem?
I’d make “tabula rasa” on the drive, but there are papers for University I’ve written and haven’t yet copied to any other location…
Whether it be Installation, or rescue system booting from the DVD - the result is always the same.
Booting the rescue system with Safe Mode kernel results in a system with a blank screen. As that state does not change for over 5 min. I concur that it hangs.
Booting the default kernel to rescue system (& install) results in hanging when loading the iwlagn module. As the NumLock & CapsLock lights flash I deduce that Kernel Panic occurs - though it is not explicitly written (but the symptoms are same).
I have absolutely no more ideas what has gone wrong and what to try.
> Booting the default kernel to rescue system (& install) results in
> hanging when loading the iwlagn module. As the NumLock & CapsLock lights
> flash I deduce that Kernel Panic occurs - though it is not explicitly
> written (but the symptoms are same).
>
> I have absolutely no more ideas what has gone wrong and what to try.
>
> Any help is greatly appreciated…
If you have a real serial port in that machine you can use it to dump
kernel messages to another machine.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2011-12-26 16:16, Aquinox wrote:
>
> That would be an option, were my problem not focused on the laptop. It
> has just a VGA out apart from the usual 1394, USB, SD, FX.
Bad luck.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Well. I managed to get a hold on the kernel messages from my laptop. Tried to mount the partition in question on my main PC while keeping an eye on “dmesg”. The lines which came up look pretty much the same as on my laptop
so just as additional info here they are: