All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_4KSTACKS in mm2?
Date: Thu, 08 Apr 2004 00:56:10 +0100	[thread overview]
Message-ID: <4074951A.8010900@blueyonder.co.uk> (raw)

Ralf Hindlebrand wrote:
* Zwane Mwaikambo <zwane@xxxxxxxxxxxxx>:

 > >/ > That's what I did (and it works) -- but it's not really 
intuitive or/
 > >/ > even configurable (in the way of menuconfig or something)./
 >/  >/
 > >/ Andrew Morton turned it on unconditionally on purpose for wider 
testing./

 > Yep. It doesn't work with Nvidia's nvidia kernel drivers. But what's
 > new :)

What's new is that I forgot to turn it off, I'd been running 2.6.5-cko1, 
built 2.6.5-mm1, booted up and installed nvidia kernel for it. I ended 
up with a trashed HD which needed reformatiing and a fresh install. I 
don't know what symptoms I should have seen, perhaps nvidia failing to 
work. I suspect it was a combination of 4K_STACKS and some hardware bug 
for which I am going to change the motherboard, memory and Athlon CPU as 
I've had odd hangs during boot. A few boots hung, finally I disabled 
level 2 cache and it came up, so I think I will leave the next bootup 
till the new stuff is installed. I previously had a hard drive that 
would not boot fully after starting X with nvidia, though it's mountable 
as hdc1 and I can get at all the stuff I need.
Regards
Sid.


             reply	other threads:[~2004-04-07 23:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 23:56 Sid Boyce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-07 13:55 CONFIG_4KSTACKS in mm2? Ralf Hildebrandt
2004-04-07 14:01 ` Zwane Mwaikambo
2004-04-07 14:03   ` Ralf Hildebrandt
2004-04-07 14:26     ` Martin Zwickel
2004-04-07 14:38     ` Zwane Mwaikambo
2004-04-07 14:43       ` Ralf Hildebrandt

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=4074951A.8010900@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --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.