Bug#1050547: GNOME crashes with white screen after boot up
rc/vm/Interpreter.cpp:3314 #18 0x7fb208195d6d in js::RunScript (cx=cx@entry=0x55724a2f63e0, state=...) at ./js/src/vm/Interpreter.cpp:389 #19 0x7fb2081981e9 in js::ExecuteKernel (result=..., evalInFrame=..., envChainArg=..., script=..., cx=0x55724a2f63e0) at ./js/src/vm/Interpreter.cpp:781 #20 js::Execute (cx=0x55724a2f63e0, script=script@entry=..., envChain=envChain@entry=..., rval=...) at ./js/src/vm/Interpreter.cpp:813 #21 0x7fb2081f2148 in js::ModuleObject::execute (cx=, self=self@entry=..., rval=...) at ./js/src/builtin/ModuleObject.cpp:1249 #22 0x7fb2083631e4 in intrinsic_ExecuteModule (cx=, argc=, vp=) at ./js/src/vm/SelfHosting.cpp:1891 #23 0x2b78f24f94e0 in ?? () #24 0x2b78f24f55e8 in ?? () #25 0x7ffc13ebdbd0 in ?? () #26 0x00000000 in ?? () Regards, Hor Jiun Shyong 何俊雄 Hor Jiun Shyong 于2023年9月11日周一 08:22写道： > Hi, > > >>DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb > Partial output as below and full output as per link. Thanks. > > > https://drive.google.com/file/d/19pahjyQSf_PRw-zQDwtC9FWRPcGQvUfo/view?usp=sharing > > > # DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb >PID: 1720 (gnome-shell) >UID: 117 (Debian-gdm) >GID: 122 (Debian-gdm) > Signal: 11 (SEGV) > Timestamp: Sat 2023-09-09 19:13:27 +08 (1 day 12h ago) > Command Line: /usr/bin/gnome-shell > Executable: /usr/bin/gnome-shell > Control Group: /user.slice/user-117.slice/session-c1.scope > Unit: session-c1.scope > Slice: user-117.slice >Session: c1 > Owner UID: 117 (Debian-gdm) >Boot ID: db5045b3be454eabaf40ab7634cdd15f > Machine ID: e2ff68e6a046472b82838d16f35a6e1f > Hostname: meixian >Storage: > /var/lib/systemd/coredump/core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.169425800700.zst > (present) > Size on Disk: 6.4M >Message: Process 1720 (gnome-shell) of user 117 dumped core. > > Module libudev.so.1 from deb systemd-254.1-2.amd64 > Module libsystemd.so.0 from deb systemd-254.1-2.amd64 > Stack trace of thread 1720: > #0 0x7f9e956ced54 meta_display_get_x11_display > (libmutter-12.so.0 + 0xced54) > #1 0x7f9e956f9a3b n/a (libmutter-12.so.0 + 0xf9a3b) > #2 0x7f9e95e95f8f g_initable_new_valist > (libgio-2.0.so.0 + 0x7df8f) > #3 0x7f9e95e96069 g_initable_new (libgio-2.0.so.0 + > 0x7e069) > #4 0x7f9e956f9dda n/a (libmutter-12.so.0 + 0xf9dda) > #5 0x7f9e956fd5ce n/a (libmutter-12.so.0 + 0xfd5ce) > #6 0x7f9e956fd62d n/a (libmutter-12.so.0 + 0xfd62d) > #7 0x7f9e9568b04e meta_cursor_tracker_get_sprite > (libmutter-12.so.0 + 0x8b04e) > #8 0x7f9e94d4cf7a n/a (libffi.so.8 + 0x6f7a) > #9 0x7f9e94d4c40e n/a (libffi.so.8 + 0x640e) > #10 0x7f9e94d4cb0d ffi_call (libffi.so.8 + 0x6b0d) > > > Regards, > Hor Jiun Shyong 何俊雄 > > > > Simon McVittie 于2023年9月11日周一 01:40写道： > >> On Sat, 09 Sep 2023 at 12:40:53 +0800, Hor Jiun Shyong wrote: >> > coredumpctl_gdb.txt.gz >> >> The relevant part is: >> >> #0 0x7f9e956ced54 in meta_display_get_x11_display () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #1 0x7f9e956f9a3b in ?? () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #2 0x7f9e95e95f8f in g_initable_new_valist () from >> /lib/x86_64-linux-gnu/libgio-2.0.so.0 >> #3 0x7f9e95e96069 in g_initable_new () from >> /lib/x86_64-linux-gnu/libgio-2.0.so.0 >> #4 0x7f9e956f9dda in ?? () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #5 0x7f9e956fd5ce in ?? () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #6 0x7f9e956fd62d in ?? () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #7 0x7f9e9568b04e in meta_cursor_tracker_get_sprite () from >> /lib/x86_64-linux-gnu/libmutter-12.so.0 >> #8 0x7f9e94d4cf7a in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 >> >> but this is of limited usefulness since you don't have debug symbols for >> mutter available. >> >> The easiest way to get the debug symbols is to use: >> >> DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb >> >> and type "bt" at the (gdb) prompt when the symbols have finished >> downloading. >> >> Or you could enable the debug symbols apt repository (see >> >> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols >> ) >>
Bug#1050547:
Hi, on 17 Sep, I have reinstall gnome-shell. An additional new package package was installed too: policykit-1-gnome:amd64 (0.105-8, automatic) The issue was resolved and GNOME gdm3 is able to start successfully. Below are the packages involved. Thanks. Start-Date: 2023-09-17 12:17:15 Commandline: apt-get remove gnome-shell -V Install: policykit-1-gnome:amd64 (0.105-8, automatic) Remove: gnome-shell-extensions:amd64 (44.0-2), gnome-shell:amd64 (44.4-1), gdm3:amd64 (45~beta-1), chrome-gnome-shell:amd64 (42.1-4), gnome-session:amd64 (44.0-4), gnome-browser-connector:amd64 (42.1-4), gnome-shell-extension-prefs:amd64 (44.4-1) End-Date: 2023-09-17 12:17:21 Start-Date: 2023-09-17 12:17:44 Commandline: apt-get install gnome-shell -V Install: gnome-shell:amd64 (44.4-1), gdm3:amd64 (45~beta-1, automatic), chrome-gnome-shell:amd64 (42.1-4, automatic), gnome-session:amd64 (44.0-4, automatic), gnome-browser-connector:amd64 (42.1-4, automatic), gnome-shell-extension-prefs:amd64 (44.4-1, automatic) End-Date: 2023-09-17 12:17:53 Regards, Hor Jiun Shyong 何俊雄 +60-16-2089567
Bug#1050547: GNOME crashes with white screen after boot up
Hi, >>DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb Partial output as below and full output as per link. Thanks. https://drive.google.com/file/d/19pahjyQSf_PRw-zQDwtC9FWRPcGQvUfo/view?usp=sharing # DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb PID: 1720 (gnome-shell) UID: 117 (Debian-gdm) GID: 122 (Debian-gdm) Signal: 11 (SEGV) Timestamp: Sat 2023-09-09 19:13:27 +08 (1 day 12h ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-117.slice/session-c1.scope Unit: session-c1.scope Slice: user-117.slice Session: c1 Owner UID: 117 (Debian-gdm) Boot ID: db5045b3be454eabaf40ab7634cdd15f Machine ID: e2ff68e6a046472b82838d16f35a6e1f Hostname: meixian Storage: /var/lib/systemd/coredump/core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.169425800700.zst (present) Size on Disk: 6.4M Message: Process 1720 (gnome-shell) of user 117 dumped core. Module libudev.so.1 from deb systemd-254.1-2.amd64 Module libsystemd.so.0 from deb systemd-254.1-2.amd64 Stack trace of thread 1720: #0 0x7f9e956ced54 meta_display_get_x11_display (libmutter-12.so.0 + 0xced54) #1 0x7f9e956f9a3b n/a (libmutter-12.so.0 + 0xf9a3b) #2 0x7f9e95e95f8f g_initable_new_valist (libgio-2.0.so.0 + 0x7df8f) #3 0x7f9e95e96069 g_initable_new (libgio-2.0.so.0 + 0x7e069) #4 0x7f9e956f9dda n/a (libmutter-12.so.0 + 0xf9dda) #5 0x7f9e956fd5ce n/a (libmutter-12.so.0 + 0xfd5ce) #6 0x7f9e956fd62d n/a (libmutter-12.so.0 + 0xfd62d) #7 0x7f9e9568b04e meta_cursor_tracker_get_sprite (libmutter-12.so.0 + 0x8b04e) #8 0x7f9e94d4cf7a n/a (libffi.so.8 + 0x6f7a) #9 0x7f9e94d4c40e n/a (libffi.so.8 + 0x640e) #10 0x7f9e94d4cb0d ffi_call (libffi.so.8 + 0x6b0d) Regards, Hor Jiun Shyong 何俊雄 Simon McVittie 于2023年9月11日周一 01:40写道： > On Sat, 09 Sep 2023 at 12:40:53 +0800, Hor Jiun Shyong wrote: > > coredumpctl_gdb.txt.gz > > The relevant part is: > > #0 0x7f9e956ced54 in meta_display_get_x11_display () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #1 0x7f9e956f9a3b in ?? () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #2 0x7f9e95e95f8f in g_initable_new_valist () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > #3 0x7f9e95e96069 in g_initable_new () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > #4 0x7f9e956f9dda in ?? () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #5 0x7f9e956fd5ce in ?? () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #6 0x7f9e956fd62d in ?? () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #7 0x7f9e9568b04e in meta_cursor_tracker_get_sprite () from > /lib/x86_64-linux-gnu/libmutter-12.so.0 > #8 0x7f9e94d4cf7a in ?? () from /lib/x86_64-linux-gnu/libffi.so.8 > > but this is of limited usefulness since you don't have debug symbols for > mutter available. > > The easiest way to get the debug symbols is to use: > > DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl gdb > > and type "bt" at the (gdb) prompt when the symbols have finished > downloading. > > Or you could enable the debug symbols apt repository (see > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols > ) > and install the libmutter-12-0-dbgsym package. We don't need any other > packages for this particular crash. > > > > core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.169425800700.zst.gz > > In general we can't get a useful backtrace from the actual compressed > core dump: that's something that the bug reporter needs to do. I tried to > get a useful backtrace from this with debug symbols, but it doesn't match > the result you sent and I'm not sure whether it really makes sense. > > Sharing these core dumps is also a privacy risk because they can contain > private information, although in this case the crash was from the gdm > login screen before you had a chance to enter any passwords, so it's > probably harmless. > > smcv >
Bug#1050547: GNOME crashes with white screen after boot up
Hi, I have submitted reportbug on this same case: 1050547. Below are the backtrace via systemd-coredump and gdb output. Thanks. coredumpctl_gdb.txt.gz https://drive.google.com/file/d/13g8x6hAvkBznODK1y96Epewk_QLUxDB3/view?usp=sharing core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.169425800700.zst.gz https://drive.google.com/file/d/1DreFJWmMfV34cbiad5Dp5d6XslVS1zqm/view?usp=sharing Regards, Hor Jiun Shyong 何俊雄 Hor Jiun Shyong 于2023年9月7日周四 18:21写道： > >>With the proprietary Nvidia driver, or with Mesa's open source Nouveau > driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be > significant. > Desktop PC uses below proprietary Nvidia driver. > > # apt-cache show nvidia-driver > Package: nvidia-driver > Source: nvidia-graphics-drivers > Version: 525.125.06-2 > Installed-Size: 1373 > Maintainer: Debian NVIDIA Maintainers < > pkg-nvidia-de...@lists.alioth.debian.org> > Architecture: amd64 > Provides: nvidia-driver-any, nvidia-glx-any > Depends: nvidia-driver-libs (= 525.125.06-2), nvidia-driver-bin (= > 525.125.06-2), xserver-xorg-video-nvidia (= 525.125.06-2), > nvidia-vdpau-driver (= 525.125.06-2), nvidia-alternative (= 525.125.06-2), > nvidia-kernel-dkms (= 525.125.06-2) | nvidia-kernel-525.125.06 | > nvidia-open-kernel-525.125.06 | nvidia-open-kernel-525.125.06, > nvidia-support > Pre-Depends: nvidia-installer-cleanup, nvidia-legacy-check (>= 495) > Recommends: nvidia-settings (>= 525), libnvidia-cfg1 (= 525.125.06-2), > nvidia-persistenced > Suggests: nvidia-kernel-dkms (>= 525.125.06) | nvidia-kernel-source (>= > 525.125.06) | nvidia-open-kernel-source (>= 525.125.06) | > nvidia-open-kernel-source (>= 525.125.06) > Description-en: NVIDIA metapackage > This metapackage depends on the NVIDIA binary driver and libraries that > provide optimized hardware acceleration of OpenGL/GLX/EGL/GLES/Vulkan > applications via a direct-rendering X Server. > > > Regards, > Hor Jiun Shyong 何俊雄 > > > > > Simon McVittie 于2023年9月7日周四 17:16写道： > >> On Thu, 07 Sep 2023 at 16:46:34 +0800, Hor Jiun Shyong wrote: >> > This issue occurred on my home desktop running with Nvidia GPU. >> >> With the proprietary Nvidia driver, or with Mesa's open source Nouveau >> driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be >> significant. >> >> > while using my laptop with AMD Ryzen Pro 7 (with integrated Radeon >> > Graphics), GNOME just crashed with the same white screen. However >> Debian >> > managed to restart the GNOME session successfully. >> >> It would probably be a good idea to install systemd-coredump on the laptop >> too, so that if this crash happens again, the crash dump will be collected >> for later investigation. >> >> If the crash doesn't happen again, no further action is needed, but if >> it happens on the AMD laptop again: >> >> * If the backtrace obtained via systemd-coredump looks the same as for the >> Nvidia desktop, we can use the same bug report for it. >> >> * But if the backtrace seems significantly different, please report a >> separate bug for it. Merging bugs if they turn out to be the same is >> easy, but keeping track of two different bugs on the same bug number >> gets really confusing, so we should avoid doing that. >> >> Thanks, >> smcv >> >
Bug#1050547: GNOME crashes with white screen after boot up
>>With the proprietary Nvidia driver, or with Mesa's open source Nouveau driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be significant. Desktop PC uses below proprietary Nvidia driver. # apt-cache show nvidia-driver Package: nvidia-driver Source: nvidia-graphics-drivers Version: 525.125.06-2 Installed-Size: 1373 Maintainer: Debian NVIDIA Maintainers < pkg-nvidia-de...@lists.alioth.debian.org> Architecture: amd64 Provides: nvidia-driver-any, nvidia-glx-any Depends: nvidia-driver-libs (= 525.125.06-2), nvidia-driver-bin (= 525.125.06-2), xserver-xorg-video-nvidia (= 525.125.06-2), nvidia-vdpau-driver (= 525.125.06-2), nvidia-alternative (= 525.125.06-2), nvidia-kernel-dkms (= 525.125.06-2) | nvidia-kernel-525.125.06 | nvidia-open-kernel-525.125.06 | nvidia-open-kernel-525.125.06, nvidia-support Pre-Depends: nvidia-installer-cleanup, nvidia-legacy-check (>= 495) Recommends: nvidia-settings (>= 525), libnvidia-cfg1 (= 525.125.06-2), nvidia-persistenced Suggests: nvidia-kernel-dkms (>= 525.125.06) | nvidia-kernel-source (>= 525.125.06) | nvidia-open-kernel-source (>= 525.125.06) | nvidia-open-kernel-source (>= 525.125.06) Description-en: NVIDIA metapackage This metapackage depends on the NVIDIA binary driver and libraries that provide optimized hardware acceleration of OpenGL/GLX/EGL/GLES/Vulkan applications via a direct-rendering X Server. Regards, Hor Jiun Shyong 何俊雄 Simon McVittie 于2023年9月7日周四 17:16写道： > On Thu, 07 Sep 2023 at 16:46:34 +0800, Hor Jiun Shyong wrote: > > This issue occurred on my home desktop running with Nvidia GPU. > > With the proprietary Nvidia driver, or with Mesa's open source Nouveau > driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be > significant. > > > while using my laptop with AMD Ryzen Pro 7 (with integrated Radeon > > Graphics), GNOME just crashed with the same white screen. However Debian > > managed to restart the GNOME session successfully. > > It would probably be a good idea to install systemd-coredump on the laptop > too, so that if this crash happens again, the crash dump will be collected > for later investigation. > > If the crash doesn't happen again, no further action is needed, but if > it happens on the AMD laptop again: > > * If the backtrace obtained via systemd-coredump looks the same as for the > Nvidia desktop, we can use the same bug report for it. > > * But if the backtrace seems significantly different, please report a > separate bug for it. Merging bugs if they turn out to be the same is > easy, but keeping track of two different bugs on the same bug number > gets really confusing, so we should avoid doing that. > > Thanks, > smcv >
Bug#1050547: GNOME crashes with white screen after boot up
__x64_sys_pread64+0x98/0xd0 [29274.323552] do_syscall_64+0x60/0xc0 [29274.323559] entry_SYSCALL_64_after_hwframe+0x77/0xe1 [29274.323566] RIP: 0033:0x7f2467234b97 [29274.323571] Code: 08 89 3c 24 48 89 4c 24 18 e8 e5 ee f8 ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 04 24 e8 35 ef f8 ff 48 8b [29274.323575] RSP: 002b:7fff4b789560 EFLAGS: 0293 ORIG_RAX: 0011 [29274.323581] RAX: ffda RBX: 1000 RCX: 7f2467234b97 [29274.323585] RDX: 1000 RSI: 7fff4b789970 RDI: 0007 [29274.323588] RBP: 7fff4b789770 R08: R09: 3590004735a0 [29274.323591] R10: 00007f679c155880 R11: 0293 R12: 7fff4b789970 [29274.323595] R13: 359000474680 R14: 7f679c155880 R15: 1000 [29274.323605] [29274.323608] ---[ end trace ]--- Regards, Hor Jiun Shyong 何俊雄 Simon McVittie 于2023年9月7日周四 16:18写道： > Control: tags -1 + moreinfo > > On Sat, 26 Aug 2023 at 10:38:45 +0800, Hor Jiun Shyong wrote: > > /var/log/kern.log showing gnome-shell segfault > > 2023-08-26T18:00:40.251595+08:00 meixian kernel: [ 19.540303] > gnome-shell > > [1746]: segfault at 18 ip 7f3bc8acc1c0 sp 7ffc8bc20798 error 4 in > > libmutter-12.so.0.0.0[7f3bc8a4e000+15000 0] likely on CPU 2 (core 1, > socket 0) > > 2023-08-26T18:00:40.251597+08:00 meixian kernel: [ 19.540329] Code: > 1f 00 > > 48 89 c7 e8 a0 6f f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 > 5c c6 > > f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 <48> 8b 47 18 c3 66 66 2e 0f > 1f 84 > > 00 00 00 00 00 55 48 89 f5 53 48 > > This information is not enough to diagnose a root cause. Please could you > get a backtrace for the crash? Usually the easiest way to achieve this is > to use systemd-coredump: see > <https://wiki.debian.org/HowToGetABacktrace#Core_dump> and > <https://wiki.debian.org/HowToGetABacktrace#Running_gdb>. > > It is helpful if you can use the reportbug tool to report bugs: that would > provide information on all the packages that gnome-shell depends on. > > Thanks, > smcv >
Bug#1050547:
Hi, After updating Debian today with below packages, Gnome still starts with white screen. Error as below. Thanks. gnome-shell:amd64 (44.3-5, 44.4-1), mutter:amd64 (44.3-7, 44.4-2) linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1), Start-Date: 2023-09-07 12:17:22 Commandline: apt-get dist-upgrade -V Install: linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-kbuild-6.4.0-4:amd64 (6.4.13-1, automatic), linux-headers-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-headers-6.4. 0-4-common:amd64 (6.4.13-1, automatic) Upgrade: libnghttp2-14:amd64 (1.55.1-1, 1.56.0-1), python3-brlapi:amd64 (6.6-2, 6.6-4), mutter-common-bin:amd64 (44.3-7, 44.4-2), xbrlapi:amd64 (6.6-2, 6.6-4), libldb2:amd64 (2:2.7.2+samba4 .18.6+dfsg-1, 2:2.8.0+samba4.19.0+dfsg-1), libbrlapi0.8:amd64 (6.6-2, 6.6-4), libmutter-12-0:amd64 (44.3-7, 44.4-2), virtinst:amd64 (1:4.1.0-2, 1:4.1.0-3), linux-compiler-gcc-13-x86:amd64 ( 6.4.11-1, 6.4.13-1), libwbclient0:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), linux-headers-amd64:amd64 (6.4.11-1, 6.4.13-1), libsmbclient:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), mutter-com mon:amd64 (44.3-7, 44.4-2), gnome-shell:amd64 (44.3-5, 44.4-1), linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1), libnet-http-perl:amd64 (6.22-1, 6.23-1), gir1.2-mutter-12:amd64 (44.3-7, 44.4-2 ), gnome-shell-common:amd64 (44.3-5, 44.4-1), libmozjs-102-0:amd64 (102.14.0-1, 102.15.0-1), mutter:amd64 (44.3-7, 44.4-2), python3-ldb:amd64 (2:2.7.2+samba4.18.6+dfsg-1, 2:2.8.0+samba4.19. 0+dfsg-1), libsdl2-2.0-0:amd64 (2.28.2+dfsg-1, 2.28.3+dfsg-1), samba-libs:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), virt-viewer:amd64 (11.0-2, 11.0-3), gnome-shell-extension-prefs:amd64 (44 .3-5, 44.4-1), linux-libc-dev:amd64 (6.4.11-1, 6.4.13-1) End-Date: 2023-09-07 12:19:30 17.787657] gnome-shell[1684]: segfault at 18 ip 7f62cfcced54 sp 7ffcfcdeff98 error 4 in libmutter-12.so.0.0.0[7f62cfc4e000+156000] likely on CPU 2 (core 1, socket 0) [ 17.787670] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48 [ 18.415736] gnome-shell[1715]: segfault at 18 ip 7f9f416ced54 sp 7ffc3a4e58a8 error 4 in libmutter-12.so.0.0.0[7f9f4164e000+156000] likely on CPU 4 (core 2, socket 0) [ 18.415750] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48 Regards, Hor Jiun Shyong 何俊雄
Bug#1050547:
Linux simayi 6.4.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.11-1 (2023-08-17) x86_64 GNU/Linux Debian GNU/Linux trixie/sid GNOME 44.3 GDM 44.1
Bug#1050547: GNOME crashes with white screen after boot up
Package: gnome-shell Version: 44.3-5 After Debian boot up, GNOME crashes with white screen.I am unable to access terminal console screens via Alt+F1 to F6 (showing cursor blinking). I am only able to access the node after SSH from another node. /var/log/kern.log showing gnome-shell segfault 2023-08-26T18:00:40.251595+08:00 meixian kernel: [ 19.540303] gnome-shell[1746]: segfault at 18 ip 7f3bc8acc1c0 sp 7ffc8bc20798 error 4 in libmutter-12.so.0.0.0[7f3bc8a4e000+15000 0] likely on CPU 2 (core 1, socket 0) 2023-08-26T18:00:40.251597+08:00 meixian kernel: [ 19.540329] Code: 1f 00 48 89 c7 e8 a0 6f f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 5c c6 f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 <48> 8b 47 18 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 f5 53 48 2023-08-26T18:00:40.795605+08:00 meixian kernel: [ 20.085797] gnome-shell[1783]: segfault at 18 ip 7f059f6cc1c0 sp 7fffbe59e5b8 error 4 in libmutter-12.so.0.0.0[7f059f64e000+15000 0] likely on CPU 1 (core 0, socket 0) 2023-08-26T18:00:40.795620+08:00 meixian kernel: [ 20.085812] Code: 1f 00 48 89 c7 e8 a0 6f f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 5c c6 f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 <48> 8b 47 18 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 f5 53 48 Recently I have upgraded the below packages. Start-Date: 2023-08-24 20:13:45 Commandline: apt-get dist-upgrade -V Install: linux-headers-6.4.0-3-common:amd64 (6.4.11-1, automatic), linux-kbuild-6.4.0-3:amd64 (6.4.11-1, automatic), linux-image-6.4.0-3-amd64:amd64 (6.4.11-1, automatic), linux-headers-6.4 .0-3-amd64:amd64 (6.4.11-1, automatic) Upgrade: libimath-3-1-29:amd64 (3.1.6-1, 3.1.9-2), fonts-noto-unhinted:amd64 (20201225-1, 20201225-2), libpipewire-0.3-common:amd64 (0.3.77-1, 0.3.78-1), pipewire-pulse:amd64 (0.3.77-1, 0.3 .78-1), libminizip1:amd64 (1.1-8+b1, 1:1.2.13.dfsg-3), linux-compiler-gcc-13-x86:amd64 (6.4.4-3, 6.4.11-1), linux-headers-amd64:amd64 (6.4.4-3, 6.4.11-1), pipewire:amd64 (0.3.77-1, 0.3.78-1 ), python3-zeroconf:amd64 (0.74.0-2, 0.80.0-1), zlib1g-dev:amd64 (1:1.2.13.dfsg-1, 1:1.2.13.dfsg-3), fonts-noto-mono:amd64 (20201225-1, 20201225-2), linux-image-amd64:amd64 (6.4.4-3, 6.4.11 -1), libspa-0.2-bluetooth:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-core:amd64 (20201225-1, 20201225-2), gstreamer1.0-pipewire:amd64 (0.3.77-1, 0.3.78-1), pipewire-audio:amd64 (0.3.77-1, 0.3.7 8-1), pipewire-bin:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-ui-extra:amd64 (20201225-1, 20201225-2), chrome-gnome-shell:amd64 (42.1-3, 42.1-4), fonts-noto:amd64 (20201225-1, 20201225-2), font s-noto-extra:amd64 (20201225-1, 20201225-2), libspa-0.2-modules:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-ui-core:amd64 (20201225-1, 20201225-2), gnome-browser-connector:amd64 (42.1-3, 42.1-4) , libpipewire-0.3-modules:amd64 (0.3.77-1, 0.3.78-1), zlib1g:amd64 (1:1.2.13.dfsg-1, 1:1.2.13.dfsg-3), pipewire-alsa:amd64 (0.3.77-1, 0.3.78-1), linux-libc-dev:amd64 (6.4.4-3, 6.4.11-1), li bpipewire-0.3-0:amd64 (0.3.77-1, 0.3.78-1) End-Date: 2023-08-24 20:16:08 Start-Date: 2023-08-25 12:02:59 Commandline: apt-get dist-upgrade -V Install: mutter-common-bin:amd64 (44.3-7, automatic), libmutter-12-0:amd64 (44.3-7, automatic), gir1.2-mutter-12:amd64 (44.3-7, automatic), gir1.2-gnomebg-4.0:amd64 (44.0-2, automatic), gir 1.2-nma4-1.0:amd64 (1.10.6-1, automatic) Upgrade: fontconfig:amd64 (2.14.2-3, 2.14.2-4), easy-rsa:amd64 (3.1.5-1, 3.1.6-1), wpasupplicant:amd64 (2:2.10-12, 2:2.10-14), libpango-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), libfwupd2:am d64 (1.9.3-1, 1.9.4-2), gnome-remote-desktop:amd64 (43.4-2, 44.2-6), mutter-common:amd64 (43.6-1, 44.3-7), gnome-shell-extensions:amd64 (43.1-1, 44.0-2), gnome-shell:amd64 (43.7-1, 44.3-5), libfontconfig1:amd64 (2.14.2-3, 2.14.2-4), fontconfig-config:amd64 (2.14.2-3, 2.14.2-4), gir1.2-nm-1.0:amd64 (1.42.8-1, 1.44.0-1), libpangocairo-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gr ep:amd64 (3.11-2, 3.11-3), python3-async-timeout:amd64 (4.0.2-1, 4.0.3-1), network-manager:amd64 (1.42.8-1, 1.44.0-1), libpangoft2-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gnome-shell-commo n:amd64 (43.7-1, 44.3-5), mutter:amd64 (43.6-1, 44.3-7), gir1.2-pango-1.0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), libpangoxft-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gnome-shell-extension-prefs :amd64 (43.7-1, 44.3-5), libnm0:amd64 (1.42.8-1, 1.44.0-1), fwupd:amd64 (1.9.3-1, 1.9.4-2) End-Date: 2023-08-25 12:03:32 Thanks. Regards, Hor Jiun Shyong 何俊雄 +60-16-2089567
Bug#993280: wpa_supplicant: EAPOL: Supplicant port status: Unauthorized
Package: wpa_supplicant Version: 2.9.0-21 wpa_supplicant -iwlx503eaaa688e4 -c/etc/wpa -dd -Dnl80211 ... wlx503eaaa688e4: WPS: UUID based on MAC address: dd4dc2bd-f55e-5989-94db-b911fe0980b0 ENGINE: Loading builtin engines ENGINE: Loading builtin engines EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized nl80211: Skip set_supp_port(unauthorized) while not associated EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED ... I have tested on 2 different laptops (builtin wifi) and also with an USB wifi adapter. All produce the same result: "EAPOL: Supplicant port status: Unauthorized". I am using Debian GNU/Linux testing/bookworm, kernel 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux and libc6 2.31-17 Regards, Hor Jiun Shyong 何俊雄
Bug#975284: calibre: crashes on start
Subject: calibre: crashes on start Package: calibre Version: 5.5.0+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? After upgrading to version 5.5.0+dfsg-1, calibre crashes on start. Error logs: $calibre Traceback (most recent call last): File "/usr/bin/calibre", line 20, in sys.exit(calibre()) File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre main(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 509, in main app, opts, args = init_qt(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 122, in init_qt app = Application(args, override_program_name=override, windows_app_uid=MAIN_APP_UID) File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__ from calibre_extensions import progress_indicator ImportError: /usr/lib/calibre/calibre/plugins/progress_indicator.so: undefined symbol: _Py_FatalErrorFunc *** End of the template -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calibre depends on: ii calibre-bin 5.5.0+dfsg-1+b1 ii dpkg 1.20.5 ii fonts-liberation 1:1.07.4-11 ii imagemagick 8:6.9.11.24+dfsg-1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.24+dfsg-1+b2 ii libjpeg-turbo-progs 1:2.0.5-1.1 ii libjxr-tools 1.1-6+b1 ii optipng 0.7.7-1+b1 ii poppler-utils20.09.0-3 ii python3 3.8.6-1 ii python3-apsw 3.32.2-r1-1+b1 ii python3-bs4 4.9.3-1 ii python3-chardet 3.0.4-7 ii python3-chm 0.8.6-2+b2 ii python3-css-parser 1.0.4-2 ii python3-cssselect1.1.0+ds-1 ii python3-cssutils 1.0.2-3 ii python3-dateutil 2.8.1-4 ii python3-dbus 1.2.16-4 ii python3-feedparser 5.2.1-3 ii python3-html2text2020.1.16-1 ii python3-html5-parser 0.4.9-3+b2 ii python3-html5lib 1.1-2 ii python3-lxml 4.6.1-1 ii python3-markdown 3.3.3-1 ii python3-mechanize1:0.4.5-2 ii python3-msgpack 0.6.2-1+b1 ii python3-netifaces0.10.9-0.2+b2 ii python3-pil 8.0.1-1 ii python3-pkg-resources50.3.0-1 ii python3-pygments 2.3.1+dfsg-4 ii python3-pyparsing2.4.7-1 ii python3-pyqt55.15.1+dfsg-2+b2 ii python3-pyqt5.qtsvg 5.15.1+dfsg-2+b2 ii python3-pyqt5.qtwebengine5.15.1-1+b1 ii python3-regex0.1.20200714-1+b1 ii python3-routes 2.4.1-2 ii python3-zeroconf 0.26.1-1 ii xdg-utils1.1.3-2 Versions of packages calibre recommends: ii python3-dnspython 2.0.0-1 ii udisks22.9.1-2 Versions of packages calibre suggests: pn python3-openssl pn python3-unrardll -- no debconf information
Bug#667459: Update
Yups I had done the same by downgrading and setting then in hold. Jiun Shyong 在 2012-11-9 下午4:15，Meike Reichle me...@debian.org写道： Hi I am using a standard Debian kernel (linux-image-3.2.0-4-686-pae) but apparently no KMS, I suppose my graphics card (Mobility Radeon HD 3200) does not support it. I also ran into this bug on my last upgrade. I could solve it by manually downgrading xorg and some related packages using http://snapshot.debian.org/ Here's are the packages and versions that I used: xserver-xorg-core 1.11.4-1 xserver-xorg-input-evdev2.6.0-3+b1 xserver-xorg-input-synaptics1.5.0-2 xserver-xorg-video-ati 6.14.3-2 xserver-xorg-video-mach64 6.9.0-1+b1 xserver-xorg-video-r128 6.8.0-2 xserver-xorg-video-radeon 6.14.3-2 (xserver-xorg-video-radeon might be enough, if you use a xorg.conf-snipplet and not the auto detection.) After downgrading the packages should, for now, be set on hold. Kind regards, Meike
Bug#682922: xserver-xorg-video-radeon: Linux kernel 3.5 compiled with kms support but drm report modesetting isn't supported. GPU only supported with KMS, using vesa instead.
Update: issue is resolved with adding of radeon into /etc/modules. Able to get 1920x1080 full resolution. 55.735] (II) [KMS] Kernel modesetting enabled. [ 55.735] (WW) Falling back to old probe method for fbdev [ 55.735] (II) Loading sub module fbdevhw [ 55.735] (II) LoadModule: fbdevhw [ 55.736] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 55.762] (II) Module fbdevhw: vendor=X.Org Foundation [ 55.762] compiled for 1.12.3, module version = 0.0.2 [ 55.762] ABI class: X.Org Video Driver, version 12.0 [ 55.762] (WW) Falling back to old probe method for vesa [ 55.762] (**) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 55.762] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 55.762] (==) RADEON(0): Default visual is TrueColor [ 55.762] (==) RADEON(0): RGB weight 888 [ 55.762] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 55.762] (--) RADEON(0): Chipset: SUMO (ChipID = 0x964a) [ 55.762] (II) RADEON(0): PCIE card detected -- Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682922: xserver-xorg-video-radeon: Linux kernel 3.5 compiled with kms support but drm report modesetting isn't supported. GPU only supported with KMS, using vesa instead.
Additional information: When modprobe radeon is run, dmesg output is as below. However Vt1 to VT 6 gets blinking cursor and the original VT7 still remains in vesa mode with low resolution 1280x1024. [ 2056.963981] [drm] Initialized drm 1.1.0 20060810 [ 2057.046762] [drm] radeon kernel modesetting enabled. [ 2057.047698] [drm] initializing kernel modesetting (SUMO 0x1002:0x964A 0x1043:0x84C8). [ 2057.047835] [drm] register mmio base: 0xFEB0 [ 2057.047839] [drm] register mmio size: 262144 [ 2057.048179] ATOM BIOS: General [ 2057.048232] radeon :00:01.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [ 2057.048240] radeon :00:01.0: GTT: 512M 0x4000 - 0x5FFF [ 2057.050145] [drm] Detected VRAM RAM=1024M, BAR=256M [ 2057.050153] [drm] RAM width 32bits DDR [ 2057.050414] [TTM] Zone kernel: Available graphics memory: 3572102 kiB [ 2057.050417] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 2057.050418] [TTM] Initializing pool allocator [ 2057.050429] [TTM] Initializing DMA pool allocator [ 2057.050462] [drm] radeon: 1024M of VRAM memory ready [ 2057.050464] [drm] radeon: 512M of GTT memory ready. [ 2057.050485] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 2057.050486] [drm] Driver supports precise vblank timestamp query. [ 2057.050525] radeon :00:01.0: irq 50 for MSI/MSI-X [ 2057.050535] radeon :00:01.0: radeon: using MSI. [ 2057.050567] [drm] radeon: irq initialized. [ 2057.050572] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 2057.051384] [drm] Loading SUMO Microcode [ 2057.182682] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 2057.182886] radeon :00:01.0: WB enabled [ 2057.182896] radeon :00:01.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x8801d03c4c00 [ 2057.200105] [drm] ring test on 0 succeeded in 1 usecs [ 2057.200600] [drm] ib test on ring 0 succeeded in 0 usecs [ 2057.201578] [drm] Radeon Display Connectors [ 2057.201580] [drm] Connector 0: [ 2057.201581] [drm] VGA-1 [ 2057.201582] [drm] HPD2 [ 2057.201583] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [ 2057.201584] [drm] Encoders: [ 2057.201585] [drm] CRT1: INTERNAL_UNIPHY2 [ 2057.201586] [drm] CRT1: NUTMEG [ 2057.201587] [drm] Connector 1: [ 2057.201588] [drm] HDMI-A-1 [ 2057.201589] [drm] HPD1 [ 2057.201590] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [ 2057.201591] [drm] Encoders: [ 2057.201592] [drm] DFP1: INTERNAL_UNIPHY2 [ 2057.218668] [drm] Internal thermal controller without fan control [ 2057.218708] [drm] radeon: power management initialized [ 2057.350198] [drm] fb mappable at 0xC0142000 [ 2057.350201] [drm] vram apper at 0xC000 [ 2057.350202] [drm] size 8294400 [ 2057.350203] [drm] fb depth is 24 [ 2057.350204] [drm]pitch is 7680 [ 2057.350411] fbcon: radeondrmfb (fb0) is primary device [ 2057.350641] Console: switching to colour frame buffer device 240x67 [ 2057.350647] fb0: radeondrmfb frame buffer device [ 2057.350648] drm: registered panic notifier [ 2057.350656] [drm] Initialized radeon 2.17.0 20080528 for :00:01.0 on minor 0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681742: fglrx-driver: Eclipse Android Development Tool (ADT) Android Device Manager (ADM)'s emulator platform crashed when started. Error log as below:
On 07/19/2012 12:53 AM, Andreas Beckmann wrote: Versions of packages fglrx-driver depends on: ii debconf [debconf-2.0] 1.5.45 ii dpkg 1.16.7 pn glx-alternative-fglrxnone ii libc6 2.13-34 pn libfglrxnone ii libgl1-mesa-glx [libgl1] 8.0.3-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxrandr22:1.3.2-2 ii libxrender1 1:0.9.7-1 pn xorg-video-abi-12 | xorg-video-abi-11 | xorg-video-abi-10 | xorgnone pn xserver-xorg-corenone Where did you run reportbug? Half of the dependencies are missing ... I ran reportbug on my home directory. These dependencies do exist on my system. Package: glx-alternative-fglrx Version: 0.2.2 Package: libfglrx Version: 1:12-6-2 xserver-xorg-core 2:1.11.4-1 Versions of packages fglrx-driver recommends: pn fglrx-modules-dkms | fglrx-kernel-12-6none pn libgl1-fglrx-glxnone And you should install these, too Andreas These exist on my system too: Package: fglrx-modules-dkms Version: 1:12-6-2 Package: libgl1-fglrx-glx Version: 1:12-6-2 -- Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521130: icedove: can't save message to Sent folder on IMAP server
Package: icedove Version: 10.0.5-1 Followup-For: Bug #521130 Hi, I am facing the same issue of can't saving messafe to Sent folder on IMAP server. HOWEVER this problem only OCCURS when I am sending email with attachment. Emails without attachments can be save to the Sent folder though. Hor Jiun Shyong -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.4 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3.2 ii fontconfig2.9.0-6 ii libasound21.0.25-3 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-34 ii libcairo2 1.12.2-2 ii libdbus-1-3 1.6.2-2 ii libdbus-glib-1-2 0.100-1 ii libevent-2.0-52.0.19-stable-3 ii libffi5 3.0.10-3 ii libfontconfig12.9.0-6 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.1-4 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libnspr4 2:4.9.1-1 ii libnspr4-0d 2:4.9.1-1 ii libnss3 2:3.13.5-1 ii libnss3-1d2:3.13.5-1 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.26.0-3 ii libsqlite3-0 3.7.13-1 ii libstartup-notification0 0.12-1 ii libstdc++64.7.1-4 ii libvpx1 1.1.0-1 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxrender1 1:0.9.7-1 ii libxt61:1.1.3-1 ii psmisc22.19-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: ii fonts-lyx 2.0.3-3 ii gconf-service 3.2.5-1 ii libgconf-2-4 3.2.5-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libnotify40.7.5-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681049: qa.debian.org: PTS shows older version of wordpress in todo box
Package: qa.debian.org Severity: normal -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.4 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681049: qa.debian.org: PTS shows older version of wordpress in todo box
Package: qa.debian.org Severity: normal The page for wordpress current shows: todo A new upstream version is available:3.4~rc2 http://wordpress.org/wordpress-3.4-RC2.tar.gz, you should consider packaging it. But the current version is newer than that. -- Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee.
Bug#681049: qa.debian.org: PTS shows older version of wordpress in todo box
Noted with thanks. Jiun Shyong On 07/10/2012 05:17 PM, Raphael Hertzog wrote: forcemerge 665247 681049 thanks On Tue, 10 Jul 2012, Hor Jiun Shyong wrote: Package: qa.debian.org Severity: normal Putting some information in the body of the mail is a good idea even if the problem is simple. And in fact this bug has already been reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665247 Please try to verify that a bug has not been already reported before submitting it (I forgot about this one when I suggested you to file this one...). Cheers, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680721: wordpress: Several security vulnerabilities fixed in 3.4.1 CVE-2012-3383, CVE-2012-3384, CVE-2012-3385
On 07/09/2012 02:06 PM, Raphael Hertzog wrote: Great! Do you need direction to get started or do you already know how you can help? Cheers, Yes , I would need direction on how to get started. Thanks. Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680721: wordpress: Several security vulnerabilities fixed in 3.4.1 CVE-2012-3383, CVE-2012-3384, CVE-2012-3385
Hi, I would like to offer my help for the wordpress package too. Thanks. - Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. On 07/09/2012 03:49 AM, Raphael Hertzog wrote: Hello, On Sun, 08 Jul 2012, Henri Salo wrote: Package: wordpress Version: 3.3.2+dfsg-1~squeeze1 Severity: important Tags: security Several security vulnerabilities has been fixed in WordPress version 3.4.1 [1]. CVE-identifiers assigned in oss-security mailing list [2][3]. These issues should be patched as soon as possible. Please ask in case you need my help. Yes, I'll gladly accept help. Are you able to extract and backport the relevant patches? If yes, we definitely want you as co-maintainer. :-) Cheers, - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680460: KVM crashes with segfault error for kernel linux-3.4.4 AMD64
Where's the kvm command line?? #virsh start diaoyudao Where's the output from qemu-kvm bug script? I have installed qemu-kvm-dgb package and set the logging option as below. export LIBVIRT_DEBUGS=1 export LIBVIRT_LOG_OUTPUTS=1:file:virsh.log log_filters=1:libvirt 1:util 1:qemu log_outputs=1:file:/var/log/libvirt/libvirtd.log Under kernel 3.4.4-amd64, (where kvm guest crashes with segfault error), there is no log output for both virsh.log and libvirtd.log when I ran the virsh start command to boot-up the guest.Under kernel 3.2.0-3-amd64, (where kvm guest runs fine) there are output for libvirtd.log . -- Regards, Hor Jiun Shyong ä½ä¿é Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680460: KVM crashes with segfault error for kernel linux-3.4.4 AMD64
Very sorry for the mistakes as I have never used reportbug before. I have fired up reportbug and submitted the information you requested. Thanks. -- Regards, Hor Jiun Shyong ä½ä¿é On 07/06/2012 06:13 PM, Michael Tokarev wrote: On 06.07.2012 13:25, Hor Jiun Shyong wrote: Where's the kvm command line?? #virsh start diaoyudao Hint: I asked for KVM command line, not for VIRSH command line. Where's the output from qemu-kvm bug script? I have installed qemu-kvm-dgb package and set the logging option as below. export LIBVIRT_DEBUGS=1 export LIBVIRT_LOG_OUTPUTS=1:file:virsh.log log_filters=1:libvirt 1:util 1:qemu log_outputs=1:file:/var/log/libvirt/libvirtd.log Under kernel 3.4.4-amd64, (where kvm guest crashes with segfault error), there is no log output for both virsh.log and libvirtd.log when I ran the virsh start command to boot-up the guest.Under kernel 3.2.0-3-amd64, (where kvm guest runs fine) there are output for libvirtd.log . Hint: When you submit a bug against a package using a tool like reportbug, the tool collects the info which is actually useful, both generally (versions of dependent components, version of the kernel etc) and package-specific. As I mentioned already, I tempted to close this bugreport rigth away due to lack of basic information, but instead asked you to provide the required info. You provided no info I asked you about. However, Haruo Kinoshita provided the missing bits for you. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680460: KVM crashes with segfault error for kernel linux-3.4.4 AMD64
Package: qemu-kvm Version: 1.1~z0+dfsg-1 Followup-For: Bug #680460 -- Package-specific info: /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 1 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 2 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate processor : 3 vendor_id : AuthenticAMD cpu family : 18 model : 1 model name : AMD A6-3670 APU with Radeon(tm) HD Graphics stepping: 0 microcode : 0x327 cpu MHz : 800.000 cache size : 1024 KB physical id : 0 siblings: 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter bogomips: 5399.78 TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.4 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii adduser 3.113+nmu3 ii ipxe1.0.0+git-20120202.f6840ba-3 ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3 ii libaio1 0.3.109-3 ii libasound2 1.0.25-3
Bug#677667: fglrx crashes with X server 1.12 on 64bit architecture
Package: fglrx-driver Version: 1:12-6~beta-1 Severity: important I have patched and rebuilt libpciaccess0 but fglrx still crashes. As temporary measure, I am using fglrx-driver 1:12-6~beta-1 while holding the below packages from upgrade. This gives me a working gdm3. xserver-xorg-core_2%3a1.11.4-1_amd64.deb xserver-common_2%3a1.11.4-1_all.deb xorg_1%3a7.6+12_amd64.deb xserver-xorg_1%3a7.6+12_amd64.deb xserver-xorg-input-all_1%3a7.6+12_amd64.deb xserver-xorg-input-evdev_1%3a2.7.0-1_amd64.deb xserver-xorg-input-synaptics_1.5.99.901-1_amd64.deb xserver-xorg-input-wacom_0.12.0-1_amd64.deb -- Regards, Hor Jiun Shyong ä½ä¿é Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. On 06/19/2012 06:05 AM, Paul Menzel wrote: retitle 677667 fglrx crashes with X server 1.12 on 64bit architecture quit Am Samstag, den 16.06.2012, 20:54 +0200 schrieb Paul Menzel: [â¦] Also it seems that there is a workaround for that issues in the upstream report [1] involving patching libpciaccess [2]. But I have not tried it yet. I got it finally working by correctly applying the patch from [2] and rebuilding `libpciaccess0` as described in comment 12 [3]. I post the updated comments here. Find out the PCI address(?) of your graphics device. $ lspci # ASRock E350M1 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9802] [â¦] Then build the package `libpciaccess0`. $ sudo aptitude install devscripts $ sudo aptitude build-dep libpciaccess0 $ debcheckout libpciaccess0 $ cd libpciaccess0 $ # copyhttp://pastebin.com/swpDj4FD to file `fglrx.patch` $ editor fglrx.patch # change `pci_device_find_by_slot(0, 1, 0, 0)` to `pci_device_find_by_slot(0, 0, 1, 0)` in `src/common_interface.c` and `src/common_io.c` $ patch -p1 fglrx.patch $ dch # add entry to Debian changelog $ git commit -a $ dpkg-buildpackage -us -uc -B $ sudo dpkg -i ../libpciaccess0*.deb Thanks, Paul [1] http://ati.cchtml.com/show_bug.cgi?id=522 [2] http://ati.cchtml.com/show_bug.cgi?id=522#c3 [3] http://ati.cchtml.com/show_bug.cgi?id=522#c12 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677954: fglrx-driver: xf86OpenConsole: Cannot find a free VT
Package: fglrx-driver Version: 1:12-6~beta-1 Severity: important On 06/18/2012 03:42 PM, Hor Jiun Shyong wrote: Hi Paul, I faced the same problem of blinking cursor when using the below 3 different drivers : fglrx-driver 1:12-6~beta-1 amd-driver-installer-12-4-x86.x86_64.run amd-driver-installer-12-3-x86.x86_64.run I then followed Issam's recommendation as below to workaround the issue and got a good gdm3. But this breaks the xorg dependencies. On 06/11/2012 06:01 AM, Issam Mehssani wrote: I believe the problem comes from an incompatibility between FGLRX version 12-4-1 and xorg 1.12. I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1. Make sure to downgrade the input packages too. Thanks for the feedback. Will try out and feedback the result. Hi Issam, I have downgraded core xorg files to 1.11.4-1 and xorg input files to lower versions matching the 1.11.4-1 release dates. xserver-xorg-core_2%3a1.11.4-1_amd64.deb xserver-common_2%3a1.11.4-1_all.deb xserver-xorg-dev_2%3a1.11.4-1_amd64.deb xorg_1%3a7.6+12_amd64.deb xorg-dev_1%3a7.6+12_all.deb xserver-xorg_1%3a7.6+12_amd64.deb xserver-xorg-input-all_1%3a7.6+12_amd64.deb xserver-xorg-input-evdev_1%3a2.7.0-1_amd64.deb xserver-xorg-input-synaptics_1.5.99.901-1_amd64.deb xserver-xorg-input-wacom_0.12.0-1_amd64.deb This is followed with a install of amd-driver-installer-12-4-x86.x86_64.run . Success: got my my gdm3 in standard mode. Thanks again. -- Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677451: Fatal server error: xf86OpenConsole: Cannot find a free VT
[ 312.759] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so [ 312.759] (II) Module dri2: vendor=X.Org Foundation [ 312.759] compiled for 1.12.1, module version = 1.2.0 [ 312.759] ABI class: X.Org Server Extension, version 6.0 [ 312.759] (II) Loading extension DRI2 [ 312.759] (II) LoadModule: fglrx [ 312.759] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so [ 312.881] (II) Module fglrx: vendor=FireGL - ATI Technologies Inc. [ 312.881] compiled for 1.4.99.906, module version = 8.96.4 [ 312.881] Module class: X.Org Video Driver [ 312.881] (II) Loading sub module fglrxdrm [ 312.881] (II) LoadModule: fglrxdrm [ 312.881] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so [ 312.881] (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc. [ 312.881] compiled for 1.4.99.906, module version = 8.96.4 [ 312.881] (II) ATI Proprietary Linux Driver Version Identifier:8.96.4 [ 312.881] (II) ATI Proprietary Linux Driver Release Identifier: 8.961 [ 312.881] (II) ATI Proprietary Linux Driver Build Date: Apr 5 2012 23:06:21 [ 312.888] Fatal server error: [ 312.888] xf86OpenConsole: Cannot find a free VT [ 312.888] [ 312.888] Please consult the The X.Org Foundation support at http://wiki.x.org for help. -- Regards, Hor Jiun Shyong 何俊雄 Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677451: Acknowledgement (Fatal server error: xf86OpenConsole: Cannot find a free VT)
Bug solved with downgrade of core xorg files to 1.11.4-1 and xorg input files to lower versions matching the 1.11.4-1 release dates. This is followed with install of fglrx driver version 12-4-1 . Further information as below: On 06/11/2012 06:01 AM, Issam Mehssani wrote: I believe the problem comes from an incompatibility between FGLRX version 12-4-1 and xorg 1.12. I've had the same symptoms and solved it by downgrading xorg to 1.11.4-1. Make sure to downgrade the input packages too. Thanks for the feedback. Will try out and feedback the result. Hi Issam, I have downgraded core xorg files to 1.11.4-1 and xorg input files to lower versions matching the 1.11.4-1 release dates. xserver-xorg-core_2%3a1.11.4-1_amd64.deb xserver-common_2%3a1.11.4-1_all.deb xserver-xorg-dev_2%3a1.11.4-1_amd64.deb xorg_1%3a7.6+12_amd64.deb xorg-dev_1%3a7.6+12_all.deb xserver-xorg_1%3a7.6+12_amd64.deb xserver-xorg-input-all_1%3a7.6+12_amd64.deb xserver-xorg-input-evdev_1%3a2.7.0-1_amd64.deb xserver-xorg-input-synaptics_1.5.99.901-1_amd64.deb xserver-xorg-input-wacom_0.12.0-1_amd64.deb This is followed with a install of amd-driver-installer-12-4-x86.x86_64.run .Success: got my my gdm3 in standard mode. Thanks again. -- Regards, Hor Jiun Shyong ä½ä¿é Blog: jiunshyong.dyndns.org twitter.com/jiunshyong facebook.com/jiunshyong I'm an FSF member -- Help us support software freedom! http://www.fsf.org/jf?referrer=2442 Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666120: Unmet dependencies:, libboost1.49-dev : Conflicts: libboost1.48-dev but 1.48.0-3 is to be installed
Package: libboost1.49-dev Version: 1.49.0-1 Package: libboost1.49-dev Version: 1.48.0-3 On Debian Sid (Linux szechuan 3.2.0-2-amd64 #1 SMP Tue Mar 20 18:36:37 UTC 2012 x86_64 GNU/Linux) root@szechuan:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libboost-locale-dev libio-stty-perl libaccess-bridge-java libboost-filesystem1.46.1 gir1.2-rb-3.0 libgmime-2.4-2 python-mako libboost-random-dev libboost-timer1.48.0 libdmapsharing-3.0-2 rhythmbox-data qemu-user openhackware libx264-118 libcupsdriver1 libboost-graph-parallel1.46.1 openbios-ppc libboost-graph-parallel1.48.0 libboost-system1.46.1 qemu-system libboost-chrono1.48.0 libio-pty-perl xulrunner-9.0 libboost-python1.46.1 libboost-signals1.46.1 libboost-signals-dev libtracker-extract-0.12-0 libboost-signals1.48.0 libboost-program-options1.46.1 libwebp-dev libboost-timer-dev python-gnomekeyring libgetopt-argvfile-perl libboost-date-time1.46.1 libboost-thread-dev libkexiv2-9 librhythmbox-core5 libboost-date-time1.48.0 libboost-chrono-dev libboost-test1.46.1 openbios-sparc libboost-iostreams1.46.1 libboost-test1.48.0 libboost-program-options-dev libboost-wave1.46.1 libboost-test-dev libboost-wave-dev libboost-graph1.46.1 libboost-wave1.48.0 libboost-graph1.48.0 libfdt1 libboost-locale1.48.0 libexpect-perl libboost-graph-parallel-dev libboost-serialization-dev libboost-system-dev libaccess-bridge-java-jni libboost-mpi-python1.48.0 libvpx0 kdegraphics-libs-data libboost-math-dev gir1.2-gst-plugins-base-0.10 libboost-thread1.46.1 grilo-plugins-0.1 libjpeg62 libquvi0 libboost-mpi1.46.1 libboost-mpi-dev libmozjs8d libmozjs9d zeitgeist-core libboost-mpi1.48.0 libtracker-miner-0.12-0 libconfig-tiny-perl libksane-data libyajl1 libboost-filesystem-dev media-player-info libberkeleydb-perl python-markupsafe libxen-4.1 libraptor1 libboost-serialization1.46.1 gir1.2-webkit-3.0 libboost-serialization1.48.0 libboost-math1.46.1 libtracker-sparql-0.12-0 libgrilo-0.1-0 libboost-math1.48.0 libwww-curl-perl libboost-iostreams-dev libboost-regex1.46.1 ipxe libboost-regex1.48.0 libboost-random1.48.0 libboost-graph-dev libkdcraw9 gir1.2-javascriptcoregtk-3.0 libaudiofile0 libboost-python-dev Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libboost-chrono-dev libboost-chrono1.49-dev libboost-locale1.49-dev libboost-random1.49-dev libboost-timer1.49-dev libboost1.49-dev Suggested packages: libboost1.49-doc doxygen default-jdk fop The following packages will be REMOVED: libboost-chrono1.48-dev libboost-locale1.48-dev libboost1.48-dev The following NEW packages will be installed: libboost-chrono1.49-dev libboost-locale1.49-dev libboost-random1.49-dev libboost-timer1.49-dev libboost1.49-dev The following packages will be upgraded: libboost-chrono-dev 1 upgraded, 5 newly installed, 3 to remove and 180 not upgraded. 54 not fully installed or removed. Need to get 0 B/9,885 kB of archives. After this operation, 1,224 kB of additional disk space will be used. Do you want to continue [Y/n]? y Reading changelogs... Done (Reading database ... 206930 files and directories currently installed.) Removing libboost-locale1.48-dev ... Selecting previously unselected package libboost-chrono1.49-dev. (Reading database ... 206921 files and directories currently installed.) Unpacking libboost-chrono1.49-dev (from .../libboost-chrono1.49-dev_1.49.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libboost-chrono1.49-dev_1.49.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libboost_chrono.a', which is also in package libboost-chrono1.48-dev 1.48.0-3 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to replace libboost-chrono-dev 1.48.0.3 (using .../libboost-chrono-dev_1.49.0.1_amd64.deb) ... Unpacking replacement libboost-chrono-dev ... Errors were encountered while processing: /var/cache/apt/archives/libboost-chrono1.49-dev_1.49.0-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648402: [Pkg-alsa-devel] Bug#648402: ALSA driver 'snd_hda_intel': snd_pcm_avail() returned a value that is exceptionally large: 1250172 bytes (7087 ms)
Hi, Sorry for the late reply. Didn't manage to test it as have upgraded system from Wheezy to Sid. Under Sid, error does not appear any more. root@xiamen:~# cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.24. root@xiamen:~# cat /proc/version Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 201 [9.152902] snd_hda_intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [9.152982] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [9.153017] snd_hda_intel :00:1b.0: setting latency timer to 64 Thanks, Jiun Shyong On 11/12/2011 01:43 AM, Elimar Riesebieter wrote: * Hor Jiun Shyong [11 15:56 +0800]: Package: alsa-base Version: 1.0.23+dfsg-4 Package: pulseaudio Version: 1.0-4 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 1250172 bytes (7087 ms). Try: # apt-get remove --purge pulseaudio # rm -f /var/lib/alsa/asound.state # shutdown -r now Test again and report back please. Else what tells: $ cat /proc/asound/version $ cat /proc/version ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648402: ALSA driver 'snd_hda_intel': snd_pcm_avail() returned a value that is exceptionally large: 1250172 bytes (7087 ms)
Package: alsa-base Version: 1.0.23+dfsg-4 Package: pulseaudio Version: 1.0-4 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 1250172 bytes (7087 ms). Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: snd_pcm_dump(): Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Soft volume PCM Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Control: PCM Playback Volume Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: min_dB: -51 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: max_dB: 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: resolution: 256 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Its setup is: Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: stream : PLAYBACK Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: access : MMAP_INTERLEAVED Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: format : S16_LE Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: subformat: STD Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: channels : 2 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: rate : 44100 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: exact rate : 44100 (44100/1) Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: msbits : 16 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: buffer_size : 16384 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_size : 8192 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_time : 185759 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: tstamp_mode : ENABLE Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_step : 1 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: avail_min: 15681 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_event : 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: start_threshold : -1 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: stop_threshold : 4611686018427387904 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: silence_threshold: 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: silence_size : 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: boundary : 4611686018427387904 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: Its setup is: Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: stream : PLAYBACK Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: access : MMAP_INTERLEAVED Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: format : S16_LE Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: subformat: STD Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: channels : 2 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: rate : 44100 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: exact rate : 44100 (44100/1) Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: msbits : 16 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: buffer_size : 16384 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_size : 8192 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_time : 185759 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: tstamp_mode : ENABLE Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_step : 1 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: avail_min: 15681 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: period_event : 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: start_threshold : -1 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: stop_threshold : 4611686018427387904 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: silence_threshold: 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: silence_size : 0 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: boundary : 4611686018427387904 Nov 11 14:38:21 xiamen pulseaudio[2602]: [alsa-sink] alsa-util.c: appl_ptr : 8419937 Nov 11 14:38:21 xiamen
Bug#648403: MusicTracker plugin for rhythmbox version: 0.4.22 status changing with music title does not work after upgrading to gnome 3.0.2
Package: pidgin Version: 2.10.0-1+b1 Package: rhythmbox Version: 2.90.1~git20110919.2dfea6-3 Package: gnome Verison: 1:3.0+3 MusicTracker plugin for rhythmbox version: 0.4.22 status changing with music title does not work after upgrading to gnome 3.0.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642484: [Pkg-alsa-devel] Bug#642484: Squeaky sound output when playing rmvb (Real Media Variable Bit) video format files
Hi Elimar, Does it mean that Non-free packages does not accept bug submission since they are not intended to run on Debian GNU/Linux? Thanks, Jiun Shyong On 09/25/2011 04:14 PM, Elimar Riesebieter wrote: * Flying Fox of the Snowy Mountain [110923 06:26 +0800]: Package: linux-sound-base Version: 1.0.23+dfsg-4 Symptom: Squeaky sound output when playing rmvb (Real Media Variable Bit) video format files. However when avi, mkv, DVD are played, sound out put is good. Seems to affect rmvb files only. Tested with vlc, Movie Player and KMPlayer: all produced the same symptom. I close this bug hereby. Playing rmvb (Real Player) audios and videos is not intendet to run on Debian GNU Linux. One have to find out which requirements are needed to play such files i.e. with mplayer. The essential codecs and others are not available in offical Debian distro. Else it is not an ALSA bug at all. Elimar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642056: Console is spammed with Message from syslogd@meixian at Sep 19 12:03:07 ... such IMContext,when Pidgin IRC protocol is used.
Noticed the spammings also occur when the IRC protocol of pidgin is turned off. The spamming also occurred for scim-bridge package: Message from syslogd@meixian at Sep 21 16:51:55 ... invalid char is given at scim_bridge_string_to_uint (): - Thanks, Hor Jiun Shyong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642056: Console is spammed with Message from syslogd@meixian at Sep 19 12:03:07 ... such IMContext,when Pidgin IRC protocol is used.
Package: bash Version: 4.1-3 Package: Pidgin Version: 2.10.0-1+b1* * Console is spammed with Message from syslogd@meixian at Sep 19 12:03:07 ... such IMContext when Pidgin IRC protocol is used.
Bug#641946: FM801 Sound card not detected for linux-image-3.0.0-1-486
Package: linux-image-3.0.0-1-486 Version: 3.0.0-3 Issue: Sound card not detected. Soundcard Chipset: FM801.Soundcard is working under linux-image-2.6.39-2-486 and older kernels. [8.590018] FM801 :00:09.0: enabling device (0004 - 0005) [8.590045] FM801 :00:09.0: PCI INT A - Link[LNKD] - GSI 5 (level, low) - IRQ 5 [8.609524] TEA575x radio not found [8.609599] FM801 :00:09.0: PCI INT A disabled [8.609614] [ cut here ] [8.609632] WARNING: at /build/buildd-linux-2.6_3.0.0-3-i386-G7H4XL/linux-2.6-3.0.0/debian/build/source_i386_none/kernel/irq/manage.c:1147 __free_irq+0x6b/0xd6() [8.609639] Hardware name: System Name [8.609643] Trying to free already-free IRQ 5 [8.609647] Modules linked in: snd_fm801(+) snd_ac97_codec ac97_bus snd_tea575x_tuner videodev media snd_pcm_oss snd_mixer_oss snd_pcm snd_opl3_lib snd_hwdep snd_mpu401_uart via686a snd_rawmidi snd_seq_device i2c_viapro snd_timer snd soundcore i2c_core snd_page_alloc evdev parport_pc shpchp pci_hotplug pcspkr psmouse fm801_gp gameport serio_raw parport processor thermal_sys button ext3 jbd mbcache sg sd_mod crc_t10dif ata_generic pata_via pata_pdc202xx_old libata floppy scsi_mod 8139too uhci_hcd ehci_hcd usbcore mii [last unloaded: scsi_wait_scan] [8.609727] Pid: 285, comm: modprobe Not tainted 3.0.0-1-486 #1 [8.609732] Call Trace: [8.609750] [c1023568] ? warn_slowpath_common+0x6a/0x7d [8.609756] [c105e86c] ? __free_irq+0x6b/0xd6 [8.609764] [c10235e1] ? warn_slowpath_fmt+0x28/0x2c [8.609770] [c105e86c] ? __free_irq+0x6b/0xd6 [8.609777] [c105e8f7] ? free_irq+0x20/0x33 [8.609799] [e0a0d662] ? snd_fm801_free+0x29/0x44 [snd_fm801] [8.609825] [e09b4cf8] ? snd_device_free+0x5e/0x83 [snd] [8.609837] [e09b4e7e] ? snd_device_free_all+0x34/0x4a [snd] [8.609848] [e09b15ff] ? snd_card_do_free+0x53/0x9c [snd] [8.609859] [e09b1ebb] ? snd_card_free+0x83/0x8e [snd] [8.609869] [e0a0d679] ? snd_fm801_free+0x40/0x44 [snd_fm801] [8.609882] [c109d616] ? kfree+0x47/0x55 [8.609893] [e0a0e2f6] ? snd_card_fm801_probe+0x4bc/0x50e [snd_fm801] [8.609910] [c10e3f9c] ? __sysfs_add_one+0x30/0x50 [8.609918] [c10e3dba] ? sysfs_addrm_finish+0x13/0x86 [8.609930] [c11b390b] ? arch_local_irq_save+0x11/0x18 [8.609938] [c11b47bd] ? __pm_runtime_set_status+0xcb/0xe7 [8.609955] [c113bd5b] ? local_pci_probe+0x2b/0x55 [8.609963] [c113c181] ? pci_device_probe+0x43/0x65 [8.609974] [c11af0d0] ? driver_probe_device+0x8a/0x109 [8.609980] [c11af18f] ? __driver_attach+0x40/0x5b [8.609987] [c11ae66c] ? bus_for_each_dev+0x37/0x59 [8.609994] [c11aee78] ? driver_attach+0x11/0x13 [8.610002] [c11af14f] ? driver_probe_device+0x109/0x109 [8.610009] [c11aeb9d] ? bus_add_driver+0x83/0x1bd [8.610026] [c1126815] ? kset_find_obj_hinted+0x44/0x74 [8.610035] [e07f9000] ? 0xe07f8fff [8.610042] [c11af537] ? driver_register+0x75/0xca [8.610057] [c1017d46] ? change_page_attr_clear+0x1a/0x1f [8.610065] [e07f9000] ? 0xe07f8fff [8.610070] [c113c325] ? __pci_register_driver+0x2c/0x82 [8.610077] [e07f9000] ? 0xe07f8fff [8.610084] [c1001212] ? do_one_initcall+0x67/0x111 [8.610099] [c1049963] ? sys_init_module+0x1358/0x1525 [8.610124] [c1274e63] ? sysenter_do_call+0x12/0x28 [8.610130] ---[ end trace 9b1201473d959a65 ]--- [8.610136] Trying to free nonexistent resource a400-a47f -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641697: [drm] nouveau 0000:02:00.0: PGRAPH: unsupported chipset, please report!
Package: linux-image-3.0.0-1-amd64 Version: 3.0.0-3 Error Message: [drm] nouveau :02:00.0: PGRAPH: unsupported chipset, please report! [ 17.227473] nouveau :02:00.0: PCI INT A - Link[LNED] - GSI 19 (level, low) - IRQ 19 [ 17.227477] nouveau :02:00.0: setting latency timer to 64 [ 17.228361] [drm] nouveau :02:00.0: Detected an NVc0 generation card (0x0c1000a1) [ 17.230940] [drm] nouveau :02:00.0: Attempting to load BIOS image from PRAMIN [ 17.289588] [drm] nouveau :02:00.0: ... appears to be valid [ 17.289591] [drm] nouveau :02:00.0: BIT BIOS found [ 17.289593] [drm] nouveau :02:00.0: Bios version 70.08.45.00 [ 17.289595] [drm] nouveau :02:00.0: Pointer to BIT loadval table invalid [ 17.289640] [drm] nouveau :02:00.0: TMDS table version 2.0 [ 17.289642] [drm] nouveau :02:00.0: Found Display Configuration Block version 4.0 [ 17.289645] [drm] nouveau :02:00.0: Raw DCB entry 0: 02000362 00020010 [ 17.289647] [drm] nouveau :02:00.0: Raw DCB entry 1: 04011310 [ 17.289649] [drm] nouveau :02:00.0: Raw DCB entry 2: 01022302 00020030 [ 17.289651] [drm] nouveau :02:00.0: Raw DCB entry 3: 02022300 [ 17.289654] [drm] nouveau :02:00.0: DCB connector table: VHER 0x40 5 16 4 [ 17.289656] [drm] nouveau :02:00.0: 0: 0x00010061: type 0x61 idx 0 tag 0x51 [ 17.289658] [drm] nouveau :02:00.0: 1: 0x0100: type 0x00 idx 1 tag 0xff [ 17.289660] [drm] nouveau :02:00.0: 2: 0x1230: type 0x30 idx 2 tag 0x07 [ 17.289664] [drm] nouveau :02:00.0: Parsing VBIOS init table 0 at offset 0x69D0 [ 17.309654] [drm] nouveau :02:00.0: Parsing VBIOS init table 1 at offset 0x701F [ 17.318232] parport_pc 00:05: reported by Plug and Play ACPI [ 17.318275] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 17.322382] [drm] nouveau :02:00.0: Parsing VBIOS init table 2 at offset 0x8150 [ 17.322385] [drm] nouveau :02:00.0: Parsing VBIOS init table 3 at offset 0x8154 [ 17.322429] [drm] nouveau :02:00.0: Parsing VBIOS init table 4 at offset 0x823C [ 17.322430] [drm] nouveau :02:00.0: Parsing VBIOS init table at offset 0x82A1 [ 17.342277] [drm] nouveau :02:00.0: 0x6987: Condition still not met after 20ms, skipping following opcodes [ 17.361037] [drm] nouveau :02:00.0: 2 available performance level(s) [ 17.361041] [drm] nouveau :02:00.0: 0: memory 135MHz core 50MHz shader 101MHz voltage 880mV timing 2 [ 17.361044] [drm] nouveau :02:00.0: 1: memory 324MHz core 405MHz shader 810MHz voltage 900mV timing 1 [ 17.361103] [TTM] Zone kernel: Available graphics memory: 4100180 kiB. [ 17.361104] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [ 17.361106] [TTM] Initializing pool allocator. [ 17.361116] [drm] nouveau :02:00.0: Detected 512MiB VRAM [ 17.365147] [drm] nouveau :02:00.0: 512 MiB GART (aperture) [ 17.365156] [drm] nouveau :02:00.0: PGRAPH: unsupported chipset, please report! [ 17.369638] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 17.369640] [drm] No driver support for vblank timestamp query. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635573: Endless message of Unable to enumerate usb device on port 5
Hi Jonathan,
Thanks for the follow-up. Will test and feedback asap.
Regards,
Jiun Shyong
On 08/05/2011 11:36 PM, Jonathan Nieder wrote:
severity 635573 important
tags 635573 + upstream
forwarded 635573 https://bugzilla.kernel.org/show_bug.cgi?id=22052
merge 620848 635573
tags 620848 + fixed-upstream
quit
Hi,
Hor Jiun Shyong wrote:
[Subject: lspci output]
Please keep in mind that this appears as the subject line when these
mails are received by email, so it can be a good place to put valuable
context.
[...]
00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller
Yep, this looks like Bug#620848. Could you test the package from
http://people.debian.org/~benh/packages/linux-image-2.6.39-3-amd64_2.6.39-4~a.test1_amd64.deb
, the latest upstream snapshot version from kernel.org, or the
following patch? Instructions for testing a snapshot or a patch are
athttp://kernel-handbook.alioth.debian.org/.
Thanks,
Jonathan
commit 6ea12a04
Author: Alan Sternst...@rowland.harvard.edu
Date: Fri Jul 15 17:22:15 2011 -0400
USB: OHCI: fix another regression for NVIDIA controllers
The NVIDIA series of OHCI controllers continues to be troublesome. A
few people using the MCP67 chipset have reported that even with the
most recent kernels, the OHCI controller fails to handle new
connections and spams the system log with unable to enumerate USB
port messages. This is different from the other problems previously
reported for NVIDIA OHCI controllers, although it is probably related.
It turns out that the MCP67 controller does not like to be kept in the
RESET state very long. After only a few seconds, it decides not to
work any more. This patch (as1479) changes the PCI initialization
quirk code so that NVIDIA controllers are switched into the SUSPEND
state after 50 ms of RESET. With no interrupts enabled and all the
downstream devices reset, and thus unable to send wakeup requests,
this should be perfectly safe (even for non-NVIDIA hardware).
The removal code in ohci-hcd hasn't been changed; it will still leave
the controller in the RESET state. As a result, if someone unloads
ohci-hcd and then reloads it, the controller won't work again until
the system is rebooted. If anybody complains about this, the removal
code can be updated similarly.
This fixes Bugzilla #22052.
Tested-by: Larry Fingerlarry.fin...@lwfinger.net
Cc: stablesta...@kernel.org
Signed-off-by: Alan Sternst...@rowland.harvard.edu
Signed-off-by: Greg Kroah-Hartmangre...@suse.de
diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
index b5a7304f..a9d31590 100644
--- a/drivers/usb/host/pci-quirks.c
+++ b/drivers/usb/host/pci-quirks.c
@@ -35,6 +35,8 @@
#define OHCI_INTRSTATUS 0x0c
#define OHCI_INTRENABLE 0x10
#define OHCI_INTRDISABLE 0x14
+#define OHCI_FMINTERVAL0x34
+#define OHCI_HCR (1 0) /* host controller reset */
#define OHCI_OCR (1 3) /* ownership change request */
#define OHCI_CTRL_RWC (1 9) /* remote wakeup connected */
#define OHCI_CTRL_IR (1 8) /* interrupt routing */
@@ -497,6 +499,32 @@ static void __devinit quirk_usb_handoff_ohci(struct
pci_dev *pdev)
/* reset controller, preserving RWC (and possibly IR) */
writel(control OHCI_CTRL_MASK, base + OHCI_CONTROL);
+ readl(base + OHCI_CONTROL);
+
+ /* Some NVIDIA controllers stop working if kept in RESET for too long */
+ if (pdev-vendor == PCI_VENDOR_ID_NVIDIA) {
+ u32 fminterval;
+ int cnt;
+
+ /* drive reset for at least 50 ms (7.1.7.5) */
+ msleep(50);
+
+ /* software reset of the controller, preserving HcFmInterval */
+ fminterval = readl(base + OHCI_FMINTERVAL);
+ writel(OHCI_HCR, base + OHCI_CMDSTATUS);
+
+ /* reset requires max 10 us delay */
+ for (cnt = 30; cnt 0; --cnt) { /* ... allow extra time */
+ if ((readl(base + OHCI_CMDSTATUS) OHCI_HCR) == 0)
+ break;
+ udelay(1);
+ }
+ writel(fminterval, base + OHCI_FMINTERVAL);
+
+ /* Now we're in the SUSPEND state with all devices reset
+* and wakeups and interrupts disabled
+*/
+ }
/*
* disable interrupts
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635573: lspci output
root@nanyang:/home/jiunshyong# lspci -v 00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [dc] HyperTransport: MSI Mapping Enable+ Fixed- 00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2) Subsystem: Hewlett-Packard Company Device 30d6 Flags: 66MHz, fast devsel, IRQ 10 I/O ports at 3080 [size=64] I/O ports at 3040 [size=64] I/O ports at 3000 [size=64] Capabilities: [44] Power Management version 2 Kernel driver in use: nForce2_smbus 00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2) Subsystem: Hewlett-Packard Company Device 30d6 Flags: 66MHz, fast devsel 00:01.3 Co-processor: nVidia Corporation MCP67 Co-processor (rev a2) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11 Memory at fc20 (32-bit, non-prefetchable) [size=512K] 00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17 Memory at fc486000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Kernel driver in use: ohci_hcd 00:02.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17 Memory at fc489000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port: BAR=1 offset=0098 Capabilities: [80] Power Management version 2 Kernel driver in use: ehci_hcd 00:04.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16 Memory at fc487000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Kernel driver in use: ohci_hcd 00:04.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2) (prog-if 20 [EHCI]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16 Memory at fc489400 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port: BAR=1 offset=0098 Capabilities: [80] Power Management version 2 Kernel driver in use: ehci_hcd 00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1) (prog-if 8a [Master SecP PriP]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] I/O ports at 30c0 [size=16] Capabilities: [44] Power Management version 2 Kernel driver in use: pata_amd 00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20 Memory at fc48 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+ Kernel driver in use: HDA Intel 00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode]) Flags: bus master, 66MHz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=02, sec-latency=64 Memory behind bridge: fc10-fc1f Capabilities: [b8] Subsystem: Hewlett-Packard Company Device 30d6 Capabilities: [8c] HyperTransport: MSI Mapping Enable- Fixed- 00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2) (prog-if 85 [Master SecO PriO]) Subsystem: Hewlett-Packard Company Device 30d6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 I/O ports at 30f0 [size=8] I/O ports at 30e4 [size=4] I/O ports at 30e8 [size=8] I/O ports at 30e0 [size=4] I/O ports at 30d0 [size=16] Memory at fc484000 (32-bit, non-prefetchable) [size=8K] Capabilities: [44] Power Management version 2 Capabilities: [8c] SATA HBA v1.0 Capabilities: [b0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+ Kernel driver in use: ahci 00:0a.0 Ethernet controller: nVidia
Bug#636675: Debian Testing Cd install on KVM virtualisation stops at Select and install software stage
Package: Debian GNU/Linux testing Squeeze - Official Snapshot amd64 CD Binary-1 20090302-06:55 Package: qemu-kvm Version: 0.14.1+dfsg-3 Package: libvirt-bin Version: 0.9.3-3 Package: virt-manager Version: 0.8.7-1 Debian Testing Cd installation on KVM virtualisation stops at Select and install software stage. The same symptoms occur on other debian cd installations as well. The latest one occurred with cd install dated in late july: I didn't manage to get the exact date version as have discarded it. I am downloading the August 1 Debian install cd and will try it out once completed. Interestingly the same symptom occured when I tried to install the debian cds on Virtualbox running on both a Debian Linux and Mac OS laptops. Installation with RHEL 6.1 beta cd is successful on the same host. I am using Debian GNU/Linux Sid with kernel Linux 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux, Gnome: 2.30.2 running on AMD Phenom II x4 3.2Ghz with 8GB memory. Thanks, Hor Jiun Shyong -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635573: Endless message of Unable to enumerate usb device on port 5
Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-31 Package:linux-image-2.6.38-2-amd64 Version: 2.6.38-5 Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-3 Console terminal is barraged by endless messages of Unable to enumerate usb device on port 5. I am using Debian Wheezy with installed kernels of the above. However kernel linux-image-2.6.32-3-amd642.6.32-9 is not affected. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635319: Vlc will stop playing rmvb movie when approaching end of movie
Package: vlc Version: 1.1.10-1+b1 Vlc will stop playing rmvb movie when approaching end of movie Using Debian Wheezy with kernel 2.6.39-2-486 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
