linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Joshua Kwan <joshk@triplehelix.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] 2.4.21-ck3 in schedule
Date: Sat, 26 Jul 2003 13:06:45 +1000	[thread overview]
Message-ID: <200307261306.45743.kernel@kolivas.org> (raw)
In-Reply-To: <20030725051847.GA1778@triplehelix.org>

On Fri, 25 Jul 2003 15:18, Joshua Kwan wrote:
> 2.4.21-ck1 was fine under nearly the same circumstances. I rebuilt with
> a newer -ck when I was configuring my new ADSL bridge to work with Linux
> pppoe, but I doubt that's related.
>
> Anyway, it drove my wireless card driver nuts too, probably due to some
> busted interrupts. It kept printing a SW TICK STUCK? message. I'll
> revert to vanilla for now. :(

I suspect it's the variable Hz that is exported as 100 but runs as 1000 in 
2.4-ck. I suggest you build without the variable Hz and tuning so it runs at 
100Hz and try again.

Con


  reply	other threads:[~2003-07-26  2:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25  5:18 Joshua Kwan
2003-07-26  3:06 ` Con Kolivas [this message]
2003-07-26  4:07   ` Joshua Kwan

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=200307261306.45743.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [OOPS] 2.4.21-ck3 in schedule' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).