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

Message-ID: <488B7297.8090405@gmail.com>
Date:	Sat, 26 Jul 2008 14:53:11 -0400
From:	Andrew Drake <zappacky.lists@...il.com>
To:	Glauber Costa <glommer@...il.com>
CC:	linux-kernel@...r.kernel.org, gcosta@...hat.com
Subject: Re: [Bisected] Regression: Hang on boot in schedule_timeout_interruptible
 during ACPI init on SMP

I just discovered; the nolapic_timer parameter causes the problem to go away 
entirely. It doesn't seem to have any nasty side effects, so I'm content to use 
it. Looking at the dmesg logs, however, I notice that the "last-good" kernel 
doesn't even try to use the LAPIC timer, but the "first-bad" does. I wasn't able 
to track down any discernible reason.

On a side note, that's the first I've ever heard/seen of that parameter, I tried 
it because I noticed the problems started when the LAPIC timer was successfully 
set up. I doubt the average user would notice this (you can't even tell unless 
you pass apic=debug), so I doubt many others would discover this fix/workaround.

The question remains, though, why did it go from "don't try" to "try"?

Thanks,

Andrew

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