linux-kernel - Re: 2.6.19-rc <-> ThinkPads

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: <Pine.LNX.4.64.0611011616460.6462@blonde.wat.veritas.com>
Date:	Wed, 1 Nov 2006 16:36:51 +0000 (GMT)
From:	Hugh Dickins <hugh@...itas.com>
To:	Adrian Bunk <bunk@...sta.de>
cc:	"Michael S. Tsirkin" <mst@...lanox.co.il>,
	Pavel Machek <pavel@...e.cz>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	len.brown@...el.com, linux-acpi@...r.kernel.org, linux-pm@...l.org,
	Martin Lorenz <martin@...enz.eu.org>
Subject: Re: 2.6.19-rc <-> ThinkPads

On Wed, 1 Nov 2006, Adrian Bunk wrote:
> 
> Subject    : Thinkpad R50p: boot fail with (lapic && on_battery)
> References : http://lkml.org/lkml/2006/10/31/333
> Submitter  : Ernst Herzberg <earny@...4u.de>
> Status     : submitter was asked to bisect
> 
> It seems to be completely unrelated (except that it's also a ThinkPad), 
> but it might be worth a try whether a (non-SMP) kernel without APIC 
> support fixes the issues after resume.
> 
> Hugh, your laptop seems to be a non-SMP laptop.

That's right.

> Do you have APIC enabled, and if yes does disabling help?

Yes, I do.  But I've just tried booting with "noapic" and with "nolapic"
and with "noapic nolapic", but none of those make any difference.

(That is, they make no difference to the FnF4-ineffective-after-resume
behaviour that I'm finding fairly easy to reproduce at will today on
2.6.19-rc4; whereas yesterday it was seeming to me that -rc4 was much
better than -rc3 in this regard.  Something I have learnt today is that
the key is ineffective "for a while", but may become effective later.
It's conceivable that the behaviour I'm reproducing today is not quite
the same as what I was experiencing earlier with real-life suspends.)

More to the point, with great hope in my heart, I've tried backing
out Andi's git-cf4c6a2f27f5db810b69dcb1da7f194489e8ff88.patch
to arch/i386/kernel/io_apic.c, the one which Michael and Linus have
homed in on.  But sadly that makes no difference for me: I'd better
get down to my own bisection.

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