linux-kernel - Re: [Bug #12337] ~100 extra wakeups reported by powertop

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200902242338.14105.nickpiggin@yahoo.com.au>
Date:	Tue, 24 Feb 2009 23:38:13 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	luis6674@...oo.com, Eric Anholt <eric@...olt.net>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #12337] ~100 extra wakeups reported by powertop

On Tuesday 24 February 2009 23:25:11 Alberto Gonzalez wrote:
> --- On Tue, 2/24/09, Nick Piggin <nickpiggin@...oo.com.au> wrote:
> > > > Bug-Entry	:
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=12337
> > > > Subject		: ~100 extra wakeups reported by
> >
> > powertop
> >
> > > > Submitter	: Alberto Gonzalez
> >
> > <luis6674@...oo.com>
> >
> > > > Date		: 2008-12-31 12:25 (55 days old)
> > >
> > > Still present, yes.
> >
> > Any chance you could bisect it?
>
> Well, if you look at the report you'd notice that:

I read at the report, but it wasn't obvious that you wouldn't be
able to bisect it.


> - I'm using a released, stable, distro (Arch Linux, basically vanilla)
> kernel. I hardly know how to compile one, let alone bisect it. - I first
> had the problem on my 5+ year old Pentium 4 with equally old Intel graphics
> (845G chipset). I thought it would be hardware specific. But now I got a
> new Core 2 Duo with new Intel graphics (G45 chipset), moved to 64bit, and
> still have the exact same problem and exact same workaround. So I really
> don't believe anymore it's something hardware specific and should be quite
> general to anyone using Intel graphics. I hoped someone with much better
> knowledge could reproduce it and investigate it better.
>
> On the report, Eric Anholt mentioned a likely cause and said that Jesse
> Barnes had looked into a similar issue before. I cc'd him (jbarnes) on last
> week reminder, but got no reply.
>
> I really wish I could do more, but learning to compile a custom kernel for
> my hardware and do a git bisect is something I just can't afford now. If
> relevant people try to reproduce it but can't, and say only possible
> solution would be for me to bisect it I guess I could try to give it a go
> when I get some spare time.

Fair enough. Reporting a problem is always very appreciated.

Pinging Eric and Jesse ;)

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