Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
Applied.
thanks,
-Len
On Friday 08 June 2007 14:12, Andrew Morton wrote:
> On Fri, 8 Jun 2007 17:15:45 +0800
> "Luming Yu" <[EMAIL PROTECTED]> wrote:
>
> > The only problem known as to the acpi throttling changes in the mm tree
> > is a typo ,and the patch to fix it is available here. Please test and
> > get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
> > problem. Would please also try not to load acpi-cpufreq.
> >
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
>
> Sigh. Is this some sort of contest to see how many things we can
> do wrong in a single patch?
>
> - Include a changelog
>
> - Include Signed-off-by:
>
> - Don't use attachments
>
> - If you _must_ use attachments, use text/plain, not application/octet-stream
>
> - Format code to remain within 80 columns.
>
> - Don't do "if(". Do "if ("
>
> Oh well. Good to hear that the oops got fixed, thanks.
>
>
> From: "Luming Yu" <[EMAIL PROTECTED]>
>
> Cc: Len Brown <[EMAIL PROTECTED]>
> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
> ---
>
> drivers/acpi/processor_throttling.c |6 --
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff -puN
> drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
> drivers/acpi/processor_throttling.c
> ---
> a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
> +++ a/drivers/acpi/processor_throttling.c
> @@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
> pr->throttling.state_count - 1);
>
> seq_puts(seq, "states:\n");
> - if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
> + if (pr->throttling.acpi_processor_get_throttling ==
> + acpi_processor_get_throttling_fadt) {
> for (i = 0; i < pr->throttling.state_count; i++)
> seq_printf(seq, " %cT%d: %02d%%\n",
> (i == pr->throttling.state ? '*' : ' '), i,
> (pr->throttling.states[i].performance ? pr->
> throttling.states[i].performance / 10 : 0));
> - else
> + } else {
> for (i = 0; i < pr->throttling.state_count; i++)
> seq_printf(seq, " %cT%d: %02d%%\n",
> (i == pr->throttling.state ? '*' : ' '), i,
> (int)pr->throttling.states_tss[i].
> freqpercentage);
> + }
>
>end:
> return 0;
> _
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
Applied.
thanks,
-Len
On Friday 08 June 2007 14:12, Andrew Morton wrote:
On Fri, 8 Jun 2007 17:15:45 +0800
Luming Yu [EMAIL PROTECTED] wrote:
The only problem known as to the acpi throttling changes in the mm tree
is a typo ,and the patch to fix it is available here. Please test and
get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
problem. Would please also try not to load acpi-cpufreq.
http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
Sigh. Is this some sort of contest to see how many things we can
do wrong in a single patch?
- Include a changelog
- Include Signed-off-by:
- Don't use attachments
- If you _must_ use attachments, use text/plain, not application/octet-stream
- Format code to remain within 80 columns.
- Don't do if(. Do if (
Oh well. Good to hear that the oops got fixed, thanks.
From: Luming Yu [EMAIL PROTECTED]
Cc: Len Brown [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/acpi/processor_throttling.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN
drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
drivers/acpi/processor_throttling.c
---
a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
+++ a/drivers/acpi/processor_throttling.c
@@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
pr-throttling.state_count - 1);
seq_puts(seq, states:\n);
- if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
+ if (pr-throttling.acpi_processor_get_throttling ==
+ acpi_processor_get_throttling_fadt) {
for (i = 0; i pr-throttling.state_count; i++)
seq_printf(seq,%cT%d: %02d%%\n,
(i == pr-throttling.state ? '*' : ' '), i,
(pr-throttling.states[i].performance ? pr-
throttling.states[i].performance / 10 : 0));
- else
+ } else {
for (i = 0; i pr-throttling.state_count; i++)
seq_printf(seq,%cT%d: %02d%%\n,
(i == pr-throttling.state ? '*' : ' '), i,
(int)pr-throttling.states_tss[i].
freqpercentage);
+ }
end:
return 0;
_
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
On Fri, 8 Jun 2007 17:15:45 +0800
"Luming Yu" <[EMAIL PROTECTED]> wrote:
> The only problem known as to the acpi throttling changes in the mm tree
> is a typo ,and the patch to fix it is available here. Please test and
> get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
> problem. Would please also try not to load acpi-cpufreq.
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
Sigh. Is this some sort of contest to see how many things we can
do wrong in a single patch?
- Include a changelog
- Include Signed-off-by:
- Don't use attachments
- If you _must_ use attachments, use text/plain, not application/octet-stream
- Format code to remain within 80 columns.
- Don't do "if(". Do "if ("
Oh well. Good to hear that the oops got fixed, thanks.
From: "Luming Yu" <[EMAIL PROTECTED]>
Cc: Len Brown <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
drivers/acpi/processor_throttling.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN
drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
drivers/acpi/processor_throttling.c
---
a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
+++ a/drivers/acpi/processor_throttling.c
@@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
pr->throttling.state_count - 1);
seq_puts(seq, "states:\n");
- if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
+ if (pr->throttling.acpi_processor_get_throttling ==
+ acpi_processor_get_throttling_fadt) {
for (i = 0; i < pr->throttling.state_count; i++)
seq_printf(seq, " %cT%d: %02d%%\n",
(i == pr->throttling.state ? '*' : ' '), i,
(pr->throttling.states[i].performance ? pr->
throttling.states[i].performance / 10 : 0));
- else
+ } else {
for (i = 0; i < pr->throttling.state_count; i++)
seq_printf(seq, " %cT%d: %02d%%\n",
(i == pr->throttling.state ? '*' : ' '), i,
(int)pr->throttling.states_tss[i].
freqpercentage);
+ }
end:
return 0;
_
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
The only problem known as to the acpi throttling changes in the mm tree is a typo ,and the patch to fix it is available here. Please test and get results back to me. BTW,the log shows that the acpi-cpufreq.ko has problem. Would please also try not to load acpi-cpufreq. http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html On 6/7/07, Andrew Morton <[EMAIL PROTECTED]> wrote: On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft <[EMAIL PROTECTED]> wrote: > Getting this on a bigger x86_64 (bl6-13): > > Unable to handle kernel NULL pointer dereference at RIP: > [] acpi_processor_throttling_seq_show+0xa7/0xd6 > PGD 2d77067 PUD 34c3067 PMD 0 > Oops: [1] SMP > CPU 3 > Modules linked in: video output button battery asus_acpi ac lp > parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core > Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 > RIP: 0010:[] [] > acpi_processor_throttling_seq_show+0xa7/0xd6 > RSP: 0018:810003c9de48 EFLAGS: 00010246 > RAX: 0020 RBX: 8100029e7800 RCX: > RDX: 002a RSI: 805993e4 RDI: 810002d714c0 > RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 > R10: R11: R12: > R13: R14: R15: 7fff64fd2b90 > FS: 2b3545aec6f0() GS:810001683a40() knlGS: > CS: 0010 DS: ES: CR0: 8005003b > CR2: CR3: 03966000 CR4: 06e0 > DR0: DR1: DR2: > DR3: DR6: 0ff0 DR7: 0400 > Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) > Stack: 00d0 810002d714c0 0001 0001 > 2000 802ab6eb 810003c9df50 810002915d00 > 810002d714f0 810002fa2000 fffb > Call Trace: > [] seq_read+0x105/0x28e > [] seq_read+0x0/0x28e > [] proc_reg_read+0x80/0x9a > [] vfs_read+0xcb/0x153 > [] sys_read+0x45/0x6e > [] system_call+0x7e/0x83 > > > Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 > RIP [] acpi_processor_throttling_seq_show+0xa7/0xd6 > RSP > CR2: > FATAL: Error inserting acpi_cpufreq > (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): > No such device Was the oops at modprobe time? If so, it seems weird that acpi_processor_throttling_seq_show() would be getting run at that stage. (The oops trace is supposed to show the oopsing process's task_struct.comm[], but it isn't shown here?) Anyway, there are extensive changes in there added by git-acpi.patch. I suppose we can try to limp along with the below, but it'll probably just oops later on. --- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show +++ a/drivers/acpi/processor_throttling.c @@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq goto end; } + seq_puts(seq, "acpi_processor_throttling_seq_show() is busted\n"); + goto end; + seq_printf(seq, "state count: %d\n" "active state:T%d\n" "state available: T%d to T%d\n", _ - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
The only problem known as to the acpi throttling changes in the mm tree is a typo ,and the patch to fix it is available here. Please test and get results back to me. BTW,the log shows that the acpi-cpufreq.ko has problem. Would please also try not to load acpi-cpufreq. http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html On 6/7/07, Andrew Morton [EMAIL PROTECTED] wrote: On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft [EMAIL PROTECTED] wrote: Getting this on a bigger x86_64 (bl6-13): Unable to handle kernel NULL pointer dereference at RIP: [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 PGD 2d77067 PUD 34c3067 PMD 0 Oops: [1] SMP CPU 3 Modules linked in: video output button battery asus_acpi ac lp parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 RIP: 0010:[8037898b] [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP: 0018:810003c9de48 EFLAGS: 00010246 RAX: 0020 RBX: 8100029e7800 RCX: RDX: 002a RSI: 805993e4 RDI: 810002d714c0 RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 R10: R11: R12: R13: R14: R15: 7fff64fd2b90 FS: 2b3545aec6f0() GS:810001683a40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 03966000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) Stack: 00d0 810002d714c0 0001 0001 2000 802ab6eb 810003c9df50 810002915d00 810002d714f0 810002fa2000 fffb Call Trace: [802ab6eb] seq_read+0x105/0x28e [802ab5e6] seq_read+0x0/0x28e [802cd085] proc_reg_read+0x80/0x9a [802925a7] vfs_read+0xcb/0x153 [80292943] sys_read+0x45/0x6e [8020bc5e] system_call+0x7e/0x83 Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 RIP [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP 810003c9de48 CR2: FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): No such device Was the oops at modprobe time? If so, it seems weird that acpi_processor_throttling_seq_show() would be getting run at that stage. (The oops trace is supposed to show the oopsing process's task_struct.comm[], but it isn't shown here?) Anyway, there are extensive changes in there added by git-acpi.patch. I suppose we can try to limp along with the below, but it'll probably just oops later on. --- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show +++ a/drivers/acpi/processor_throttling.c @@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq goto end; } + seq_puts(seq, acpi_processor_throttling_seq_show() is busted\n); + goto end; + seq_printf(seq, state count: %d\n active state:T%d\n state available: T%d to T%d\n, _ - To unsubscribe from this list: send the line unsubscribe linux-acpi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
On Fri, 8 Jun 2007 17:15:45 +0800
Luming Yu [EMAIL PROTECTED] wrote:
The only problem known as to the acpi throttling changes in the mm tree
is a typo ,and the patch to fix it is available here. Please test and
get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
problem. Would please also try not to load acpi-cpufreq.
http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
Sigh. Is this some sort of contest to see how many things we can
do wrong in a single patch?
- Include a changelog
- Include Signed-off-by:
- Don't use attachments
- If you _must_ use attachments, use text/plain, not application/octet-stream
- Format code to remain within 80 columns.
- Don't do if(. Do if (
Oh well. Good to hear that the oops got fixed, thanks.
From: Luming Yu [EMAIL PROTECTED]
Cc: Len Brown [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/acpi/processor_throttling.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN
drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
drivers/acpi/processor_throttling.c
---
a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
+++ a/drivers/acpi/processor_throttling.c
@@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
pr-throttling.state_count - 1);
seq_puts(seq, states:\n);
- if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
+ if (pr-throttling.acpi_processor_get_throttling ==
+ acpi_processor_get_throttling_fadt) {
for (i = 0; i pr-throttling.state_count; i++)
seq_printf(seq,%cT%d: %02d%%\n,
(i == pr-throttling.state ? '*' : ' '), i,
(pr-throttling.states[i].performance ? pr-
throttling.states[i].performance / 10 : 0));
- else
+ } else {
for (i = 0; i pr-throttling.state_count; i++)
seq_printf(seq,%cT%d: %02d%%\n,
(i == pr-throttling.state ? '*' : ' '), i,
(int)pr-throttling.states_tss[i].
freqpercentage);
+ }
end:
return 0;
_
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft <[EMAIL PROTECTED]> wrote: > Getting this on a bigger x86_64 (bl6-13): > > Unable to handle kernel NULL pointer dereference at RIP: > [] acpi_processor_throttling_seq_show+0xa7/0xd6 > PGD 2d77067 PUD 34c3067 PMD 0 > Oops: [1] SMP > CPU 3 > Modules linked in: video output button battery asus_acpi ac lp > parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core > Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 > RIP: 0010:[] [] > acpi_processor_throttling_seq_show+0xa7/0xd6 > RSP: 0018:810003c9de48 EFLAGS: 00010246 > RAX: 0020 RBX: 8100029e7800 RCX: > RDX: 002a RSI: 805993e4 RDI: 810002d714c0 > RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 > R10: R11: R12: > R13: R14: R15: 7fff64fd2b90 > FS: 2b3545aec6f0() GS:810001683a40() knlGS: > CS: 0010 DS: ES: CR0: 8005003b > CR2: CR3: 03966000 CR4: 06e0 > DR0: DR1: DR2: > DR3: DR6: 0ff0 DR7: 0400 > Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) > Stack: 00d0 810002d714c0 0001 0001 > 2000 802ab6eb 810003c9df50 810002915d00 > 810002d714f0 810002fa2000 fffb > Call Trace: > [] seq_read+0x105/0x28e > [] seq_read+0x0/0x28e > [] proc_reg_read+0x80/0x9a > [] vfs_read+0xcb/0x153 > [] sys_read+0x45/0x6e > [] system_call+0x7e/0x83 > > > Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 > RIP [] acpi_processor_throttling_seq_show+0xa7/0xd6 > RSP > CR2: > FATAL: Error inserting acpi_cpufreq > (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): > No such device Was the oops at modprobe time? If so, it seems weird that acpi_processor_throttling_seq_show() would be getting run at that stage. (The oops trace is supposed to show the oopsing process's task_struct.comm[], but it isn't shown here?) Anyway, there are extensive changes in there added by git-acpi.patch. I suppose we can try to limp along with the below, but it'll probably just oops later on. --- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show +++ a/drivers/acpi/processor_throttling.c @@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq goto end; } + seq_puts(seq, "acpi_processor_throttling_seq_show() is busted\n"); + goto end; + seq_printf(seq, "state count: %d\n" "active state:T%d\n" "state available: T%d to T%d\n", _ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
Getting this on a bigger x86_64 (bl6-13): Unable to handle kernel NULL pointer dereference at RIP: [] acpi_processor_throttling_seq_show+0xa7/0xd6 PGD 2d77067 PUD 34c3067 PMD 0 Oops: [1] SMP CPU 3 Modules linked in: video output button battery asus_acpi ac lp parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 RIP: 0010:[] [] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP: 0018:810003c9de48 EFLAGS: 00010246 RAX: 0020 RBX: 8100029e7800 RCX: RDX: 002a RSI: 805993e4 RDI: 810002d714c0 RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 R10: R11: R12: R13: R14: R15: 7fff64fd2b90 FS: 2b3545aec6f0() GS:810001683a40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 03966000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) Stack: 00d0 810002d714c0 0001 0001 2000 802ab6eb 810003c9df50 810002915d00 810002d714f0 810002fa2000 fffb Call Trace: [] seq_read+0x105/0x28e [] seq_read+0x0/0x28e [] proc_reg_read+0x80/0x9a [] vfs_read+0xcb/0x153 [] sys_read+0x45/0x6e [] system_call+0x7e/0x83 Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 RIP [] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP CR2: FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): No such device - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
Getting this on a bigger x86_64 (bl6-13): Unable to handle kernel NULL pointer dereference at RIP: [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 PGD 2d77067 PUD 34c3067 PMD 0 Oops: [1] SMP CPU 3 Modules linked in: video output button battery asus_acpi ac lp parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 RIP: 0010:[8037898b] [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP: 0018:810003c9de48 EFLAGS: 00010246 RAX: 0020 RBX: 8100029e7800 RCX: RDX: 002a RSI: 805993e4 RDI: 810002d714c0 RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 R10: R11: R12: R13: R14: R15: 7fff64fd2b90 FS: 2b3545aec6f0() GS:810001683a40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 03966000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) Stack: 00d0 810002d714c0 0001 0001 2000 802ab6eb 810003c9df50 810002915d00 810002d714f0 810002fa2000 fffb Call Trace: [802ab6eb] seq_read+0x105/0x28e [802ab5e6] seq_read+0x0/0x28e [802cd085] proc_reg_read+0x80/0x9a [802925a7] vfs_read+0xcb/0x153 [80292943] sys_read+0x45/0x6e [8020bc5e] system_call+0x7e/0x83 Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 RIP [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP 810003c9de48 CR2: FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): No such device - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft [EMAIL PROTECTED] wrote: Getting this on a bigger x86_64 (bl6-13): Unable to handle kernel NULL pointer dereference at RIP: [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 PGD 2d77067 PUD 34c3067 PMD 0 Oops: [1] SMP CPU 3 Modules linked in: video output button battery asus_acpi ac lp parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1 RIP: 0010:[8037898b] [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP: 0018:810003c9de48 EFLAGS: 00010246 RAX: 0020 RBX: 8100029e7800 RCX: RDX: 002a RSI: 805993e4 RDI: 810002d714c0 RBP: 810002d714c0 R08: 810003f82051 R09: 810002d714c0 R10: R11: R12: R13: R14: R15: 7fff64fd2b90 FS: 2b3545aec6f0() GS:810001683a40() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 03966000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process head (pid: 1634, threadinfo 810003c9c000, task 810001c8c810) Stack: 00d0 810002d714c0 0001 0001 2000 802ab6eb 810003c9df50 810002915d00 810002d714f0 810002fa2000 fffb Call Trace: [802ab6eb] seq_read+0x105/0x28e [802ab5e6] seq_read+0x0/0x28e [802cd085] proc_reg_read+0x80/0x9a [802925a7] vfs_read+0xcb/0x153 [80292943] sys_read+0x45/0x6e [8020bc5e] system_call+0x7e/0x83 Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28 RIP [8037898b] acpi_processor_throttling_seq_show+0xa7/0xd6 RSP 810003c9de48 CR2: FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko): No such device Was the oops at modprobe time? If so, it seems weird that acpi_processor_throttling_seq_show() would be getting run at that stage. (The oops trace is supposed to show the oopsing process's task_struct.comm[], but it isn't shown here?) Anyway, there are extensive changes in there added by git-acpi.patch. I suppose we can try to limp along with the below, but it'll probably just oops later on. --- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show +++ a/drivers/acpi/processor_throttling.c @@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq goto end; } + seq_puts(seq, acpi_processor_throttling_seq_show() is busted\n); + goto end; + seq_printf(seq, state count: %d\n active state:T%d\n state available: T%d to T%d\n, _ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
