linux-kernel - Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})

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: <1174334646.13341.577.camel@localhost.localdomain>
Date:	Mon, 19 Mar 2007 21:04:06 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stefan Prechtel <stefan.prechtel@...glemail.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Len Brown <lenb@...nel.org>, Andi Kleen <ak@...e.de>,
	john stultz <johnstul@...ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})

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 /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   29793520    IO-APIC-edge  timer
...
LOC:  119180305  119180039

And please do a sleep 10; between two reads, so I can see the deltas.

> and this on 2.6.21-rc*:
>            CPU0       CPU1
>   0:        255          0  local-APIC-edge-fasteoi   timer
> ....
> 
> on 2.6.21-rc* the number "255" doesn't change.

Yes. I know. We rely on the local APIC, if the ACPI code does us not
tell to use the PIT broadcast, sigh.

> But if it is ACPI relevant, shouldn't it boot with acpi=off?
> I've tried with acpi=off and noapic but only with nolapic it started.
> 
> And the content of /proc/acpi/processor/C000/power shows only one
> c-state; shouldn't it show more C-states? (please correct me if I'm
> wrong)
> 
>  # cat /proc/acpi/processor/C000/power
> active state:            C1
> max_cstate:              C8
> bus master activity:     00000000
> maximum allowed latency: 2000 usec
> states:
>    *C1:                  type[C1] promotion[--] demotion[--]
> latency[000] usage[00000000] duration[00000000000000000000]

Yup. It should.

Thanks,

	tglx


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