Thanks Rob. Sorry for the extra noise with the previous automated call
for testing that was posted. I'll go ahead and mark this Fix
Released. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in
See note posted on 2008-08-11, please.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://bugs.launchpad.net/bugs/56096
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I think this can be closed. I don't know if a kernel upgrade fixed the
issue, or an nvidia driver, but this hasn't happed for a rather long
time.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://bugs.launchpad.net/bugs/56096
You received this bug notification because you are a
Setting back to unconfirmed and changing linux-source version, however
this is probably a bug in the NVIDIA binary driver (since the open
source driver can't do SLI) and should probably be punted to linux-
restricted-modules...
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename:
Rob:
Is this still a problem in Feisty?
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://bugs.launchpad.net/bugs/56096
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yes, and the 100.14.03 driver makes it even worse.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://bugs.launchpad.net/bugs/56096
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm also having the same problem. I have a Foxconn C51XEM2AA Motherboard
(AM2 nForce 590 SLI) and an A64 X2 4600+ (Socket AM2). I also compiled
my own 2.6.17 kernel with the beyond3 patchset, and enabled SMP support.
I also installed the latest nVidia driver, the 8774. When I enable SLI
in the
Well, I spoke too soon. I was able to get in and out of an app twice,
but after a reboot, the system just hard locks again. I'll keep trying
to capture the oops or whatever is happening.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://launchpad.net/bugs/56096
--
ubuntu-bugs
As a test, I upgraded to the 8776 driver last night. The system no
longer locks. There are still other problems, like the new evdev blows
chunks and fails to initialize about half the time, but that's a
separate issue.
--
2.6.15 K7 and above - enabling SLI hard locks the system
Sorry, minor correction... s/8776/8774/
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://launchpad.net/bugs/56096
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Still trying to replicate. So far, X either just hard locks, or using
pci=conf1, X segfaults with the above error. I may see about relocating
this system so I can hook a console cable to it.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://launchpad.net/bugs/56096
--
So far, I haven't been able to replicate, as the system usually just
hard locks when this happens. I did, however, notice this:
[17186079.472000] irq 58: nobody cared (try booting with the irqpoll option)
[17186079.472000] [c014e31a] __report_bad_irq+0x2a/0x90
[17186079.472000] [c014daed]
One other thing possibly of interest or not.. from the xorg.0.log.old:
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x86) [0x80b4a86]
1: [0xe420]
2:
Please attach dmesg from either 2.6.15-26-k7 in dapper, or 2.6.17-6-k7
in edgy.
Thanks
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed = Needs Info
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://launchpad.net/bugs/56096
--
ubuntu-bugs mailing list
I'm going to have to reject this bug unless you can reproduce it with a
stock Ubuntu kernel. Self compiled kernels are your responsibility.
** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux-meta = linux-source-2.6.17
--
2.6.15 K7 and above - enabling SLI hard locks the system
Sorry if I wasn't clear This started with the stock 2.6.15-xx-k7
kernels on breezy. I was simply saying that I tried the 2.6.17 kernel at
the request of nvidia to see if that resolved the issue. It didn't.
--
2.6.15 K7 and above - enabling SLI hard locks the system
Here's the oops message and xorg logs. nvidia is unable to reproduce
because they don't have my board.
--
2.6.15 K7 and above - enabling SLI hard locks the system
https://launchpad.net/bugs/56096
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
18 matches
Mail list logo
