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: <20070604203158.GB8456@rhlx01.hs-esslingen.de>
Date:	Mon, 4 Jun 2007 22:31:58 +0200
From:	Andreas Mohr <andi@...x01.hs-esslingen.de>
To:	Antonio Mignolli <antoniomignolli@...il.com>
Cc:	linux-kernel@...r.kernel.org, Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: lid switch hangs notebook

Hi,

On Mon, Jun 04, 2007 at 10:26:05PM +0200, Antonio Mignolli wrote:
> Interesting...
> The lid problem was solved, but many others arised.
> I don't remember what lapic is, I didn't put the lapic on kernel
> command line, but it seemed to be active by default:
> # find /sys -name "*lapic*"
> /sys/devices/system/lapic_nmi
> /sys/devices/system/lapic_nmi/lapic_nmi0
> /sys/devices/system/lapic
> /sys/devices/system/lapic/lapic0
> 
> I put a "nolapic" in cmdline, and this time no hangs,
> even WITH acpi support in kernel, pressing the button
> a dozen of times (without nolapic it hanged after a couple of times).

Just sounds like local APIC issues are really wide-spread then ;)
I'm really wondering whether it's the kernel which is not doing enough here.
Too many BIOSes with issues, it seems.

> BUT:
> - Module b44 (broadcom network adapter) fails to load, giving,
>    with debug actived:
>    b44 0000:01:0e.0: Cannot find proper PCI device base address, aborting.

Known issue I think, b44 stuff was discussed on LKML very recently.

> - Alsa does not work

Hmm. Known issue, too, I think. ALSA stuff was... (c.f. above ;).

> ... No time for analyze other issues.
> 
> Thanks for helping,
> I'll take a look to lapic.

Maybe try pci=routeirq or some other useful parameters from
Documentation/kernel-parameters.txt.

And believe me that I'll take a HARD look at lapic stuff, too.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ