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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 01 Jan 2014 00:41:48 +0000
From:	Sid Boyce <sboyce@...eyonder.co.uk>
To:	Ilia Mirkin <imirkin@...m.mit.edu>
CC:	LKML Mailing List <linux-kernel@...r.kernel.org>,
	opensuse factory list <opensuse-factory@...nsuse.org>,
	"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>
Subject: Re: Possible 3.13-rc nouveau regression with GT 560 Ti

On 31/12/13 10:36, Ilia Mirkin wrote:
> On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce <sboyce@...eyonder.co.uk> wrote:
>> System x86_64 with openSUSE 13.1.
>> X.Org version: 1.14.99.905
>>
>> openSUSE 12.2 kernels boot successfully into a graphical screen, login to
>> KDE4, etc. all normal.
>>
>> 3.13-rc kernels boot fully with X running but no graphical screen and it
>> freezes in VC with not all the startup messages displayed but I could ssh in
>> from another box to check dmesg and logs.
>>
>> Xorg.0.log which I thought I had saved did not log an error.
>>
>> dmesg said "nouveau Playlist update failed".
>>
>> Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and
>> running.
>>
>> If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log
>> information.
> Having a dmesg would be nice. One thing I can think of off-hand is
> that 3.13-rc has MSI turned on by default. You can turn it off by
> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that
> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should
> show the offending commit fairly quickly.
>
>    -ilia
>
Adding "nouveau.config=NvMSI=0" to the command line fixed the problem.
So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 
introduced it.
Thanks Ilia,
Regards
Sid.

-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
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/

Powered by blists - more mailing lists