On Wed, 2007-03-21 at 14:04 +0100, Stefan Prechtel wrote:
> I uploaded the output of dmesg (kernel 2.6.21-rc4-git5) (battery / ac)
> and dmidecode
> I can boot on battery with nolapic_timer and the second core is online, too.
> /proc/acpi/processor/C000/ shows the same as before but
>
2007/3/21, Andi Kleen <[EMAIL PROTECTED]>:
On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
> On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > > The BIOS/ACPI is broken and does only expose C1, which should not
> > > switch off LAPIC. The BIOS is switching into deeper C-States
On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
> On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > > The BIOS/ACPI is broken and does only expose C1, which should not
> > > switch off LAPIC. The BIOS is switching into deeper C-States behind the
> > > kernels back somehow.
> >
> >
On Wed, 2007-03-21 at 13:15 +0100, Thomas Gleixner wrote:
> + return;
> + }}
> +
Ooops, sorry. Did not quilt refresh before sending it out. Correct
version below.
tglx
diff --git a/arch/i386/kernel/apic.c b/arch/i386/kernel/apic.c
index 5cff797..83cf98d 100644
---
Stefan, Grzegorz
On Wed, 2007-03-21 at 12:14 +0100, Thomas Gleixner wrote:
> On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > > The BIOS/ACPI is broken and does only expose C1, which should not switch
> > > off LAPIC. The BIOS is switching into deeper C-States behind the kernels
> > >
On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
> > The BIOS/ACPI is broken and does only expose C1, which should not switch
> > off LAPIC. The BIOS is switching into deeper C-States behind the kernels
> > back somehow.
>
> Hmm, perhaps we can check AMD && (cstate >= 2 || has a battery) ?
>
> The BIOS/ACPI is broken and does only expose C1, which should not switch
> off LAPIC. The BIOS is switching into deeper C-States behind the kernels
> back somehow.
Hmm, perhaps we can check AMD && (cstate >= 2 || has a battery) ?
Should be doable by looking up the battery object in ACPI
On Wed, 2007-03-21 at 10:46 +0100, Andi Kleen wrote:
> On Wednesday 21 March 2007 10:24, Thomas Gleixner wrote:
> > On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
> > > I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
> > > nothing special in dmesg. Just in
On Wednesday 21 March 2007 10:24, Thomas Gleixner wrote:
> On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
> > I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
> > nothing special in dmesg. Just in case I'm posting my
> > dmesg_2.6.20_WARN_ON_ONCE_on_battery
On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
> I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
> nothing special in dmesg. Just in case I'm posting my
> dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
> http://bugzilla.kernel.org/show_bug.cgi?id=8235 .
>
>
On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
nothing special in dmesg. Just in case I'm posting my
dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
http://bugzilla.kernel.org/show_bug.cgi?id=8235 .
Below I
On Wednesday 21 March 2007 10:24, Thomas Gleixner wrote:
On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
nothing special in dmesg. Just in case I'm posting my
dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
On Wed, 2007-03-21 at 10:46 +0100, Andi Kleen wrote:
On Wednesday 21 March 2007 10:24, Thomas Gleixner wrote:
On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
nothing special in dmesg. Just in case I'm
The BIOS/ACPI is broken and does only expose C1, which should not switch
off LAPIC. The BIOS is switching into deeper C-States behind the kernels
back somehow.
Hmm, perhaps we can check AMD (cstate = 2 || has a battery) ?
Should be doable by looking up the battery object in ACPI
-Andi
-
To
On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
The BIOS/ACPI is broken and does only expose C1, which should not switch
off LAPIC. The BIOS is switching into deeper C-States behind the kernels
back somehow.
Hmm, perhaps we can check AMD (cstate = 2 || has a battery) ?
Should be
Stefan, Grzegorz
On Wed, 2007-03-21 at 12:14 +0100, Thomas Gleixner wrote:
On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
The BIOS/ACPI is broken and does only expose C1, which should not switch
off LAPIC. The BIOS is switching into deeper C-States behind the kernels
back somehow.
On Wed, 2007-03-21 at 13:15 +0100, Thomas Gleixner wrote:
+ return;
+ }}
+
Ooops, sorry. Did not quilt refresh before sending it out. Correct
version below.
tglx
diff --git a/arch/i386/kernel/apic.c b/arch/i386/kernel/apic.c
index 5cff797..83cf98d 100644
---
On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
The BIOS/ACPI is broken and does only expose C1, which should not
switch off LAPIC. The BIOS is switching into deeper C-States behind the
kernels back somehow.
Hmm, perhaps
2007/3/21, Andi Kleen [EMAIL PROTECTED]:
On Wednesday 21 March 2007 12:14, Thomas Gleixner wrote:
On Wed, 2007-03-21 at 11:37 +0100, Andi Kleen wrote:
The BIOS/ACPI is broken and does only expose C1, which should not
switch off LAPIC. The BIOS is switching into deeper C-States behind the
On Wed, 2007-03-21 at 14:04 +0100, Stefan Prechtel wrote:
I uploaded the output of dmesg (kernel 2.6.21-rc4-git5) (battery / ac)
and dmidecode
I can boot on battery with nolapic_timer and the second core is online, too.
/proc/acpi/processor/C000/ shows the same as before but
/proc/interrupts
I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
nothing special in dmesg. Just in case I'm posting my
dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
http://bugzilla.kernel.org/show_bug.cgi?id=8235 .
Below I post output of my /proc interrupts (10 sec. delay between reads).
2007/3/20, Thomas Gleixner <[EMAIL PROTECTED]>:
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
> 2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
> > On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
> > >CPU0 CPU1
> > > 0: 28289 0
2007/3/20, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
CPU0 CPU1
0: 28289 0 local-APIC-edge-fasteio
I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
nothing special in dmesg. Just in case I'm posting my
dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
http://bugzilla.kernel.org/show_bug.cgi?id=8235 .
Below I post output of my /proc interrupts (10 sec. delay between reads).
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
> 2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
> > On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
> > >CPU0 CPU1
> > > 0: 28289 0 local-APIC-edge-fasteio timer
> > > ...
> > > LOC:
2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
>CPU0 CPU1
> 0: 28289 0 local-APIC-edge-fasteio timer
> ...
> LOC: 28237 28236
>
> after a read: (I hope that is this what you want :-)
>
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
>CPU0 CPU1
> 0: 28289 0 local-APIC-edge-fasteio timer
> ...
> LOC: 28237 28236
>
> after a read: (I hope that is this what you want :-)
>CPU0 CPU1
> 0: 30344 0
2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
> Here is the output of /proc/interrupts on 2.6.20:
>CPU0 CPU1
> 0: 7089 0 local-APIC-edge-fasteio timer
>
Can you provide the numbers for LOC too ?
0: 29801420 29793520IO-APIC-edge timer
...
On Mon, 2007-03-19 at 20:49 +0100, Stefan Prechtel wrote:
> > Can you please boot with 2.6.20 or earlier and check the output
> > of /proc/interrupts ?
> >
> > IRQ#0 and the LOC (local APIC timer) Interrupts should increment in the
> > same frequency.
> >
> > tglx
>
> Here is the output
2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
We have a broadcast mechanism for this, which gets activated from ACPI,
but the broadcast mechanism is not activated:
[3.798000] Clock Event Device: pit
[3.798000] tick_broadcast_mask:
Can you please boot with 2.6.20 or
Stefan,
On Mon, 2007-03-19 at 19:53 +0100, Stefan Prechtel wrote:
> You can find the files here:
> http://bugzilla.kernel.org/show_bug.cgi?id=8235
thanks for providing the data. Your ACPI tables don't provide
information about the power states (C-States), but your BIOS seems to
switch the CPUs
(Bugzilla)
Does booting w/ clocksource=acpi_pm avoid the problem?
No, it doesn't.
I hope it's ok that I added your email to CC.
2007/3/19, Stefan Prechtel <[EMAIL PROTECTED]>:
Hi!
If the ac-cable is plugged in, I can start my Notebook (HP nx6325)
without any problems.
On battery the kernel
You can find the files here:
http://bugzilla.kernel.org/show_bug.cgi?id=8235
Regards,
Stefan Prechtel
2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
On Mon, 2007-03-19 at 18:36 +0100, Thomas Gleixner wrote:
Oh, a bootlog with ac plugged in would be great too.
Also can you please enable
On Mon, 2007-03-19 at 18:36 +0100, Thomas Gleixner wrote:
> On Mon, 2007-03-19 at 18:10 +0100, Stefan Prechtel wrote:
> > So I tried to boot with nolapic on battery and with this option the
> > kernel (and system) starts as it should.
> > If you need more information, I will send it to you.
>
>
On Mon, 2007-03-19 at 18:10 +0100, Stefan Prechtel wrote:
> So I tried to boot with nolapic on battery and with this option the
> kernel (and system) starts as it should.
> If you need more information, I will send it to you.
Can you please provide your .config and a bootlog from a boot with
On Mon, 2007-03-19 at 18:10 +0100, Stefan Prechtel wrote:
So I tried to boot with nolapic on battery and with this option the
kernel (and system) starts as it should.
If you need more information, I will send it to you.
Can you please provide your .config and a bootlog from a boot with
nolapic
On Mon, 2007-03-19 at 18:36 +0100, Thomas Gleixner wrote:
On Mon, 2007-03-19 at 18:10 +0100, Stefan Prechtel wrote:
So I tried to boot with nolapic on battery and with this option the
kernel (and system) starts as it should.
If you need more information, I will send it to you.
Can you
You can find the files here:
http://bugzilla.kernel.org/show_bug.cgi?id=8235
Regards,
Stefan Prechtel
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 18:36 +0100, Thomas Gleixner wrote:
Oh, a bootlog with ac plugged in would be great too.
Also can you please enable
(Bugzilla)
Does booting w/ clocksource=acpi_pm avoid the problem?
No, it doesn't.
I hope it's ok that I added your email to CC.
2007/3/19, Stefan Prechtel [EMAIL PROTECTED]:
Hi!
If the ac-cable is plugged in, I can start my Notebook (HP nx6325)
without any problems.
On battery the kernel
Stefan,
On Mon, 2007-03-19 at 19:53 +0100, Stefan Prechtel wrote:
You can find the files here:
http://bugzilla.kernel.org/show_bug.cgi?id=8235
thanks for providing the data. Your ACPI tables don't provide
information about the power states (C-States), but your BIOS seems to
switch the CPUs
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
We have a broadcast mechanism for this, which gets activated from ACPI,
but the broadcast mechanism is not activated:
[3.798000] Clock Event Device: pit
[3.798000] tick_broadcast_mask:
Can you please boot with 2.6.20 or
On Mon, 2007-03-19 at 20:49 +0100, Stefan Prechtel wrote:
Can you please boot with 2.6.20 or earlier and check the output
of /proc/interrupts ?
IRQ#0 and the LOC (local APIC timer) Interrupts should increment in the
same frequency.
tglx
Here is the output of
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
Here is the output of /proc/interrupts on 2.6.20:
CPU0 CPU1
0: 7089 0 local-APIC-edge-fasteio timer
Can you provide the numbers for LOC too ?
0: 29801420 29793520IO-APIC-edge timer
...
LOC:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
CPU0 CPU1
0: 28289 0 local-APIC-edge-fasteio timer
...
LOC: 28237 28236
after a read: (I hope that is this what you want :-)
CPU0 CPU1
0: 30344 0
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
CPU0 CPU1
0: 28289 0 local-APIC-edge-fasteio timer
...
LOC: 28237 28236
after a read: (I hope that is this what you want :-)
CPU0
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
CPU0 CPU1
0: 28289 0 local-APIC-edge-fasteio timer
...
LOC: 28237 28236
46 matches
Mail list logo
