linux-kernel - Re: 2.6.18-rc3-mm2

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]

Date:	Mon, 7 Aug 2006 22:34:12 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
	Jens Axboe <axboe@...e.de>
Subject: Re: 2.6.18-rc3-mm2

On Monday 07 August 2006 11:15, Rafael J. Wysocki wrote:
> On Monday 07 August 2006 00:54, Andrew Morton wrote:
> > On Mon, 7 Aug 2006 00:42:10 +0200
> > "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> > 
> > > On Sunday 06 August 2006 12:08, Andrew Morton wrote:
> > > > 
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc3/2.6.18-rc3-mm2/
> > > 
> > > My box's (Asus L5D, x86_64) keyboard doesn't work on this kernel at all, even
> > > if I boot with init=/bin/bash.  On the 2.6.18-rc2-mm1 it worked.
> > > 
> > > Unfortunately I have no indication what can be wrong, no oopses, no error
> > > messages in dmesg, nothing.
> > > 
> > > Right now I'm doing a binary search for the offending patch.
> > > 
> > 
> > Thanks.  I'd zoom in on
> > hdaps-handle-errors-from-input_register_device.patch and git-input.patch.
> 
> None of these, but close: remove-polling-timer-from-i8042-v2.patch breaks
> things here.  [FYI, the box is booted with "noapic", because the IRQ sharing
> doesn't work otherwise due to a BIOS issue, so it may be related.]
> 
> Attached is the dmesg output with i8042.debug=1 for Dmitry.  It's from
> 2.6.18-rc3 with -mm2 partially applied (up to and including
> logips2pp-fix-mx300-button-layout.patch).  I'll apply the rest tonight, after
> I find the patch that broke suspend for me.

Unfortunately this one is git-block.patch.  I have no idea which part of it
may break the suspend.

It hangs during suspend, right after the memory has been shrunk, when devices
should be suspended.  After pressing SysRq-P it shows it's spinning in the
idle thread and then hangs hard.

Greetings,
Rafael
-
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/