linux-kernel - [3.11-rc4] Possible problem with nouveau drm driver and interrupts on Dell Latitude E6510

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 7 Aug 2013 14:41:09 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	David Airlie <airlied@...ux.ie>
Cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: [3.11-rc4] Possible problem with nouveau drm driver and interrupts on Dell Latitude E6510

My Latitude E6510 has the following graphics HW:

01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: Dell Latitude E6510
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e2000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at e0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at 7000 [size=128]
        Expansion ROM at e3000000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau

User-space is Fedora 17.  No proprietary drivers of any kind.

Up to the 3.11-rc2 kernel I never had any problems with it.

With 3.11-rc4 I've twice so far had the following problem:

0. X has been running for a while with fvwm, a couple of xterms, emacs, firefox, and xclock.

1. Suddenly text scrolling in xterm or emacs becomes extremely slow and grinds to a halt.
   Moving the mouse (which generates interrupts) resumes the scrolling, but then it stops
   again unless I keep moving the mouse.

2. At this time there are no kernel messages indicating problems.

3. If I exit X then the console behaves normally.

4. If I try to start X again it paints the background of my desktop and shows the mouse cursor,
   but nothing else comes up and it's unresponsive to mouse or keyboard input.
   I have to press C-A-D or the power button at this point.

5. After 1. above occurs, even a warm reboot isn't enough to make X work again.  A full
   power-cycled reboot is needed to bring the machine back to normal.

/Mikael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/