I've managed to produce an oops on 2.4.4-ac7 that specifically mentions
the rivafb. As such I produced a BUG-REPORT and sent it to the address
listed in MAINTAINERS for:
NVIDIA (RIVA) FRAMEBUFFER DRIVER
P: Ani Joshi
M: aj...@sh...
L: lin...@li...
S: Maintained
Since then, I've received no reply, but I'm getting a WARNING: message
delayed...:
From: Pos...@un...
To: gbs...@lc...
Subject: WARNING: message delayed at "mlucom8.urz.uni-halle.de"
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.5K --]
>>>>> This report is generated automatically. <<<<<
This report relates to your message:
Subject: PROBLEM: 2.4....
This message has still not yet been delivered to the following
recipients:
wa...@in...
The message is queued for processing on mlucom8.urz.uni-halle.de.
Delays are usually created by hosts being down, less often
by network outages.
Delivery attempts will continue and no action on your part is required.
If the message cannot be delivered in the next 131 hours,
it will be returned to you.
[-- Attachment #2 --]
[-- Type: message/delivery-status, Encoding: 7bit, Size: 0.2K --]
Reporting-MTA: dns; mlucom8.urz.uni-halle.de
Final-Recipient: rfc822;wa...@in...
Action: delayed
Status: 4.0.0
Will-Retry-Until: Thu, 17 May 2001 19:00:19 +0000
Leads me to think one or both of those addresses are faulty? All I get
when trying http://lists.surfsouth.com is connection refused, so.. I'm
trying to follow-up here.
Unfortunately, I cannot produce the original bug-report, I didn't save
it, but I may just get a copy when the above mailer finally quits -).
Anyway, I compiled 2.4.4ac7 with k6 support as my Duron with k7 opts
will fail to boot every time. I have a Riva TNT original (16MB) card.
With the rivafb compiled into the kernel I produced the oops, with
vesafb -- no problems.
Attached is a tarball containing my config, kern.log the oops appears
in, result of oops run through ksymoops, and result of lspci -vvv as
root.
Hope someone can look at or redirect this appropriately.
Thanks=20
Gordon Sadler
|
