From: "Steven A. DuChene" <linux-clusters@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-pre2 locks up hard with rivafb
Date: Sat, 30 Mar 2002 20:43:34 -0500 [thread overview]
Message-ID: <20020330204334.N13832@lapsony.mydomain.here> (raw)
I have a dual Pentium Pro 200MHz system with a STB Velocity 128 PCI
video card. This card has a Riva 128 chip on it and shows up in
/proc/pci as
Bus 0, device 15, function 0:
VGA compatible controller: NVidia / SGS Thomson (Joint Venture) Riva128 (rev 16).
IRQ 19.
Master Capable. Latency=64. Min Gnt=3.Max Lat=1.
Non-prefetchable 32 bit memory at 0xef000000 [0xefffffff].
Prefetchable 32 bit memory at 0xee000000 [0xeeffffff].
When I boot up 2.4.19-pre1 with the rivafb driver compiled into the kernel
I get the following:
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd
rivafb: RIVA MTRR set to ON
fbcon_setup: No support for fontwidth 8
fbcon_setup: type 0 (aux 0, depth 15) not supported
Console: switching to colour frame buffer device 160x64
rivafb: PCI nVidia NV3 framebuffer ver 0.9.2a (RIVA-128, 4MB @ 0xEE000000)
This is with a append line in lilo.conf as
video=riva:1280x1024-15@74
If I boot into 2.4.19-pre2 when the rivag=fb is also compiled into the kernel
the systems locks up hard after:
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd
rivafb: RIVA MTRR set to ON
I found this much by altering the append line to send the comsole to the
serial port.
Even if I remove the "video=blah" line from lilo.conf the system still locks
hard if the rivafb driver is present. System boots fine if the frame buffer
stuff is disabled.
I traced this down to the change between 2.4.19-pre1 and 2.4.19-pre2 because
the same hard lock up happened with 2.4.19-pre4-ac3 earlier today.
Thing is there is no change to the rivafb code in 2.4.19-pre2
Any ideas about wehat could cause this or what I should try?
--
Steven A. DuChene linux-clusters@mindspring.com
sduchene@mindspring.com
http://www.mindspring.com/~sduchene/
reply other threads:[~2002-03-31 1:44 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=20020330204334.N13832@lapsony.mydomain.here \
--to=linux-clusters@mindspring.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®