linux-kernel - genirq,x86_64: Genirq patch (b4bc724e82) makes Compaq Presario V6000 hang during 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAF1_xX205BcA_r77UhxXNYw1YwUAnTvHUAO7ONfioZ38KdRq9Q@mail.gmail.com>
Date:	Thu, 12 Apr 2012 08:16:04 +0200
From:	Ronald <ronald645@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: genirq,x86_64: Genirq patch (b4bc724e82) makes Compaq Presario V6000
 hang during boot

Please CC me as I'm not subscribed to this list.

Recently I found out that my laptop hangs during boot with recent kernels.
It began with stable 3.2.9 and then I confirmed that with 3.3.1 had
the same issue.
Using git I tried the latest head of a few days ago (f4e52e7ffde)
which also hanged.
Reverting the following patch fixes the issue for me on all versions.

commit b4bc724e82e80478cba5fe9825b62e71ddf78757
Author: Thomas Gleixner <tglx@...utronix.de>
Date:   Wed Feb 8 11:57:52 2012 +0100

    genirq: Handle pending irqs in irq_startup()

    An interrupt might be pending when irq_startup() is called, but the
    startup code does not invoke the resend logic. In some cases this
    prevents the device from issuing another interrupt which renders the
    device non functional.

    Call the resend function in irq_startup() to keep things going.

    Reported-and-tested-by: Russell King <rmk+kernel@....linux.org.uk>
    Cc: stable@...r.kernel.org
    Signed-off-by: Thomas Gleixner <tglx@...utronix.de>

I have attached my .config [1] and a photo of the latest hanging kernel [2]
which is post 3.4 rc-2 by now (f549e088b80). I also attached a correctly
working dmesg of current head (again f549e088b80) with the offending
patch reverted [3].

So I opened a bug for this in the bugtracker [4]. So far there has
been no response,
so I suppose I classified it incorrectly.
Sorry for that.

Therefore I'm posting this message here to notify you of my
incorrectly placed bugreport.
And for suggestions on how to proceed. The kernel reliably hangs and I don't see
any output. Using SYSRQ does not help either.

Please, if the correct people are already aware of this bug then
ignore this mail.
And sorry for the noise. I'm still sending this since I believe this
is quite important
and should be fixed before the final release. Again, sorry for the
noise if this mail
is superfluous.

[1] http://pastebin.com/fvWAqmqv
[2] http://tinypic.com/view.php?pic=2uif21j&s=5
[3] http://pastebin.com/QmMA6hGS
[4] https://bugzilla.kernel.org/show_bug.cgi?id=43069

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