linux-kernel - Re: 2.6.29-rc1 does not 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: <20090111153548.GB7401@elte.hu>
Date:	Sun, 11 Jan 2009 16:35:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Dieter Ries <clip2@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc1 does not boot


* Dieter Ries <clip2@....de> wrote:

> Ingo Molnar schrieb:
> > * Dieter Ries <clip2@....de> wrote:
> > 
> >> Hi,
> >>
> >> I just pulled 2.6.29-rc1, ran oldconfig with defaults and built it.
> >> When I try to boot it, that kind of works until init should start. Then
> >> nothing happens. I tried with init=/bin/bash, which sometimes works, and
> >> sometimes gets me a bash without the prompt flashing.
> >>
> >> I captured the output with netconsole, but I cannot see a problem there.
> >> It is attached.
> >>
> >> My config is also attached.
> >>
> >> The machine:
> >>
> >> Lenovo Thinkpad T60
> >> Core2Duo 2GHz
> >>
> >> Gentoo 64bit
> >>
> >> Everything worked fine with 83bc66f, which was my last pull.
> >>
> >> What else should I provide for debugging that?
> > 
> > hm, there's no 83bc66f in Linus's tree.
> 
> Sorry, thats because I applied Timo Hoenigs patch for the fingerprint
> reader. So the right commit where it worked is 6680598.
> 
> Before pulling today, I reverted that patch, to avoid conflicts, so I
> guess it should not matter.

in the 6680598..v2.6.29-rc1 window there's more than 3000 commits: there 
were libata and IDE changes, x86 changes, cpumask changes, ACPI changes 
and more. Any of those categories could produce such error symptoms as 
your box is showing.

Unless you can see some particular badness in the kernel messages 
(something that changed to the last working version) that narrows it down 
to some subsystem, i suspect this would have to be bisected ...

	Ingo
--
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/