linux-kernel - Re: PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c96265a60707212156v5cfad301q8c3d75bf65863048@mail.gmail.com>
Date:	Sat, 21 Jul 2007 21:56:00 -0700
From:	"Mark Tiefenbruck" <mark@...xbox.org>
To:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+

> Can you please try the following command line options in any
> combination:
>
> hpet=disable
> nohz=off
> highres=off
> nolapic_timer

I've now tried running the kernel with all combinations of
hpet=disable, nolapic_timer, and clocksource=pm_timer|acpi_pm. I feel
like hpet=disable was probably unnecessary, since I have HPET disabled
in my BIOS. I didn't bother with nohz and highres=off, since I don't
believe those options are present in the version of the kernel I'm
testing. None of these made any difference, but I can try the rest of
the combinations, if you think I should. Just to make sure, I should
be placing these after the kernel path in grub.conf, right?

I noticed during these tests that the cursor still blinks when it
reaches the point where it stops printing things. This seems like good
evidence that, indeed, the kernel is still active but is waiting for a
response. Or maybe the hardware does that itself.

I checked on what happens when I enable HPET in my BIOS. In the
working kernel, it gets to the boot scripts and stops doing anything
useful when letting udev process events. With the newer kernels, it
halts in the same place as before.

So, what next? I am of course willing to give out reasonable
information about my system and try out patches.

  Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/