All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Berck E. Nash" <flyboy@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
Date: Mon, 30 Apr 2007 06:07:49 -0600	[thread overview]
Message-ID: <4635DC15.6090705@gmail.com> (raw)
In-Reply-To: <46354620.4060902@gmail.com>

Tejun Heo wrote:

> Hmmm... Once properly initialized, ahci is highly unlikely to cause
> runaway IRQs which results in nobody cared.  It has proper IRQ mask and
> pending bits allowing the driver to reliably detect when and why the
> controller is raising interrupt and disable it if necessary.  Can you
> try without the NVIDIA module?

I'm beginning to think it was a one-time hardware error of some sort.
I've been running 2.6.21-rc7-mm2 for awhile now and the problem hasn't
reoccurred, so I think you can consider the matter settled...

Thanks,
Berck

  reply	other threads:[~2007-04-30 12:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 18:28 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock() Berck E. Nash
2007-04-25  8:16 ` Andrew Morton
2007-04-25  8:42   ` Tejun Heo
2007-04-25  8:54     ` Tejun Heo
2007-04-25  9:30       ` Tejun Heo
2007-04-25 12:28         ` Berck E. Nash
2007-04-25 23:51         ` Berck E. Nash
2007-04-30  1:28           ` Tejun Heo
2007-04-30 12:07             ` Berck E. Nash [this message]
2007-05-01  9:02               ` Tejun Heo
2007-04-25 10:21       ` Alan Cox
2007-04-25 10:25       ` Alan Cox
2007-04-25 10:25         ` Tejun Heo
2007-04-25 10:35           ` Alan Cox
2007-04-25  8:55     ` Andrew Morton
2007-04-25  9:15       ` Tejun Heo

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=4635DC15.6090705@gmail.com \
    --to=flyboy@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.