Re: [Nouveau] [PATCH 1/3] drm/nouveau/therm: turn on a fan only when crossing threshold in positive direction

2013-02-08 Thread Martin Peres
On 03/02/2013 21:07, Marcin Slusarz wrote: + the same for shutdown threshold - seems impossible, but shutdown can fail. Signed-off-by: Marcin Slusarz marcin.slus...@gmail.com Looks good. Please add my signed-off-by Signed-off-by: Martin Peres martin.pe...@labri.fr ---

Re: [Nouveau] [PATCH 2/3] drm/nv40/therm: reset temperature sensor on init

2013-02-08 Thread Martin Peres
On 03/02/2013 21:07, Marcin Slusarz wrote: Current uninitialized sensor detection does not work for me on nv4b and sensor returns crazy values (190°C). It stabilises later, but it's too late - therm code shutdowns the machine... Let's just reset it on init. Signed-off-by: Marcin Slusarz

Re: [Nouveau] [PATCH 3/3] drm/nouveau/therm: use workqueue to shutdown the machine

2013-02-08 Thread Martin Peres
On 03/02/2013 21:07, Marcin Slusarz wrote: orderly_poweroff cannot be called from atomic context. Signed-off-by: Marcin Slusarz marcin.slus...@gmail.com Oops, my bad. Please add my signed-off-by. ___ Nouveau mailing list

Re: [Nouveau] [PATCH] drm/nouveau: add lockdep annotations

2013-02-08 Thread Peter Hurley
Hi Maarten On Mon, 2013-02-04 at 22:59 +0100, Maarten Lankhorst wrote: Op 04-02-13 22:30, Marcin Slusarz schreef: 1) Lockdep thinks all nouveau subdevs belong to the same class and can be locked in arbitrary order, which is not true (at least in general case). Tell it to distinguish

Re: [Nouveau] Monitor with corrupted EDID

2013-02-08 Thread Flavio Castelli
On 02/07/2013 08:37 PM, mwesten wrote: I recently used a DOS program called ddcw.exe to fix the corrupted EDID on one of my monitors. I already tried to write the good EDID into the monitor but I failed. I also tried to do that using i2cset with the same result. I suspect the EEPROM is write

Re: [Nouveau] Monitor with corrupted EDID

2013-02-08 Thread mwesten
On 02/08/2013 03:23 AM, Flavio Castelli wrote: On 02/07/2013 08:37 PM, mwesten wrote: I recently used a DOS program called ddcw.exe to fix the corrupted EDID on one of my monitors. I already tried to write the good EDID into the monitor but I failed. I also tried to do that using i2cset with

Re: [Nouveau] Monitor with corrupted EDID

2013-02-08 Thread Flavio Castelli
On 02/08/2013 11:44 AM, mwesten wrote: My suspicion is that if the EDID data got corrupted in the first place, then it's not protected. I don't know about i2cset, or any other methods. That's exactly what I'm thinking. I'm trying to overwrite the EEPROM using a DVI cable (since it's the DVI

[Nouveau] [Bug 60510] New: Firefox 18.0.2 Crash On Nvidia GeForce2

2013-02-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60510 Priority: medium Bug ID: 60510 Assignee: nouveau@lists.freedesktop.org Summary: Firefox 18.0.2 Crash On Nvidia GeForce2 QA Contact: xorg-t...@lists.x.org Severity: normal

[Nouveau] [Bug 60516] New: nouveau driver graphics corrupted in 3.7 kernel for nvidia FX5200 [NV34] hardware

2013-02-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60516 Priority: medium Bug ID: 60516 Assignee: nouveau@lists.freedesktop.org Summary: nouveau driver graphics corrupted in 3.7 kernel for nvidia FX5200 [NV34] hardware QA Contact:

[Nouveau] [Bug 60516] nouveau driver graphics corrupted in 3.7 kernel for nvidia FX5200 [NV34] hardware

2013-02-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60516 --- Comment #1 from Lee Matheson lee_mathe...@hotmail.com --- I note a bug report on Red Hat bugzilla (kernel-PAE-3.7.3-101.fc17.i686) which could be the same: https://bugzilla.redhat.com/show_bug.cgi?id=905631 (and also

[Nouveau] [Bug 60516] nouveau driver graphics corrupted in 3.7 kernel for nvidia FX5200 [NV34] hardware

2013-02-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60516 --- Comment #2 from Lee Matheson lee_mathe...@hotmail.com --- This bug here may be the same: https://bugs.freedesktop.org/show_bug.cgi?id=58261 -- You are receiving this mail because: You are the assignee for the bug.

[Nouveau] [Bug 57350] [nouveau, linux-3.7-rc] Broken cursor and kernel log swamped with trapped reads/writes from BAR/PFIFO_READ/FB

2013-02-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=57350 --- Comment #11 from Ankur an...@lipidity.com --- I also have this issue on a MacBook5,1 Bottom half of mouse cursor is transparent. There are thousands of trapped read at ... on channel ... BAR/PFIFO_READ/FB reason: PAGE_NOT_PRESENT with