linux-kernel - Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

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: <201102042136.20165.rjw@sisk.pl>
Date:	Fri, 4 Feb 2011 21:36:19 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
Cc:	Richard Schütz <r.schtz@...nline.de>,
	Lionel Debroux <lionel_debroux@...oo.fr>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	platform-driver-x86@...r.kernel.org
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

On Friday, February 04, 2011, Ozan Çağlayan wrote:
> Cuma 04 Şubat 2011 günü (saat 00:51:31) Rafael J. Wysocki şunları yazmıştı:
> 
> > Hmm.  Are those boxes uniprocessor running SMP kernels?
> 
> The kernel is SMP.
> 
> ASUS X61S is 
>  CPU0: Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz stepping 0a
> 
> F50SV has 2 CPU's too according to dmesg:
> [    0.000000] Processor #0 (Bootup-CPU)
> [    0.000000] Processor #1
> [    0.000000] I/O APIC #2 Version 20 at 0xFEC00000.
> [    0.000000] IOAPIC[0]: apic_id 2, version 20, address 0xfec00000, GSI 0-23
> [    0.000000] Processors: 2
> [    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
> 
> ASUS N51JQ (occasional shutdown hang) has:
> CPU0: Intel(R) Core(TM) i7 CPU       Q 740  @ 1.73GHz stepping 05
> [    0.132435] Booting Node   0, Processors  #1 #2 #3 #4 #5 #6 #7 Ok.
> [    0.768809] Brought up 8 CPUs

OK, so it's not the case I was thinking of.  Ohwell.

At this point I guess it's best to open a bug entry in the kernel Bugzilla,
against ACPI (although ACPI may be a red herring), and put some system
information (ie. dmesg outputs from working kernels, if any, outputs of
acpidump) -- or links to where it can be found.

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