From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.4-rc2-mm1 lockup with NVIDIA driver
Date: Wed, 10 Mar 2004 08:56:37 +0000 [thread overview]
Message-ID: <404ED845.7070804@blueyonder.co.uk> (raw)
SuSE 9.0 Pro on Athlon XP2200+, 2.6.4-rc2-mm1 seemed to cause some
filesystem corruption with the nvidia driver, using the distributed nv
driver is OK.
Booted to runlevel 3, installed the latest nvidia 5336 package, init 5
and video switched to a black screen and there is a hard lockup. No
problems up to 2.6.3-mm kernels. Rebooting to 2.6.3-mm4 which had been
OK now gave a hard lockup.
Did a reiserfsck --rebuild-tree, a number of files fixed, but the
problem did not go away. Also when starting vi or saving a file edited
with vi, I get this garbage, the file is however fine.
E575: viminfo: Illegal starting char in line: ADD 3925868551 "def"
"/apps/gnome-settings/ggv"
"IOR:01eeffbf1700000049444c3a436f6e6669674c697374656e65723a312e300000030000000054424f580000000101026205000000554e495800000000090000006261727261626173000000002d0000002f746d702f6f726269742d6c616e63656c6f742f6c696e632d6664382d302d3666333639616464376366653100652f7300000000caaedfba58000000010102002d0000002f746d702f6f726269742d6c616e63656c6f742f6c696e632d6664382d302d36663336396164643763666531000000001c00000000000000e8aa2c20e00768a8dc2928282828282804000000ff9f55c101
E575: viminfo: Illegal starting char in line: ADD 3942645768 "def"
"/apps/ggv/gtkgs"
"IOR:01eeffbf1700000049444c3a436f6e6669674c697374656e65723a312e300000030000000054424f580000000101020005000000554e495800646573090000006261727261626173007465722d0000002f746d702f6f726269742d6c616e63656c6f742f6c696e632d6664382d302d3666333639616464376366653100652f7300000000caaedfba58000000010102002d0000002f746d702f6f726269742d6c616e63656c6f742f6c696e632d6664382d302d36663336396164643763666531000000001c00000000000000e8aa2c20e00768a8dc2928282828282804000000ff9f55c101000000480
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
reply other threads:[~2004-03-10 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=404ED845.7070804@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.