public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Kumlien <iank@bredband.net>
To: David Miller <davem@davemloft.net>
Cc: michal.k.k.piotrowski@gmail.com, Linux-kernel@vger.kernel.org
Subject: Re: [BUG] Something goes wrong with timer statistics.
Date: Wed, 30 May 2007 00:51:52 +0200	[thread overview]
Message-ID: <1180479122.19814.8.camel@pi.pomac.com> (raw)
In-Reply-To: <20070529.154406.104042418.davem@davemloft.net>

On tis, 2007-05-29 at 15:44 -0700, David Miller wrote:
> From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
> Date: Wed, 30 May 2007 00:41:46 +0200
> 
> > On 30/05/07, David Miller <davem@davemloft.net> wrote:
> > > From: Ian Kumlien <iank@bredband.net>
> > > Date: Tue, 29 May 2007 23:38:48 +0200
> > >
> > > > 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
> > > >
> > > > If i don't run powertop, it is rock solid... Compiling for hours,
> > > > running memtest for hours etc etc...
> > >
> > > I see this same exact problem on sparc64.
> > 
> > Have you tried this patch?
> > http://lkml.org/lkml/2007/5/29/392
> 
> Of course, I worked with Thomas on the fix :-)

I dunno if this applies to me, i run a 32 bit userspace...

-- 
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net

  reply	other threads:[~2007-05-29 22:52 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
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 [this message]
2007-05-29 23:03         ` David Miller
2007-05-30  0:04           ` 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
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-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=1180479122.19814.8.camel@pi.pomac.com \
    --to=iank@bredband.net \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox