Re: Pinpointing faulty kernel driver?
On Wed, 28 Mar 2012 11:07:15 +0200, Lars wrote in message
<[🔎] 20120328090715.GA4262@starfish.lan>:
> Hi all
>
> When upgrading kernel series 3.1.0 to series 3.2.0, suddenly my system
> won't boot. It hangs with the message
>
> Waiting for /dev to be fully populated
..me 2, upgrading from 3.2.0-1-rt-amd64 to 3.2.0-2-rt-amd64:
arnt@celsius:~/FG-git$ dpkg -l |grep linux-image
ii linux-image-3.2.0-1-amd64 3.2.4-1 Linux 3.2 for 64-bit PCs
ii linux-image-3.2.0-1-rt-amd64 3.2.4-1 Linux 3.2 for 64-bit PCs,
PREEMPT_RT
ii linux-image-3.2.0-2-amd64 3.2.12-1 Linux 3.2 for 64-bit PCs
ii linux-image-3.2.0-2-rt-amd64 3.2.12-1 Linux 3.2 for 64-bit PCs,
PREEMPT_RT
arnt@celsius:~/FG-git$ uname -a
Linux celsius 3.2.0-1-rt-amd64 #1 SMP PREEMPT RT Sun Feb 5 15:51:02 UTC
2012 x86_64 GNU/Linux
arnt@celsius:~/FG-git$
> I read the manual and found out how to drop into the initramfs debug
> shell, but I am unsure how to proceed from here. I guess the problem
> could be a faulty driver that I need to disable, but I know of no
> (efficient) way to find out which one. Ideally, I would load one
> driver at a time, and see when the problem occurs.
>
> Can anyone help? Or am I completely off track with this problem?
>
> I am running the latest packages in both kernel series, and the 3.1
> series does not have the problem.
>
> Regards
>
> Lars
>
>
--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
Reply to: