[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689420: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)



But this is a bug report, not a support request.
Yes.
... So 'unusable' should
be considered in relation to all users, not a particular user.
This view is nowhere stated officially on the aforementioned page.

> Windows runs on the computer without problems and the computer is new,
> so a hardware fault is unlikely. As soon as I run some testing
> program, I'll report here again.

Sometimes new hardware can fail very quickly.     But if Windows is working
on the same system then this definitely points to a software problem.
Windows is working.
The BIOS setup of this DELL machine offers extensive tests of about 20 minutes length, including memory and CPU tests.
I ran them, and no problems were detected. If you want me to try some other extensive testing, please tell me so.

Alas, "boot_delay=1000" does not slow down printing.
It just introduces a pause right after blanking the screen at boot, but before quickly printing pages of information.
Thus, to get usable screenshots from a failing boot, I have to do some preparation.
I have two kernels installed, one from testing (linux-image-3.2.0-3-amd64, version 3.2.23-1), and the other from unstable (linux-image-3.2.0-4-amd64, version 3.2.32-1).
Both can be run with or without "acpi=off", with or without "quiet", with or without "elevator=noop" (currently used, since an SSD is inside), with or without "boot_delay=1000", normally or in a repair mode.

E. g., attached is a screenshot of a boot of kernel 3.2.0-4, with "acpi=off quiet elevator=noop".
The machine in the state you see does not boot further but remains responsive to Ctrl+Alt+Del, which performs a reboot.

For which kernel and which choice of options do you want to see a series of screenshots of the failing boot sequence?

Today the kernel started to boot sometimes without artificial delays at grub time (but still with acpi=off) again.
While last time it continuously refused to boot without artificial delays.
There are a few differences between last time and today:
- the date
- the usual kernel-irrelevant updates of the testing distribution (dpkg being probably the most important updated package)
- 18G of stuff has been copied onto the machine's drive.

Jaakov. 

Attachment: Foto-0130.jpg
Description: JPEG image


Reply to: