linux-kernel - Re: 2.6.26-rc1 fails to boot

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: <20080510222201.GA3754@beyonder.ift.unesp.br>
Date:	Sat, 10 May 2008 19:22:01 -0300
From:	"Carlos R. Mafra" <crmafra2@...il.com>
To:	Henny Wilbrink <wsdwhw@....tue.nl>
Cc:	linux-kernel@...r.kernel.org, venkatesh.pallipadi@...el.com
Subject: Re: 2.6.26-rc1 fails to boot

On Sat 10.May'08 at 22:21:28 +0200, Henny Wilbrink wrote:
Content-Description: message body text
> Hello,
> 
> Kernel 2.6.26-rc1 completely fails to boot on my laptop. The last line
> appearing on the console is:
> 
> ACPI: Processor [CPU1] (supports 8 throttling states)

Does booting with hpet=disable help?

> Kernel 2.6.25 fails to boot in an estimated 1 in 2 attempts.  The last
> line on the console if this one fails is:
> 
> ACPI: LNXTHERM:01 is registered as thermal_zone0
> 
> I did a git bisection with "fails to boot in the first three attempts"
> as the definition of "bad" between 2.6.26-rc1 and 2.6.25-rc3 which I
> believed to be free of this problem.  The many reboots in the
> bisection process however showed me that 2.6.25-rc3 also has an
> estimated 1 in 10 chance of failing.  Anyway, the bisection ended
> with:
> 
> 8a3227268877b81096d7b7a841aaf51099ad2068 is first bad commit
> 
> The bisection log and dmesg are attached.

I have this boot problem since before 2.6.25-rc1 but it is
very difficult to do a bisection. Sometimes the probability
of hanging was 1:30 and what I thought was a good kernel in
fact was bad.

In fact the commit you got is a "merge commit" which does not
change the source code so it is clearly bogus.

Mark Lord points out that this bug comes and goes with slight
modifications in the .config, and in fact very recently 
the probability of hanging changed dramatically for me.

I have already booted the kernel afa26be86b65 (six commits
after 2.6.26-rc1) more than 30 times and it did not hang.

You can also take a look at some discussion here:
http://bugzilla.kernel.org/show_bug.cgi?id=10117

And good luck with this!
--
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/