https://bugzilla.novell.com/show_bug.cgi?id=376165
User drankinatty@suddenlinkmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=376165#c11
David Rankin changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #11 from David Rankin 2008-04-03 23:40:12 MST ---
WAIT, WAIT a minute.
I don't mind buying a new board, but I don't think this is a HARDWARE
error. That is the point of the bug report.
Just because the log says it is, that doesn't make it so. Since when did we
start dismissing potential problems because the "log says it's hardware". God
knows log error messages are NOT infallible.
Did you even read the discussion above?? The problem goes AWAY when the
*software* nvidia driver isn't loaded. I've been running mprime for the past 10
hours with NO errors what so ever. This certainly merits more attention than an
arbitrary invalidation of the bug "because the log says so?"
10 hours no error no *software* driver loaded:
ps axf | grep mprime
788 pts/1 S+ 0:00 \_ grep mprime
19956 ? RN 628:02 ./mprime
I want help you validate that there isn't a generic problem with some of
the newer x86_64 chipsets.
If you have already diagnosed the problem from your look at the thorough
information I provided, then "what is it?" Are you telling the world that you
are absolutely sure a software error could not create the crash problem that is
being experienced when the nvidia kernel module is loaded?
What triggered the errors with the nvidia software module loaded at
addresses:
ADDR 2aaaad165cf0
ADDR 2aaf6b4262a0
ADDR 2aafbc3102b0
ADDR 2ab5d9f3d5f0
ADDR 2acbc6b2dbf0
ADDR 2ad0a10d93e0
ADDR 2ad2c6d787a0
ADDR 2b063ff544f0
ADDR 2b351ba197a0
ADDR 2b351ba197a0
ADDR 2b351ba197a0
ADDR 2b351ba197a0
ADDR 2b47840ed7b0
ADDR 2b7505fe1fa0
ADDR 2b76e1f8d3c0
ADDR 2b81c17b6ad0
ADDR 2b850b97d1f0
ADDR 2b8b094a6e20
ADDR 41df70
ADDR 43d930
ADDR eb4ceaa0
ADDR f0ce3900
ADDR f0cfb940
ADDR f0cfde20
ADDR f0d150f0
ADDR f688caf0
ADDR f688cc30
ADDR f6894530
ADDR f68adb70
ADDR f68ba940
ADDR f68d50f0
ADDR f69553f0
ADDR f74cda70
ADDR f74cfb20
ADDR f78cdbb0
ADDR f78e3900
ADDR ffff80220a20
ADDR ffff802603e0
ADDR ffff802962c0
ADDR ffff802a88a0
ADDR ffff8034d760
ADDR ffff803586a0
ADDR ffff803f3d80
ADDR ffff803f55f0
ADDR ffff803f55f0
ADDR ffff803f56b0
ADDR ffff880b1020
ADDR ffff88658f20
Why do the errors disappear when the *software* module is unloaded?
If you're right, I'm happy to send the board back, burn it, whatever.
However, if I'm right, and you miss this opportunity to better your product and
this problem snowballs, a lot of people will be getting screwed because we
couldn't take the time necessary to either rule in or rule out a software
problem.
If you know what the problem is, just post it and I'll happily send the
system back. If you don't know what it is and are just trying to punt this bug
as invalid, then it is time we get down to work and figure out what the problem
is.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.