[Bug 9429] acpi-cpufreq boot crash

2008-01-01 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment

[Bug 9429] acpi-cpufreq boot crash

2007-12-05 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #21 from

[Bug 9429] acpi-cpufreq boot crash

2007-12-05 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #22 from [EMAIL PROTECTED] 2007-12-05 20:20 --- Created an attachment (id=13882) -- (http://bugzilla.kernel.org/attachment.cgi?id=13882action=view) patch from comment #20 backported to linux-2.6.16, 2.6.17 -- Configure

[Bug 9429] acpi-cpufreq boot crash

2007-12-05 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #23 from [EMAIL PROTECTED] 2007-12-05 20:34 --- Created an attachment (id=13883) -- (http://bugzilla.kernel.org/attachment.cgi?id=13883action=view) patch from comment #20 backported to linux-2.6.18, 2.6.19, 2.6.20 --

[Bug 9429] acpi-cpufreq boot crash

2007-12-02 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #20 from [EMAIL PROTECTED] 2007-12-02 11:32 --- Created an attachment (id=13831) -- (http://bugzilla.kernel.org/attachment.cgi?id=13831action=view) patch vs 2.6.24-rc3 verified that this patch, cherry-picked from the

[Bug 9429] acpi-cpufreq boot crash

2007-12-02 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 9429] acpi-cpufreq boot crash

2007-11-26 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment

[Bug 9429] acpi-cpufreq boot crash

2007-11-26 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #19 from [EMAIL PROTECTED] 2007-11-26 14:38 --- Verified failure on 20070919, works correctly on 20071019: - ex _psd Executing \_PSD Execution of \_PSD returned object 00327E40 Buflen 70 [Package] Contains 1 Elements:

[Bug 9429] acpi-cpufreq boot crash

2007-11-24 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #16 from [EMAIL PROTECTED] 2007-11-24 06:03 --- I do see few examples in ACPI spec which has Return (Package(x)) {} syntax. That must be valid. Isn't it? -- Configure bugmail:

[Bug 9429] acpi-cpufreq boot crash

2007-11-23 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #11 from [EMAIL PROTECTED] 2007-11-23 00:40 --- Created an attachment (id=13705) -- (http://bugzilla.kernel.org/attachment.cgi?id=13705action=view) console log 2.6.24+ w/o ACPI tracing debugging enabled all debug flags at

[Bug 9429] acpi-cpufreq boot crash

2007-11-23 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #13705|0 |1 is obsolete|

[Bug 9429] acpi-cpufreq boot crash

2007-11-23 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #13 from [EMAIL PROTECTED] 2007-11-23 09:57 --- Created an attachment (id=13719) -- (http://bugzilla.kernel.org/attachment.cgi?id=13719action=view) CPU1IST.dat $ acpidump -a 0x7DFB0720 -l 0x0359 CPU1IST.dat --

[Bug 9429] acpi-cpufreq boot crash

2007-11-23 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #12 from [EMAIL PROTECTED] 2007-11-23 09:56 --- Created an attachment (id=13718) -- (http://bugzilla.kernel.org/attachment.cgi?id=13718action=view) CPU0IST.dat -- Configure bugmail:

[Bug 9429] acpi-cpufreq boot crash

2007-11-23 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED]|[EMAIL PROTECTED] |m

[Bug 9429] acpi-cpufreq boot crash

2007-11-22 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #8 from [EMAIL PROTECTED] 2007-11-22 00:23 --- Created an attachment (id=13690) -- (http://bugzilla.kernel.org/attachment.cgi?id=13690action=view) console log 2.6.24-rc3+ 64-bit Yes, 64-bit mode fails too. Attached is a

[Bug 9429] acpi-cpufreq boot crash

2007-11-22 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #10 from [EMAIL PROTECTED] 2007-11-22 23:34 --- The 93,414th call to acpi_ns_get_parent_node() caused the crash. It was passed a namespace node... at address 81007d8544c8. node-name node-flags 6b node-peer

[Bug 9429] acpi-cpufreq boot crash

2007-11-21 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #2 from [EMAIL PROTECTED] 2007-11-21 11:11 --- Created an attachment (id=13674) -- (http://bugzilla.kernel.org/attachment.cgi?id=13674action=view) console log 2.6.24-rc3+ w/ CONFIG_DEBUG_SLAB=n -- Configure bugmail:

[Bug 9429] acpi-cpufreq boot crash

2007-11-21 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #3 from [EMAIL PROTECTED] 2007-11-21 11:11 --- Created an attachment (id=13675) -- (http://bugzilla.kernel.org/attachment.cgi?id=13675action=view) acpidump -- Configure bugmail:

[Bug 9429] acpi-cpufreq boot crash

2007-11-21 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #4 from [EMAIL PROTECTED] 2007-11-21 11:13 --- typo: comment #1 is 2.6.24-rc3+, not .23-rc3+ The system under test is a Weybridge SDV with a dual core processor. -- Configure bugmail:

[Bug 9429] acpi-cpufreq boot crash

2007-11-21 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #5 from [EMAIL PROTECTED] 2007-11-21 16:32 --- Len, Can you attach your config. Also, do yo see the problem with 64 bit kernel as well? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ---

[Bug 9429] acpi-cpufreq boot crash

2007-11-21 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=9429 --- Comment #6 from [EMAIL PROTECTED] 2007-11-21 17:02 --- 0x6b is POISON_FREE. SLAB and SLUB debug sets the freed area to 0x6b. But, somewhere in the linked list there is still an active pointer to some freed area which we try to