| Summary: | oops on rmmod nouveau with nv31m | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | prg | ||||||||||||||||||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||||||||
| Severity: | normal | ||||||||||||||||||||||||
| Priority: | medium | ||||||||||||||||||||||||
| Version: | git | ||||||||||||||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||
You seem to be using old kernel with serious bugs, see http://nouveau.freedesktop.org/wiki/UpstreamKernelIssues for more details. You should try building the whole kernel from nouveau/linux-2.6 repository if possible, otherwise upgrade to 2.6.31. Also, a memory corruption bug was squashed recently in nouveau drm, can you verify this issue still happens with current git? Created attachment 29990 [details]
dmesg on 2.6.31 after modprobe without modeset=1
Using 2.6.31 now, rebuilt everything from the x11 overlay, but when I do modprobe nouveau modeset=1 the screen turns off and the system freezes (sysrq doesn't work anymore), nothing in the log about that after reboot.
Attached the dmesg without modeset=1, but I guess it won't help much.
Nouveau-drm package from x11 overlay is still using master-compat, which is not up-to-date, and does not contain the fix. I updated the master-compat right now, it will propagate into the snapshot nouveau-drm uses within six hours, IIRC. I do not intend to update master-compat anymore. I'm using nouveau/linux-2.6 now, the system freezes here too with the latest commit (4e9caac6c3f7888848e1614bca0b4551fa196ce6), doing a bisect to find out when the freeze was introduced but compiling a kernel takes about half an eternity on this notebook. 756 revisions left to test after this (roughly 10 steps). Getting the old behaviour with 3f4f9a450f602251839f986f8785a78803c7d8da from 2009-08-08. 66960bf357b134b46044f46f5e80ed4d8ed86220 is first bad commit drm/nouveau: Import >=nv17 TV-out support. With the commit before that (b07297c4d302c8b1bb476cf8f4b67171dd1b6d38) I get the old behaviour. Created attachment 30013 [details] [review] patch0.diff Your bios tables seem a little bit misleading, does the attached patch change anything? (please attach some logs if it works around the hard lockup). The patch didn't help. Created attachment 30026 [details] [review] patch1.diff I'm attaching a couple of patches more that would be interesting to try... Created attachment 30027 [details] [review] patch2.diff Created attachment 30029 [details]
dmesg with patch1
KMS seems to be working fine with patch1.
With patch2 I still get the freeze.
(In reply to comment #10) > Created an attachment (id=30029) [details] > dmesg with patch1 > > KMS seems to be working fine with patch1. > With patch2 I still get the freeze. > So your card probably needs something to be done differently for TV-out load detection... An mmiotrace is likely to be very useful (see http://nouveau.freedesktop.org/wiki/MmioTraceHowto). I got a trace of modprobing nvidia, starting and exiting X, it's about 1.1MB lzma compressed, should I attach it here or send to that gmail adress? (In reply to comment #12) > I got a trace of modprobing nvidia, starting and exiting X, it's about 1.1MB > lzma compressed, should I attach it here or send to that gmail adress? > Yeah, you'd better send it to mmio.dumps at gmail.com. Done. Created attachment 30042 [details] [review] patch3.diff The attached patch should do the trick, nv31 TV load detection seems to be more like nv17 than other newer nv3x. I probably did some other untested assumptions about nv31 TV-out, so it would be nice if you tried it (Note that you'll surely need patch2 for it to work), but don't worry too much about it :-) Created attachment 30056 [details]
dmesg with KMS and a TV connected
KMS is working with patch2+3. Not sure how to enable TV out though. Running xrandr just returns "Output TV-0 is not disconnected but has no modes", no matter what I pass to xrandr. TV out is working fine if I set it up with the blob and nvidia-settings.
Created attachment 30057 [details]
Xorg.0.log with KMS and a TV connected
Created attachment 30058 [details] [review] patch4.diff Hm, that seems to be because of some recent DRM changes... the attached patch should fix it. (In reply to comment #18) > Created an attachment (id=30058) [details] > patch4.diff > > Hm, that seems to be because of some recent DRM changes... the attached patch > should fix it. > Actually no need for that, just updated xrandr from 1.2.3 to latest git, working fine now. (In reply to comment #19) > (In reply to comment #18) > > Created an attachment (id=30058) [details] [details] > > patch4.diff > > > > Hm, that seems to be because of some recent DRM changes... the attached patch > > should fix it. > > > > Actually no need for that, just updated xrandr from 1.2.3 to latest git, > working fine now. > Weird, it really shouldn't have worked without it. Pekka has pushed the fixes so I'm marking this as closed. Thanks! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 28436 [details] dmesg after rmmod nouveau i'm trying to get kms working on my nv31m on gentoo using the x11 overlay, when i do modprobe nouveau modeset=1 the screen still stays the same resolution (80x25 chars) and the cursor freezes in place though i'm still able to type stuff. when i rmmod nouveau i get an oops (attached) everything from the overlay is up to date. i'm using nouveau-drm instead of x11-drm i have FRAMEBUFFER_CONSOLE=y