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: NVIDIA and 2.6.4?
Date: Thu, 11 Mar 2004 15:15:46 +0000	[thread overview]
Message-ID: <405082A2.5040304@blueyonder.co.uk> (raw)

I tried 5336 with 2.6.4-rc2-mm1 and it locks the box up completely after 
switching to kdm. It worked with 2.6.3-mm4 previously, now even that 
kernel gets a lock up. I've done a reiserfsck --rebuild-tree which 
repaired some files and left 10 files in /lost+found and I can't 
determine what they are.
I am currently using 2.6.4-rc2-mm1 with the standard SuSE 9.0  Driver "nv".
I also went back to the minion.de release and still got a lockup, I 
guess it's down to some of those files in lost+found that are missing.
Regards
Sid.

-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.


             reply	other threads:[~2004-03-11 15:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 15:15 Sid Boyce [this message]
2004-03-11 19:26 ` NVIDIA and 2.6.4? Max Valdez
2004-03-12  1:31   ` Sid Boyce
2004-03-12 18:24     ` Adam Jones
2004-03-13  5:15       ` Valdis.Kletnieks
2004-03-15  3:36         ` Steve Youngs
2004-03-16 20:49           ` Dominik Karall
2004-03-16 20:50             ` Brian Gerst
2004-03-16 21:19             ` Valdis.Kletnieks
2004-03-16 21:55               ` Dominik Karall
  -- strict thread matches above, loose matches on Subject: below --
2004-03-15  1:24 Sid Boyce
2004-03-14  2:23 Sid Boyce
2004-03-14  2:28 ` Sid Boyce
     [not found] <1yxEK-7cw-5@gated-at.bofh.it>
2004-03-11 13:20 ` Dennis Bliefernicht
2004-03-11 15:05   ` Robert L. Harris
2004-03-11 12:31 Robert L. Harris
2004-03-11 13:07 ` Nerijus Baliunas
2004-03-11 13:23   ` Martin Zwickel
2004-03-13 14:34   ` venom
2004-03-11 14:52 ` Alistair John Strachan

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=405082A2.5040304@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.