Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-11-05 Thread Andreas Beckmann 
On 2015-10-27 18:15, Stéphane Glondu wrote:
> Le 27/10/2015 17:07, Stéphane Glondu a écrit :
>> It seems that I am experiencing the same bug. I have upgraded to
>> 304.128-6, and the bug is still present.

No, whatever you experienced is clearly a differnent problem, there is
nothing about "busid" in there.

> I tried using the vesa driver. It worked for a few hours, then froze the
> graphical display (I could still SSH in). Then, it never worked again. I
> tried with different drivers: nouveau, fbdev. None of them work (X
> doesn't start). I then downgraded the kernel to 4.1.0-2-amd64 and it
> seems to work. Note: in the process, I also downgraded
> xserver-xorg-video-nvidia-legacy-304xx to 304.125-2.

304.128-7 should be worthwile to test, it should fix the permission
issues in case you ran into them ...

> Note: it seems that #801515 happens when using the nvidia driver. I have
> no idea how it is related.

No clue either.

If your problem is persisting, please open a new bug report, don't
followup here.


Andreas

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-10-27 Thread Stéphane Glondu 
Le 27/10/2015 17:07, Stéphane Glondu a écrit :
> It seems that I am experiencing the same bug. I have upgraded to
> 304.128-6, and the bug is still present.

I tried using the vesa driver. It worked for a few hours, then froze the
graphical display (I could still SSH in). Then, it never worked again. I
tried with different drivers: nouveau, fbdev. None of them work (X
doesn't start). I then downgraded the kernel to 4.1.0-2-amd64 and it
seems to work. Note: in the process, I also downgraded
xserver-xorg-video-nvidia-legacy-304xx to 304.125-2.

Note: it seems that #801515 happens when using the nvidia driver. I have
no idea how it is related.

Cheers,

-- 
Stéphane

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-10-20 Thread Luis Carvalheiro 
Package: nvidia-legacy-304xx-driver
Version: 304.125-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

since my last dist-upgrade, X fails to start when installing this package. When
system boots, the screen starts to flicker, and X doesn't come up.

The error lines in Xorg.0.log are:

EE) [mi] EQ overflowing.  Additional events will be discarded until existing
events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (xorg_backtrace+0x4e) [0x55ad24a5685e]
(EE) 1: /usr/bin/Xorg (mieqEnqueue+0x253) [0x55ad24a38893]
(EE) 2: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x55ad24912fd2]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbb45779000+0x60a7)
[0x7fbb4577f0a7]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fbb45779000+0x687d)
[0x7fbb4577f87d]
(EE) 5: /usr/bin/Xorg (0x55ad248a3000+0x96848) [0x55ad24939848]
(EE) 6: /usr/bin/Xorg (0x55ad248a3000+0xbf6f8) [0x55ad249626f8]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbb4ca9e000+0x35180)
[0x7fbb4cad3180]
(EE) 8: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x9ef42)
[0x7fbb4710ff42]
(EE) 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0xa0c43)
[0x7fbb47111c43]
(EE) 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x11fb71)
[0x7fbb47190b71]
(EE) 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x701bbd)
[0x7fbb47772bbd]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x701daf)
[0x7fbb47772daf]
(EE) 13: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7fbb47071000+0x6f19b0)
[0x7fbb477629b0]
(EE) 14: /usr/bin/Xorg (0x55ad248a3000+0x13c351) [0x55ad249df351]
(EE) 15: /usr/bin/Xorg (0x55ad248a3000+0x131f87) [0x55ad249d4f87]
(EE) 16: /usr/bin/Xorg (0x55ad248a3000+0x5807f) [0x55ad248fb07f]
(EE) 17: /usr/bin/Xorg (0x55ad248a3000+0x5c1cb) [0x55ad248ff1cb]
(EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
[0x7fbb4cabfb45]
(EE) 19: /usr/bin/Xorg (0x55ad248a3000+0x465be) [0x55ad248e95be]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up
the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
[  4371.719] [mi] Increasing EQ size to 1024 to prevent dropped events.
[  4371.720] [mi] EQ processing has resumed after 75 dropped events.
[  4371.720] [mi] This may be caused my a misbehaving driver monopolizing the
server's resources.


Relevant information from /var/log/messages:

Oct 19 10:16:14 munch gdm3: Unable to kill session worker process
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: X.Org X Server 1.17.2
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Release Date:
2015-06-16
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: X Protocol Version 11,
Revision 0
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Build Operating
System: Linux 4.2.0-1-amd64 x86_64 Debian
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Current Operating
System: Linux munch 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 root=UUID=5018e4ce-ecb4-43eb-
95e0-81251baa6b4a ro quiet
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Build Date: 06 October
2015  07:27:47AM
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: xorg-server 2:1.17.2-3
(http://www.debian.org/support)
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Current version of
pixman: 0.33.2
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Before reporting
problems, check http://wiki.x.org
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: to make sure that you
have the latest version.
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: Markers: (--) probed,
(**) from config file, (==) default setting,
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (++) from command
line, (!!) notice, (II) informational,
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (WW) warning, (EE)
error, (NI) not implemented, (??) unknown.
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Log file:
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Mon Oct 19 10:16:15 2015
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Using config
file: "/etc/X11/xorg.conf"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) Using system
config directory "/usr/share/X11/xorg.conf.d"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (==) ServerLayout
"Layout0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Screen
"Screen0" (0)
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |   |-->Monitor
"Monitor0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |   |-->Device
"Device0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Input Device
"Keyboard0"
Oct 19 10:16:15 munch /usr/lib/gdm3/gdm-x-session[1781]: (**) |-->Input Device
"Mouse0"
Oct 19 10:16:15 munch

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-10-20 Thread Andreas Beckmann 
On 2015-10-20 11:10, Luis Carvalheiro wrote:
> Package: nvidia-legacy-304xx-driver
> Version: 304.125-2

This is not a recent (legacy) driver version. Or you didn't report the
bug on the system where it happened.

Please run
  reportbug -N 802452
in the failing system to collect system information.


Andreas

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-10-20 Thread Andreas Beckmann 
On 2015-10-20 13:32, Luis Carvalheiro wrote:
> Dear Maintainer,
> 
> I had to apt-get remove --purge nvidia* to get a working graphical
> environment. I used reportbug in a GUI to report it after that. When i run
> reportbug -N 802452 i can't add nothing more. I reported the bug in the
> failing system.

Well, that's not the failing system any more.

> Do you want me to install nvidia-legacy-304xx-driver, switch to a
> text-based reportbug and fill a new bug report?

That would be great. Just reportbug -N 802452 should collect the info.


Andreas

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

2015-10-20 Thread Andreas Beckmann 
On 2015-10-20 11:10, Luis Carvalheiro wrote:
> Oct 19 10:03:09 munch kernel: [177312.799746] No drm_driver.set_busid()
> implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to
> set the unique name explicitly.

Yes, same error as in #801193, now that I looked for it specifically.


Andreas