[Bug 1574354] Re: playing .mp4 in VLC freezes machine
Same problem (assumed) here with Kubuntu 16.04, and Kubuntu 17.10. Nvidia 384.90 video drivers. Seeking in large files causes VLC to hang freezing the desktop session. Sometimes I can CTL-ALT-F2 and get a console session. VLC cant be killed, wont even die with a -9 for several minutes. Sometimes I cant even CTL-ALT-F2 to a console. Graphical console is completely frozen. I can ssh in, which leads me to believe that the problem is not that the entire system is frozen, just something in the video side. Ive tried every setting in VLC I can from disabling hardware acceleration, use/dont use VDPAU, etc.. Other video players which do use HW Acceleration seem to have no issue. The larger the file, the more I seek/skip, the more likley VLC is to trigger the freeze. Relevant Graphical PKGS: rc libcg:amd64 3.1.0013-2 amd64Nvidia Cg core runtime library rc libcggl:amd64 3.1.0013-2 amd64Nvidia Cg Opengl runtime library all X Window System (X.Org) infrastructure ii xfonts-utils1:7.7+4 amd64X Window System font utility programs ii xorg1:7.7+19ubuntu3 amd64X.Org X Window System ii libvdpau1:amd64 1.1.1-3ubuntu1 amd64Video Decode and Presentation API for Unix (libraries) ii libvdpau1:i386 1.1.1-3ubuntu1 i386 Video Decode and Presentation API for Unix (libraries) ii mesa-vdpau-drivers:amd6417.2.2-0ubuntu1 amd64Mesa VDPAU video acceleration drivers ii mesa-vdpau-drivers:i386 17.2.2-0ubuntu1 i386 Mesa VDPAU video acceleration drivers ii vdpau-driver-all:amd64 1.1.1-3ubuntu1 amd64Video Decode and Presentation API for Unix (driver metapackage) ii vdpau-driver-all:i386 1.1.1-3ubuntu1 i386 Video Decode and Presentation API for Unix (driver metapackage) ii vdpau-va-driver:amd64 0.7.4-6 amd64VDPAU-based backend for VA API ii vdpau-va-driver:i3860.7.4-6 i386 VDPAU-based backend for VA API ii vdpauinfo 1.0-1 amd64Video Decode and Presentation API for Unix (vdpauinfo utility) ii libvlc-bin:amd642.2.6-6 amd64tools for VLC's base library ii libvlc5:amd64 2.2.6-6 amd64multimedia player and streamer library rc libvlccore5 2.0.8-1 amd64base library for VLC and its modules rc libvlccore7 2.1.6-0ubuntu14.04.1 amd64base library for VLC and its modules ii libvlccore8:amd64 2.2.6-6 amd64base library for VLC and its modules ii vlc 2.2.6-6 amd64multimedia player and streamer ii vlc-bin 2.2.6-6 amd64binaries from VLC ii vlc-data2.2.6-6 all Common data for VLC ii vlc-l10n2.2.6-6 all Translations for VLC rc vlc-nox 3.0.0~~git20160813+r65787+62~ubuntu16.04.1 amd64multimedia player and streamer (without X support) ii vlc-plugin-base:amd64 2.2.6-6 amd64multimedia player and streamer (base plugins) ii vlc-plugin-notify:amd64 2.2.6-6 amd64LibNotify plugin for VLC ii vlc-plugin-qt:amd64 2.2.6-6 amd64multimedia player and streamer (Qt plugin) ii vlc-plugin-samba:amd64 2.2.6-6 amd64Samba plugin for VLC ii
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
Good News! The issue was a card issue that was resolved working with EVGA. Today I re-imaged again with a clean 16.04.01 Kubuntu, dist-update, then added the PPA and installed the nvidia-367 package from the PPA. 1060 works correctly! I can also vouch for the 1070 working with the same PPA & driver as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
The current nvidia-367 package installed on a clean new 16.04 install with nvidia evga 1060 fails to boot after the nvidia-367 package is installed. ** Attachment added: "gpu-manager from a clean new install" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+attachment/4733302/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
Heres the Xorg logs from the same clean system. The .old is from the default setup that the system booted on from the install image before adding nvidia-367. ** Attachment added: "Xorg Logs" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+attachment/4733303/+files/Xorg.logs.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386619] Re: *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated
I gave up. I got somethings working, but decided to wait and try again when karmic comes out. On 10/15/09, Chuck Short chuck.sh...@canonical.com wrote: Hi, I was wondering if you were still having this problem. Regards chuck ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = Low ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a direct subscriber of the bug. Status in “multipath-tools” package in Ubuntu: Incomplete Bug description: Binary package hint: multipath-tools Jaunty server 32-bit. Running mpath_prio_hds_modular against any device causes the *** stack smashing detected *** message to be displayed. r...@tie-interceptor:~# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb8074da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb8074d60] /sbin/mpath_prio_hds_modular[0x8048b92] /sbin/mpath_prio_hds_modular[0x80486b3] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f8d775] /sbin/mpath_prio_hds_modular[0x8048551] === Memory map: 08048000-08049000 r-xp 09:02 1537228 /sbin/mpath_prio_hds_modular 08049000-0804a000 r--p 1000 09:02 1537228 /sbin/mpath_prio_hds_modular 0804a000-0804b000 rw-p 2000 09:02 1537228 /sbin/mpath_prio_hds_modular 09e2c000-09e4d000 rw-p 09e2c000 00:00 0 [heap] b7f63000-b7f7 r-xp 09:02 1496221/lib/libgcc_s.so.1 b7f7-b7f71000 r--p c000 09:02 1496221/lib/libgcc_s.so.1 b7f71000-b7f72000 rw-p d000 09:02 1496221/lib/libgcc_s.so.1 b7f76000-b7f77000 rw-p b7f76000 00:00 0 b7f77000-b80d3000 r-xp 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d3000-b80d4000 ---p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d4000-b80d6000 r--p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d6000-b80d7000 rw-p 0015e000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d7000-b80da000 rw-p b80d7000 00:00 0 b80dd000-b80e rw-p b80dd000 00:00 0 b80e-b80e1000 r-xp b80e 00:00 0 [vdso] b80e1000-b80fd000 r-xp 09:02 1496222/lib/ld-2.9.so b80fd000-b80fe000 r--p 0001b000 09:02 1496222/lib/ld-2.9.so b80fe000-b80ff000 rw-p 0001c000 09:02 1496222/lib/ld-2.9.so bfdea000-bfdff000 rw-p bffeb000 00:00 0 [stack] Aborted I got new source for Version 2.01 from the mpath_prio_hds_modular author. Version 2.01 Changes 2007-11-13: o Source code changes: § Delete #include libdevmapper.h § Deletechar vendor[8] § Add char vendor[9] Compiled it with: # gcc pp_hds_modular.c –o mpath_prio_hds_modular Copy the prioritizer: # cp mpath_prio_hds_modular /sbin Now mpath_prio_hds_modular works correctly: r...@tie-interceptor:/# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 0 However one part of the multipath package seems to be missing from the ubuntu package. multipath normally requires /sbin/scsi_id to exist. Looks like udev puts scsi_id in a strange place, and there is an existing bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481447 for that. So I symlinked the /lib/udev/scsi_id to /sbin/scsi_id However the version of scsi_id that is there does not support the -s flag and fails: r...@tie-interceptor:/sbin# multipath /sbin/scsi_id: invalid option -- 's' error calling out /sbin/scsi_id -g -u -s /block/sda /sbin/scsi_id: invalid option -- 's' It appears that the version of scsi_id that is supplied with ubuntu is a bit different than the version in RH, or SUSE. r...@tie-interceptor:/sbin# /lib/udev/scsi_id --version 141 -- Sent from my mobile device ** Bug watch added: Debian Bug tracker #481447 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481447 -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 386619] Re: *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated
I gave up. I got somethings working, but decided to wait and try again when karmic comes out. On 10/15/09, Chuck Short chuck.sh...@canonical.com wrote: Hi, I was wondering if you were still having this problem. Regards chuck ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = Low ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a direct subscriber of the bug. Status in “multipath-tools” package in Ubuntu: Incomplete Bug description: Binary package hint: multipath-tools Jaunty server 32-bit. Running mpath_prio_hds_modular against any device causes the *** stack smashing detected *** message to be displayed. r...@tie-interceptor:~# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb8074da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb8074d60] /sbin/mpath_prio_hds_modular[0x8048b92] /sbin/mpath_prio_hds_modular[0x80486b3] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f8d775] /sbin/mpath_prio_hds_modular[0x8048551] === Memory map: 08048000-08049000 r-xp 09:02 1537228 /sbin/mpath_prio_hds_modular 08049000-0804a000 r--p 1000 09:02 1537228 /sbin/mpath_prio_hds_modular 0804a000-0804b000 rw-p 2000 09:02 1537228 /sbin/mpath_prio_hds_modular 09e2c000-09e4d000 rw-p 09e2c000 00:00 0 [heap] b7f63000-b7f7 r-xp 09:02 1496221/lib/libgcc_s.so.1 b7f7-b7f71000 r--p c000 09:02 1496221/lib/libgcc_s.so.1 b7f71000-b7f72000 rw-p d000 09:02 1496221/lib/libgcc_s.so.1 b7f76000-b7f77000 rw-p b7f76000 00:00 0 b7f77000-b80d3000 r-xp 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d3000-b80d4000 ---p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d4000-b80d6000 r--p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d6000-b80d7000 rw-p 0015e000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d7000-b80da000 rw-p b80d7000 00:00 0 b80dd000-b80e rw-p b80dd000 00:00 0 b80e-b80e1000 r-xp b80e 00:00 0 [vdso] b80e1000-b80fd000 r-xp 09:02 1496222/lib/ld-2.9.so b80fd000-b80fe000 r--p 0001b000 09:02 1496222/lib/ld-2.9.so b80fe000-b80ff000 rw-p 0001c000 09:02 1496222/lib/ld-2.9.so bfdea000-bfdff000 rw-p bffeb000 00:00 0 [stack] Aborted I got new source for Version 2.01 from the mpath_prio_hds_modular author. Version 2.01 Changes 2007-11-13: o Source code changes: § Delete #include libdevmapper.h § Deletechar vendor[8] § Add char vendor[9] Compiled it with: # gcc pp_hds_modular.c –o mpath_prio_hds_modular Copy the prioritizer: # cp mpath_prio_hds_modular /sbin Now mpath_prio_hds_modular works correctly: r...@tie-interceptor:/# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 0 However one part of the multipath package seems to be missing from the ubuntu package. multipath normally requires /sbin/scsi_id to exist. Looks like udev puts scsi_id in a strange place, and there is an existing bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481447 for that. So I symlinked the /lib/udev/scsi_id to /sbin/scsi_id However the version of scsi_id that is there does not support the -s flag and fails: r...@tie-interceptor:/sbin# multipath /sbin/scsi_id: invalid option -- 's' error calling out /sbin/scsi_id -g -u -s /block/sda /sbin/scsi_id: invalid option -- 's' It appears that the version of scsi_id that is supplied with ubuntu is a bit different than the version in RH, or SUSE. r...@tie-interceptor:/sbin# /lib/udev/scsi_id --version 141 -- Sent from my mobile device ** Bug watch added: Debian Bug tracker #481447 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481447 -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386619] Re: *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated
** Description changed: Binary package hint: multipath-tools Jaunty server 32-bit. Running mpath_prio_hds_modular against any device causes the *** stack smashing detected *** message to be displayed. r...@tie-interceptor:~# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb8074da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb8074d60] /sbin/mpath_prio_hds_modular[0x8048b92] /sbin/mpath_prio_hds_modular[0x80486b3] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f8d775] /sbin/mpath_prio_hds_modular[0x8048551] === Memory map: 08048000-08049000 r-xp 09:02 1537228/sbin/mpath_prio_hds_modular 08049000-0804a000 r--p 1000 09:02 1537228/sbin/mpath_prio_hds_modular 0804a000-0804b000 rw-p 2000 09:02 1537228/sbin/mpath_prio_hds_modular 09e2c000-09e4d000 rw-p 09e2c000 00:00 0 [heap] b7f63000-b7f7 r-xp 09:02 1496221/lib/libgcc_s.so.1 b7f7-b7f71000 r--p c000 09:02 1496221/lib/libgcc_s.so.1 b7f71000-b7f72000 rw-p d000 09:02 1496221/lib/libgcc_s.so.1 b7f76000-b7f77000 rw-p b7f76000 00:00 0 b7f77000-b80d3000 r-xp 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d3000-b80d4000 ---p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d4000-b80d6000 r--p 0015c000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d6000-b80d7000 rw-p 0015e000 09:02 1496367 /lib/tls/i686/cmov/libc-2.9.so b80d7000-b80da000 rw-p b80d7000 00:00 0 b80dd000-b80e rw-p b80dd000 00:00 0 b80e-b80e1000 r-xp b80e 00:00 0 [vdso] b80e1000-b80fd000 r-xp 09:02 1496222/lib/ld-2.9.so b80fd000-b80fe000 r--p 0001b000 09:02 1496222/lib/ld-2.9.so b80fe000-b80ff000 rw-p 0001c000 09:02 1496222/lib/ld-2.9.so bfdea000-bfdff000 rw-p bffeb000 00:00 0 [stack] Aborted + + + I got new source for Version 2.01 from the mpath_prio_hds_modular author. + Version 2.01 + Changes 2007-11-13: + + o Source code changes: + + § Delete #include libdevmapper.h + + § Deletechar vendor[8] + + § Add char vendor[9] + + Compiled it with: + + # gcc pp_hds_modular.c –o mpath_prio_hds_modular + Copy the prioritizer: + # cp mpath_prio_hds_modular /sbin + + Now mpath_prio_hds_modular works correctly: + + r...@tie-interceptor:/# /sbin/mpath_prio_hds_modular -v /dev/sda + VENDOR: HITACHI + PRODUCT: DF600F + SERIAL: 0x + LDEV:0x0007 + CTRL:2 + PORT:A + CTRL EVEN, LDEV ODD, PRIO 0 + 0 + + However one part of the multipath package seems to be missing from the ubuntu package. + multipath normally requires /sbin/scsi_id to exist. + + Looks like udev puts scsi_id in a strange place, and there is an existing bug + http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481447 for that. + + So I symlinked the /lib/udev/scsi_id to /sbin/scsi_id + + However the version of scsi_id that is there does not support the -s + flag and fails: + + r...@tie-interceptor:/sbin# multipath + /sbin/scsi_id: invalid option -- 's' + error calling out /sbin/scsi_id -g -u -s /block/sda + /sbin/scsi_id: invalid option -- 's' + + It appears that the version of scsi_id that is supplied with ubuntu is a + bit different than the version in RH, or SUSE. + + r...@tie-interceptor:/sbin# /lib/udev/scsi_id --version + 141 -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386619] Re: *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated
So Ive got it working now. Here's what I did. 1. Compile pp_hds_modular.c 2.01 (attached) # gcc pp_hds_modular.c –o mpath_prio_hds_modular Copy the prioritizer: # cp mpath_prio_hds_modular /sbin 2. Copy multipath.conf into /etc (attached) 3. Edit /etc/multipath.conf Change lines (2) that say: getuid_callout /sbin/scsi_id -g -u -s /block/%n To: getuid_callout /lib/udev/scsi_id --whitelisted --device=/dev/%n ** Attachment added: pp_hds_modular 2.01 http://launchpadlibrarian.net/27956301/%5C10.3.20.154%5Cmperino%5Clinux%5Cpp_hds_modular_v2.01.tar -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 386619] [NEW] *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated
Public bug reported: Binary package hint: multipath-tools Jaunty server 32-bit. Running mpath_prio_hds_modular against any device causes the *** stack smashing detected *** message to be displayed. r...@tie-interceptor:~# /sbin/mpath_prio_hds_modular -v /dev/sda VENDOR: HITACHI PRODUCT: DF600F SERIAL: 0x LDEV:0x0007 CTRL:2 PORT:A CTRL EVEN, LDEV ODD, PRIO 0 *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb8074da8] /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb8074d60] /sbin/mpath_prio_hds_modular[0x8048b92] /sbin/mpath_prio_hds_modular[0x80486b3] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7f8d775] /sbin/mpath_prio_hds_modular[0x8048551] === Memory map: 08048000-08049000 r-xp 09:02 1537228/sbin/mpath_prio_hds_modular 08049000-0804a000 r--p 1000 09:02 1537228/sbin/mpath_prio_hds_modular 0804a000-0804b000 rw-p 2000 09:02 1537228/sbin/mpath_prio_hds_modular 09e2c000-09e4d000 rw-p 09e2c000 00:00 0 [heap] b7f63000-b7f7 r-xp 09:02 1496221/lib/libgcc_s.so.1 b7f7-b7f71000 r--p c000 09:02 1496221/lib/libgcc_s.so.1 b7f71000-b7f72000 rw-p d000 09:02 1496221/lib/libgcc_s.so.1 b7f76000-b7f77000 rw-p b7f76000 00:00 0 b7f77000-b80d3000 r-xp 09:02 1496367/lib/tls/i686/cmov/libc-2.9.so b80d3000-b80d4000 ---p 0015c000 09:02 1496367/lib/tls/i686/cmov/libc-2.9.so b80d4000-b80d6000 r--p 0015c000 09:02 1496367/lib/tls/i686/cmov/libc-2.9.so b80d6000-b80d7000 rw-p 0015e000 09:02 1496367/lib/tls/i686/cmov/libc-2.9.so b80d7000-b80da000 rw-p b80d7000 00:00 0 b80dd000-b80e rw-p b80dd000 00:00 0 b80e-b80e1000 r-xp b80e 00:00 0 [vdso] b80e1000-b80fd000 r-xp 09:02 1496222/lib/ld-2.9.so b80fd000-b80fe000 r--p 0001b000 09:02 1496222/lib/ld-2.9.so b80fe000-b80ff000 rw-p 0001c000 09:02 1496222/lib/ld-2.9.so bfdea000-bfdff000 rw-p bffeb000 00:00 0 [stack] Aborted ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- *** stack smashing detected ***: /sbin/mpath_prio_hds_modular terminated https://bugs.launchpad.net/bugs/386619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 292788] Re: [i855] Kubuntu: False Monitor Detection
Hey Bruce.. I can install 9.04 and try again. It'll take a week or so. I still have the laptop but it's stable on good old Hardy kde3. On Tue, Jun 2, 2009 at 10:04 AM, Bryce Harrington br...@bryceharrington.org wrote: Hi kleidokrators, Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/) If it remains an issue, could you also attach a new /var/log/Xorg.0.log? Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] ** Tags added: needs-verification ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Incomplete -- [i855] Kubuntu: False Monitor Detection https://bugs.launchpad.net/bugs/292788 You received this bug notification because you are a direct subscriber of the bug. Status in “xserver-xorg-video-intel” source package in Ubuntu: Incomplete Bug description: After upgrading from Kubuntu 8.04 with KDE4 to 8.10 the system detects that a monitor has been disconnected when there isn't one. A window pops asking me if I wish to run the configuration tool to adjust the monitor setup or to ignore it. My system is an IBM Thinkpad R50e lspci |grep VGA gives 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) There are also some errors in the Xorg.0.log: (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc008 to 0xd009 (WW) intel(0): PP_STATUS before: on, ready, sequencing idle (WW) intel(0): PP_STATUS after: on, ready, sequencing on (WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x8202 to 0x0202 (WW) intel(0): PIPEBSTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS VBLANK_INT_STATUS (WW) intel(0): PIPEBSTAT after: status: VSYNC_INT_STATUS VBLANK_INT_STATUS --- (II) intel(0): Pipe A is off (II) intel(0): Display plane A is now enabled and connected to pipe A. (WW) intel(0): Hardware claims pipe A is on while software believes it is off (WW) intel(0): Hardware claims plane A is on while software believes it is off --- and finally this keeps repeating (EE) intel(0): tried to update DSPARB with both planes enabled! (II) intel(0): I2C device LVDSDDC_C:ddc2 registered at address 0xA0. (II) intel(0): I2C device LVDSDDC_C:ddc2 removed. (EE) intel(0): underrun on pipe B! (EE) intel(0): underrun on pipe B! (EE) intel(0): underrun on pipe B! (EE) intel(0): tried to update DSPARB with both planes enabled! (II) intel(0): I2C device LVDSDDC_C:ddc2 registered at address 0xA0. (II) intel(0): I2C device LVDSDDC_C:ddc2 removed. (EE) intel(0): tried to update DSPARB with both planes enabled! (II) intel(0): I2C device CRTDDC_A:ddc2 registered at address 0xA0. (II) intel(0): I2C device CRTDDC_A:ddc2 removed. -- [i855] Kubuntu: False Monitor Detection https://bugs.launchpad.net/bugs/292788 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292788] Re: False Monitor Detection
So you are also getting the errors: (EE) intel(0): tried to update DSPARB with both planes enabled! (EE) intel(0): underrun on pipe B! I have searched and there are a number of other folks reporting bugs with these same error messages popping up. My patience with an unstable KDE is at an end.. Im downgrading to Hardy later today as I cant deal with the crashes any more. -- False Monitor Detection https://bugs.launchpad.net/bugs/292788 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292788] Re: False Monitor Detection
I have similar problems. Window Manager keeps crashing intermittently dropping me out to the KDE login screen. Occurs most frequently when scrolling in Firefox. Intel Corporation 82852/855GM Integrated Graphics Device in a laptop. Was completley stable running every version of Kubuntu that was installed on it (Feisty, Gutsy, Hardy). Now crashes frequently with Intrepid. Im also experiencing the visual glitch that happens when an app goes full screen. http://forum.kde.org/showthread.php?tid=6511 What are you all seeing in /var/log/kdm.log? Here's what I see: (EE) intel(0): tried to update DSPARB with both planes enabled! (EE) intel(0): Unknown EDID version 0 Backtrace: 0: /usr/bin/X(xf86SigHandler+0x79) [0x80c3009] 1: [0xb7f29400] 2: /usr/lib/xorg/modules/extensions//libglx.so(__glXContextDestroy+0x23) [0xb7a4 81d3] 3: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a55ade] 4: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x89) [0xb7a4a85 9] 5: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a4a8a7] 6: /usr/bin/X(FreeResourceByType+0xe2) [0x8073c72] 7: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a46b77] 8: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a4ac0a] 9: /usr/bin/X(Dispatch+0x34f) [0x808c89f] 10: /usr/bin/X(main+0x47d) [0x8071d1d] 11: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b2c685] 12: /usr/bin/X [0x8071101] Saw signal 11. Server aborting. X.Org X Server 1.5.2 Release Date: 10 October 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-19-server i686 Ubuntu Current Operating System: Linux halfdome 2.6.27-7-generic #1 SMP Tue Nov 4 19:33 :20 UTC 2008 i686 Build Date: 24 October 2008 08:00:16AM xorg-server 2:1.5.2-2ubuntu3 ([EMAIL PROTECTED]) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Nov 28 11:10:29 2008 (==) Using config file: /etc/X11/xorg.conf (EE) intel(0): Unknown EDID version 0 (EE) intel(0): Unknown EDID version 0 (EE) intel(0): underrun on pipe B! Im curious to see if you have similar odd messages in /var/log/kdm.log -- False Monitor Detection https://bugs.launchpad.net/bugs/292788 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
