linux-kernel - Re: [Bisected] Regression: Hang on boot in schedule_timeout

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] [day] [month] [year] [list]

Message-ID: <20080728182420.GB3697@redhat.com>
Date:	Mon, 28 Jul 2008 15:24:21 -0300
From:	Glauber Costa <gcosta@...hat.com>
To:	Andrew Drake <drakedevel.lists@...il.com>
Cc:	Andrew Drake <zappacky.lists@...il.com>,
	Glauber Costa <glommer@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [Bisected] Regression: Hang on boot in
	schedule_timeout_interruptible during ACPI init on SMP

On Mon, Jul 28, 2008 at 12:46:09PM -0400, Andrew Drake wrote:
> On Mon, Jul 28, 2008 at 10:15 AM, Glauber Costa <gcosta@...hat.com> wrote:
> > fine, but if you can still help us on this, it would be awesome ;-)
> >
> 
> Oh absolutely! :P I'm not the type to settle on a workaround.
> 
> > Actually, there is another nasty bug that depends, at least by a first
> > impression, on the lapic timer. I'm planning to save a time today to
> > look further on your problem.
> 
> Thanks!
> 
> >
> > Probably because the order of initialization of smp entities changed a
> > bit during this series. Probably the lapic timer is now initialized a
> > little bit earlier, before we have the chance to mark it as bad.
> >
> 
> I noticed that; but I couldn't find where it was indeed marked as bad.
FYI: Bug 11101 (http://bugzilla.kernel.org/show_bug.cgi?id=11101) is probably
the same bug as yours. I've just updated a possible solution in there.
Could you verify that?

Thanks!

> 
> > If you can send me at least your dmesgs and cpuinfo, it would be really really
> > awesome.
> >
> 
> Did you get my most recent email? (It was sent to your glommer[at]
> address, and CC'd to the kernel list) If you didn't receive it, I'll
> forward you the message. It included dmesg of good kernel, dmesg of
> bad kernel, cpuinfo, .config, and my disassembled DSDT (which, as a
> side project, I'm doing a full-blown reverse engineering of).
> 
> Thanks,
> 
> Andrew
> 
> P.S. I apologize in advance if this email is HTML, I'm at work and I
> have to use the gmail web interface, I have it set to "text only", but
> you never know.
--
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/