Re: [Nouveau] vdpau problems and logging
Op 14-03-13 10:47, Steven Ward schreef: Hi Maarten, I'm sure I have downloaded and installed the latest libvdpau firmware from git.. I will check the git repository for Mesa and re-compile it again. I will invoke the git version of Mesa with nvgl when I start the video players again. Are you sure it's picking up the right vdpau_nouveau though? Maybe your distro has one in path, you could try strace to see where it gets libvdpau_nouveau.so from. The way I got the mmiotradce is this: I downloaded and installed the 313 blob for my Chakra default kernel sudo pacman -S nvidia I rebooted back to the desktop. I then logged out and ended up at KDM. I then selected console login from the KDM settings there. When I got a prompt, I pressed Alt+Ctrl+F3 to get myself to tty 3 it was the only way to get there with my Chakra installation,as I've tried to invoke init 3 from the advanced kernel options with no success. Anyway, I invoked su my password,then sudo echo mmiotrace /sys/kernel/debug/tracing/current_tracer *return* Then I ran sudo cat /sys/kernel/debug/tracing/trace_pipe 21 ¦ tee /home/steve/video-dump.txt startx Then X started up and I saw the nvidia logo flash as well. I then went onto konsole and ran the mplayer command string with the mkv file from beginning to end (the video was roughly 24 minutes) After the video had finished and had caught a trace. I logged back out again,and stopped the mmiotrace from the tty 3 console. You don't need to play an actual video, just having mplayer initialize video is enough. The nvidia module must be unloaded before you start your mmiotrace, easiest is to ssh into the machine. The script I'm using for mmiotrace is: http://people.freedesktop.org/~mlankhorst/mmiotrace-nvidia.sh Connect to the machine with ssh, make sure your display manager is stopped, and nvidia module is unloaded, then run the script and in the shell it spawns, type: /usr/bin/X :0 sleep 5 # if you copy paste, give it some time to init, if not just skip this and wait 5 seconds DISPLAY=:0 envytools/vdpow/mmt_ufw # check if it returns any errors like unable to connect to display, if not you're good exit 0 The mmiotrace should be in /tmp/current_trace.txt now, and have all the kernel firmwares you need. ~Maarten ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing
Marcin Slusarz wrote: I think it may be already fixed by commit 94f54f5336aac6801f2a14dcb12467e41b35456a drm/nv50: encoder creation failure doesn't mean full init failure (post 3.9-rc2) With the latest 3.9-rc2+ git, I got past the KMS init blackout and into X, but I got a panic shortly after. Unfortunately, the trace was too lengthy to see in which module, and since it wasn't captured /var/log/syslog, I have no idea whether it has anything to do with nouveau or something else. tl;dr: It would seem that the commit fixes the specific bug I reported, but my system isn't functional. Thank you so far anyway, Sune Mølgaard -- Nothing exists except atoms and empty space; everything else is opinion. - Democritus ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Fwd: [bisected] nouveau failure with 3.9-rc1 and ongoing
On Thu, Mar 14, 2013 at 07:56:03PM +0100, Sune Mølgaard wrote: Marcin Slusarz wrote: I think it may be already fixed by commit 94f54f5336aac6801f2a14dcb12467e41b35456a drm/nv50: encoder creation failure doesn't mean full init failure (post 3.9-rc2) With the latest 3.9-rc2+ git, I got past the KMS init blackout and into X, but I got a panic shortly after. Unfortunately, the trace was too lengthy to see in which module, and since it wasn't captured /var/log/syslog, I have no idea whether it has anything to do with nouveau or something else. tl;dr: It would seem that the commit fixes the specific bug I reported, but my system isn't functional. If you have another machine in the same network, you could try to catch this panic with netconsole. See http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/netconsole.txt Marcin ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 62351] New: Segfault in nouveau_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=62351 Priority: medium Bug ID: 62351 Assignee: nouveau@lists.freedesktop.org Summary: Segfault in nouveau_dri.so Severity: major Classification: Unclassified OS: Linux (All) Reporter: s...@molgaard.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/nouveau Product: Mesa Using xorg-edgers PPA on ubuntu 12.10 but with newer vanilla kernel, I consistently get the following when attempting to start the DE Cinnamon as well as Gnome 3 upon which it is based: cinnamon[4414]: segfault at 1 ip 7f0bf3d24f95 sp 7fffac52e440 error 4 in nouveau_dri.so[7f0bf3cb6000+143000] According to dpkg, the version is git20130227. Card is a NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2) Please advise as to how I can provide more info and possibly test patches. Best regards, Sune Mølgaard -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 62351] Segfault in nouveau_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=62351 Ungifted ungift...@ya.ru changed: What|Removed |Added CC||ungift...@ya.ru --- Comment #1 from Ungifted ungift...@ya.ru --- Same on Gentoo and mesa- (~ 2-3 weeks) -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 62351] Segfault in nouveau_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=62351 --- Comment #2 from Ungifted ungift...@ya.ru --- Created attachment 76541 -- https://bugs.freedesktop.org/attachment.cgi?id=76541action=edit backtrace gdb /usr/bin/gnome-shell run bt full -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] Nouveau not working on second monitor
Your kernel log shows that nouveau isn't loaded. Instead, an old version of the closed-source nVidia driver is brought up, possibly when X starts. Get rid of it and make sure to remove nouveau from the blacklist. Op 27-02-13 20:48, rv0...@aol.com schreef: Hi, I have a problem that my nouveau driver does not properly load every time I boot my laptop. It either: - defaults to the vesa driver (always if my power cord is plugged into the laptop - starts nouveau but without the external monitor - starts nouveau WITH the external monitor (as it should be) (starting without the monitor attached and then connecting it always fails crashes X) How/where can i find any help for this? Details: - Ubuntu 12.10. - card: VGA compatible controller: NVIDIA Corporation G86 [GeForce 8400M GT] (rev a1) - kernel 3.5.0-25-generic - X.Org X Server 1.13.0 Release Date: 2012-09-05 - all nv nvidia drivers are blacklisted - the problem has grown worse over the last 2 years ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] nouveau lockdep splat
On Tue, Mar 05, 2013 at 05:30:52PM +0100, Lucas Stach wrote: Dropping Tegra ML, it's not the place where Nouveau mails should go. $ ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau/nv50_display.c ... linux-te...@vger.kernel.org (open list:TEGRA SUPPORT) Maybe get_maintainer.pl patterns need correction... Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] nouveau lockdep splat
On 03/06/2013 12:14 PM, Marcin Slusarz wrote: On Wed, Mar 06, 2013 at 01:04:29AM +0100, Borislav Petkov wrote: On Tue, Mar 05, 2013 at 05:30:52PM +0100, Lucas Stach wrote: Dropping Tegra ML, it's not the place where Nouveau mails should go. $ ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau/nv50_display.c ... linux-te...@vger.kernel.org (open list:TEGRA SUPPORT) Maybe get_maintainer.pl patterns need correction... That's new feature (introduced in commit eb90d0855b75f8 get_maintainer: allow keywords to match filenames) of get_maintainer.pl which now can look at file contents... get_maintainer.pl could always look at file contents IIRC. The change was that I added keyword tegra to the Tegra section that now matches this file's contents. ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau ... might be a better invocation, although perhaps I should add an explicit exclusion for nouveau to the Tegra section in MAINTAINERS. ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] nouveau lockdep splat
On Wed, Mar 06, 2013 at 08:14:18PM +0100, Marcin Slusarz wrote: On Wed, Mar 06, 2013 at 01:04:29AM +0100, Borislav Petkov wrote: On Tue, Mar 05, 2013 at 05:30:52PM +0100, Lucas Stach wrote: Dropping Tegra ML, it's not the place where Nouveau mails should go. $ ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau/nv50_display.c ... linux-te...@vger.kernel.org (open list:TEGRA SUPPORT) Maybe get_maintainer.pl patterns need correction... That's new feature (introduced in commit eb90d0855b75f8 get_maintainer: allow keywords to match filenames) of get_maintainer.pl which now can look at file contents... TEGRA SUPPORT M:Stephen Warren swar...@wwwdotorg.org L:linux-te...@vger.kernel.org Q:http://patchwork.ozlabs.org/project/linux-tegra/list/ T:git git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git S:Supported K:(?i)[^a-z]tegra Note the last line and this: $ grep tegra drivers/gpu/drm/nouveau/nv50_display.c u32 rekey = 56; /* binary driver, and tegra constant */ max_ac_packet -= 18; /* constant from tegra */ Fun. Yeah, and a lot of it, thanks for digging this out. So obviously this regex is a bit... unfortunate. Although the idea of grepping the files for unique patterns is not bad, I have to admit. :-) -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] nouveau lockdep splat
On Wed, Mar 06, 2013 at 12:31:49PM -0700, Stephen Warren wrote: get_maintainer.pl could always look at file contents IIRC. The change was that I added keyword tegra to the Tegra section that now matches this file's contents. ./scripts/get_maintainer.pl -f drivers/gpu/drm/nouveau ... might be a better invocation, although perhaps I should add an explicit exclusion for nouveau to the Tegra section in MAINTAINERS. No, you should add a pattern which matches only tegra. If there's no such pattern, you should simply drop the K: thing. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
