From: Ian Kumlien <iank@bredband.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [BUG] Something goes wrong with timer statistics.
Date: Wed, 30 May 2007 00:50:55 +0200 [thread overview]
Message-ID: <1180479065.19814.6.camel@pi.pomac.com> (raw)
In-Reply-To: <1180478288.20546.39.camel@chaos>
On ons, 2007-05-30 at 00:38 +0200, Thomas Gleixner wrote:
> On Wed, 2007-05-30 at 00:24 +0200, Michal Piotrowski wrote:
> > Hi Ian,
> >
> > (Thomas "The Wizard of Time" added to CC :))
>
> Added more wizards :)
>
> > On 29/05/07, Ian Kumlien <iank@bredband.net> wrote:
> > > Hi,
> > >
> > > As the daystar sets, i try to play some with my new would be
> > > firewall/server, but since this will be running for quite some time i
> > > have been experimenting with powertop to find out what i can do to limit
> > > it's power usage.
> > >
> > > But, if i run powertop for too long or a few times to many... this
> > > happens:
> > > http://pomac.netswarm.net/pics/kernel_panic.jpg
>
> This was reported before. It's incredibly hard to reproduce.
>
> Ian, is this happening reproducible ?
Seems like it, i haven't actually TRIED to crash yet...
But i can try if i don't have to crash in the future =)
(The machine is just a motherboard lying on the floor with some disks
attached, so i have to bring out my pocket knife and short circuit the
right pins =))
> > > If i don't run powertop, it is rock solid... Compiling for hours,
> > > running memtest for hours etc etc...
> >
> > (Where is my magic ball?)
> >
> > Let me guess - Pentium 4 with HT?
>
> I might be wrong, but it's a newer core duo thingy.
>
> tglx
>
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
next prev parent reply other threads:[~2007-05-29 22:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 21:38 [BUG] Something goes wrong with timer statistics Ian Kumlien
[not found] ` <6bffcb0e0705291524y2752d646p94b0bf6ca87af68f@mail.gmail.com>
2007-05-29 22:35 ` Ian Kumlien
2007-05-29 22:38 ` Thomas Gleixner
2007-05-29 22:50 ` Ian Kumlien [this message]
2007-05-30 6:52 ` Björn Steinbrink
2007-05-30 7:10 ` Björn Steinbrink
2007-05-30 11:38 ` Björn Steinbrink
2007-05-30 12:44 ` Eric Dumazet
2007-05-30 13:14 ` Björn Steinbrink
[not found] ` <20070531102047.GG19272@pomac.netswarm.net>
2007-05-31 14:25 ` Björn Steinbrink
2007-05-31 15:10 ` Eric Dumazet
2007-05-31 15:27 ` Björn Steinbrink
2007-05-31 22:59 ` Ian Kumlien
2007-05-31 23:09 ` Björn Steinbrink
2007-06-01 6:21 ` Ingo Molnar
2007-05-29 22:37 ` David Miller
2007-05-29 22:42 ` Thomas Gleixner
2007-05-29 22:44 ` David Miller
2007-05-29 22:53 ` Thomas Gleixner
[not found] ` <6bffcb0e0705291541q7e6d6faen5cd6345074c4c92a@mail.gmail.com>
2007-05-29 22:44 ` David Miller
2007-05-29 22:51 ` Ian Kumlien
2007-05-29 23:03 ` David Miller
2007-05-30 0:04 ` Ian Kumlien
2007-05-30 0:13 ` Stephane Casset
2007-05-31 23:53 ` Björn Steinbrink
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180479065.19814.6.camel@pi.pomac.com \
--to=iank@bredband.net \
--cc=Linux-kernel@vger.kernel.org \
--cc=arjan@infradead.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.