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: <b93822910703200123g5b3ac0e4n1ba1122a7e90a838@mail.gmail.com>
Date:	Tue, 20 Mar 2007 09:23:48 +0100
From:	"Stefan Prechtel" <stefan.prechtel@...glemail.com>
To:	tglx@...utronix.de
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})

2007/3/20, Thomas Gleixner <tglx@...utronix.de>:
> On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
> > 2007/3/19, Thomas Gleixner <tglx@...utronix.de>:
> > > 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  local-APIC-edge-fasteio   timer
> > > > ...
> > > > LOC:      30292      30291
> > >
> > > Is this with AC plugged in ? If yes, please provide the same numbers for
> > > battery mode.
> >
> > Yes. And here is the output for battery mode (2.6.20):
> >            CPU0       CPU1
> >   0:     292153          0  local-APIC-edge-fasteio   timer
> > LOC:     292114     292113
> >
> >            CPU0       CPU1
> >   0:     293263          0  local-APIC-edge-fasteio   timer
> > LOC:     293224     293223
>
> Hmm. Can you please apply the following patch on top of 2.6.20 and
> check, if the WARN_ON_ONCE triggers when you boot w/o AC plugged ?
>
> Thanks,
>
>         tglx

Good morning!

The WARN_ON / WARN_ON_ONCE didn't trigger on boot.

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