Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hello Michael, Am 1/12/2013 1:24 PM, Michael Tokarev wrote: Peter, are you able to run git bisect or something like that, to try to pinpoint either the commit which introduced this issue or which fixed it? Well, i'm no expert at git, but i made some progress, see below. Besides, what are the sympthoms of the device non-working? Does it happen with linux guest too? Have you tried re-running the guest again when the problem occur, using the same problematic version of qemu - I mean, is it 100% reproducible or happens at random? In my case it's the SmartCard-Reader that's not working, i.e. the DATEV Software called Sicherheitspaket does not work. The background process called SiPaHost.exe just hangs; any client program trying to display SmartCard information does also just hang forever. That behaviour is 100% reproducible and persists over reboots of the Linux host and/or the Windows guest (Windows XP SP3). I did not try Linux guests. Yesterday, i used git to checkout all qemu-kvm versions from kernel.org and build Debian packets from it (source kept vanilla, i just applied the two patches that rename paths from 'qemuXXX' to 'kvmXXX'). The findings were: - v1.0 - ok - v1.0.1 - ok - v1.1.0 - not ok - v1.1.1 - not ok - v1.1.2 - not ok - v1.2.0 - not ok So far, this is consistent with the findings in this bug report. BUT: The latest HEAD from kernel.org (called v1.2.50) also does work again! So, i'm now learning about git bisect (however, today i won't have time for this). Regards, Peter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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
Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hi, well - it's probably only for historic interest, but if i made no bisecting mistake, this commit has fixed it (note that the meaning of 'good' and 'bad' is swapped due to how git bisect works): root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 87 revisions left to test after this (roughly 7 steps) [c26032b2c91721245bfec542d94f37a0238e986e] target-xtensa: don't emit extra tcg_gen_goto_tb root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 43 revisions left to test after this (roughly 6 steps) [1fd959466574c3d46f4898f2e27cd3b1060338e4] tcg-sparc: Mask shift immediates to avoid illegal insns. root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 24 revisions left to test after this (roughly 5 steps) [e55f523d7977480462151d8abb0ebb4b1747eabf] tcg-hppa: Fix broken load/store helpers root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 12 revisions left to test after this (roughly 4 steps) [09054d19e72f6991cd359d41c479badd92f62a06] usb-redir: Add chardev open / close debug logging root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 6 revisions left to test after this (roughly 3 steps) [a221ae3fcc55fcc3911587bc572af88eed3342dd] tcg-sparc: Fix ADDX opcode. root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 2 revisions left to test after this (roughly 2 steps) [cfb75cb9807463ebe18b127096b48b5d0db1ce03] Merge branch 'usb.65' of git://git.kraxel.org/qemu root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [72a04d0c178f01908d74539230d9de64ffc6da19] uhci: Don't queue up packets after one with the SPD flag set root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [35efba2cc6812dc980c336d7b9bf81dbfb5daf00] usb-redir: Revert usb-redir part of commit 93bfef4c root@debian:~/qemu_git/qemu-kvm# git bisect good 72a04d0c178f01908d74539230d9de64ffc6da19 is the first bad commit commit 72a04d0c178f01908d74539230d9de64ffc6da19 Author: Hans de Goede hdego...@redhat.com Date: Wed Sep 12 15:08:40 2012 +0200 uhci: Don't queue up packets after one with the SPD flag set Don't queue up packets after a packet with the SPD (short packet detect) flag set. Since we won't know if the packet will actually be short until it has completed, and if it is short we should stop the queue. This fixes a miniature photoframe emulating a USB cdrom with the windows software for it not working. Signed-off-by: Hans de Goede hdego...@redhat.com Signed-off-by: Gerd Hoffmann kra...@redhat.com :04 04 18e7490171762dec04cb8ce49fd21e0b685b53b2 86f7cb33d8b77828e671c5fb39c9d137d39eca06 M hw root@debian:~/qemu_git/qemu-kvm# HTH. Regards, Peter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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
Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hello Michael, Am 1/12/2013 1:24 PM, Michael Tokarev wrote: Peter, are you able to run git bisect or something like that, to try to pinpoint either the commit which introduced this issue or which fixed it? Well, i'm no expert at git, but i made some progress, see below. Besides, what are the sympthoms of the device non-working? Does it happen with linux guest too? Have you tried re-running the guest again when the problem occur, using the same problematic version of qemu - I mean, is it 100% reproducible or happens at random? In my case it's the SmartCard-Reader that's not working, i.e. the DATEV Software called Sicherheitspaket does not work. The background process called SiPaHost.exe just hangs; any client program trying to display SmartCard information does also just hang forever. That behaviour is 100% reproducible and persists over reboots of the Linux host and/or the Windows guest (Windows XP SP3). I did not try Linux guests. Yesterday, i used git to checkout all qemu-kvm versions from kernel.org and build Debian packets from it (source kept vanilla, i just applied the two patches that rename paths from 'qemuXXX' to 'kvmXXX'). The findings were: - v1.0 - ok - v1.0.1 - ok - v1.1.0 - not ok - v1.1.1 - not ok - v1.1.2 - not ok - v1.2.0 - not ok So far, this is consistent with the findings in this bug report. BUT: The latest HEAD from kernel.org (called v1.2.50) also does work again! So, i'm now learning about git bisect (however, today i won't have time for this). Regards, Peter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hi, well - it's probably only for historic interest, but if i made no bisecting mistake, this commit has fixed it (note that the meaning of 'good' and 'bad' is swapped due to how git bisect works): root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 87 revisions left to test after this (roughly 7 steps) [c26032b2c91721245bfec542d94f37a0238e986e] target-xtensa: don't emit extra tcg_gen_goto_tb root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 43 revisions left to test after this (roughly 6 steps) [1fd959466574c3d46f4898f2e27cd3b1060338e4] tcg-sparc: Mask shift immediates to avoid illegal insns. root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 24 revisions left to test after this (roughly 5 steps) [e55f523d7977480462151d8abb0ebb4b1747eabf] tcg-hppa: Fix broken load/store helpers root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 12 revisions left to test after this (roughly 4 steps) [09054d19e72f6991cd359d41c479badd92f62a06] usb-redir: Add chardev open / close debug logging root@debian:~/qemu_git/qemu-kvm# git bisect good Bisecting: 6 revisions left to test after this (roughly 3 steps) [a221ae3fcc55fcc3911587bc572af88eed3342dd] tcg-sparc: Fix ADDX opcode. root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 2 revisions left to test after this (roughly 2 steps) [cfb75cb9807463ebe18b127096b48b5d0db1ce03] Merge branch 'usb.65' of git://git.kraxel.org/qemu root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [72a04d0c178f01908d74539230d9de64ffc6da19] uhci: Don't queue up packets after one with the SPD flag set root@debian:~/qemu_git/qemu-kvm# git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [35efba2cc6812dc980c336d7b9bf81dbfb5daf00] usb-redir: Revert usb-redir part of commit 93bfef4c root@debian:~/qemu_git/qemu-kvm# git bisect good 72a04d0c178f01908d74539230d9de64ffc6da19 is the first bad commit commit 72a04d0c178f01908d74539230d9de64ffc6da19 Author: Hans de Goede hdego...@redhat.com Date: Wed Sep 12 15:08:40 2012 +0200 uhci: Don't queue up packets after one with the SPD flag set Don't queue up packets after a packet with the SPD (short packet detect) flag set. Since we won't know if the packet will actually be short until it has completed, and if it is short we should stop the queue. This fixes a miniature photoframe emulating a USB cdrom with the windows software for it not working. Signed-off-by: Hans de Goede hdego...@redhat.com Signed-off-by: Gerd Hoffmann kra...@redhat.com :04 04 18e7490171762dec04cb8ce49fd21e0b685b53b2 86f7cb33d8b77828e671c5fb39c9d137d39eca06 M hw root@debian:~/qemu_git/qemu-kvm# HTH. Regards, Peter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hi again! The good news: 1.3.0 works (at least with my setup). The bad news is that this might lower the motivation to fix 1.1.2 ;-) ... Attached is the USB trace file from the non-working case with V 1.1.2. If decompressed, it's an 185 MB text file and - honestly - i cannot make any sense of it, but here you have it... ;-) There's two USB devices passed-through: 1) vendor=0x529 product=0x1 - Hardlock USB Dongle 2) vendor=0xd46 product=0x3003 - Kobil USB Smartcard Reader HTH, Peter ** Attachment added: Trace of the non-working case https://bugs.launchpad.net/qemu/+bug/1033727/+attachment/3479688/+files/usb_trace.txt.bz2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Hi again! The good news: 1.3.0 works (at least with my setup). The bad news is that this might lower the motivation to fix 1.1.2 ;-) ... Attached is the USB trace file from the non-working case with V 1.1.2. If decompressed, it's an 185 MB text file and - honestly - i cannot make any sense of it, but here you have it... ;-) There's two USB devices passed-through: 1) vendor=0x529 product=0x1 - Hardlock USB Dongle 2) vendor=0xd46 product=0x3003 - Kobil USB Smartcard Reader HTH, Peter ** Attachment added: Trace of the non-working case https://bugs.launchpad.net/qemu/+bug/1033727/+attachment/3479688/+files/usb_trace.txt.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Am 1/8/2013 6:08 PM, Serge Hallyn wrote: (replying to comment #12) could you please follow up on comments #6 and #7? It also would be worthwhile, at this point, checking whether latest upstream (1.3) is still broken. Just a short note: I somehow produced a backported *.deb for 1.3.0 and i managed to recompile the debs of 1.1.2 and 1.0 from debian backports with --enable-trace-backend=simple. The problematic box runs Debian Squeeze with Kernel 3.2.35 (and some other packages) from backports. Tomorrow evening i'm going to make test runs on the system. I'll keep you posted. Regards, Peter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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
Re: [Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Am 1/8/2013 6:08 PM, Serge Hallyn wrote: (replying to comment #12) could you please follow up on comments #6 and #7? It also would be worthwhile, at this point, checking whether latest upstream (1.3) is still broken. Just a short note: I somehow produced a backported *.deb for 1.3.0 and i managed to recompile the debs of 1.1.2 and 1.0 from debian backports with --enable-trace-backend=simple. The problematic box runs Debian Squeeze with Kernel 3.2.35 (and some other packages) from backports. Tomorrow evening i'm going to make test runs on the system. I'll keep you posted. Regards, Peter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Just confirming the bug. I'm having the same issues with the same USB smart card reader as the submitter (Kobil mIDentity) on Debian Squeeze using the qemu-kvm version 1.2.0 from debian-backports. Going back to 1.0 fixes the problem (http://snapshot.debian.org/package/qemu- kvm/1.0%2Bdfsg-8~bpo60%2B1). Since I can easily toggle between versions i could provide more support, if wanted and instructions provided... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Referring to my last comment: The URL does only work if you add a backslash at the end, sorry about that. One last note: In Germany, the Kobil USB Reader is/was supplied by DATEV (see http://www.datev.com/) to their members/partners. So, anybody who's running DATEV software on kvm-virtualized systems will run into this problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- 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 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Just confirming the bug. I'm having the same issues with the same USB smart card reader as the submitter (Kobil mIDentity) on Debian Squeeze using the qemu-kvm version 1.2.0 from debian-backports. Going back to 1.0 fixes the problem (http://snapshot.debian.org/package/qemu- kvm/1.0%2Bdfsg-8~bpo60%2B1). Since I can easily toggle between versions i could provide more support, if wanted and instructions provided... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Referring to my last comment: The URL does only work if you add a backslash at the end, sorry about that. One last note: In Germany, the Kobil USB Reader is/was supplied by DATEV (see http://www.datev.com/) to their members/partners. So, anybody who's running DATEV software on kvm-virtualized systems will run into this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567399] Re: rhythmbox crashed with SIGSEGV in save_playlist()
Just tested rhythmbox from lucid-proposed. Well, rhythmbox still doesn't honour my playlist_format=audio/x-mpegurl line in the .is_audio_player file and keeps creating *.pls instead *.m3u playlists, but: The crasher is gone. Verified fixed. However, dropping files directly from playlists or the music library into a playlist on removable media does nothing. One must first drop the file onto the removable media and from there on the playlist on the removable media. Seems that the file must reside on the same media as the playlist. Alas, thanks guys. -- rhythmbox crashed with SIGSEGV in save_playlist() https://bugs.launchpad.net/bugs/567399 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 567399] [NEW] rhythmbox crashed with SIGSEGV in save_playlist()
Public bug reported: Binary package hint: rhythmbox Steps to reproduce: 1) Insert a SD-memory card containing the magic file .is_audio_player into the pc's card reader. 2) Wait till the removable device comes up in rhythmbox. 3) Create a playlist on the device. 4) Drag-and-drop an entry from a playlist residing already on the computer onto the newly created playlist. 5) Crash ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: rhythmbox 0.12.8-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Apr 20 20:08:12 2010 ExecutablePath: /usr/bin/rhythmbox ProcCmdline: rhythmbox ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc963f9dd68 save_playlist+504: mov 0x8(%rax),%rcx PC (0x7fc963f9dd68) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rcx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: save_playlist (source=value optimized out) at rb-generic-player-playlist-source.c:276 ?? () from /lib/libglib-2.0.so.0 g_main_context_dispatch () from /lib/libglib-2.0.so.0 ?? () from /lib/libglib-2.0.so.0 g_main_loop_run () from /lib/libglib-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in save_playlist() UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev sambashare tape vboxusers video ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lucid -- rhythmbox crashed with SIGSEGV in save_playlist() https://bugs.launchpad.net/bugs/567399 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 567399] Re: rhythmbox crashed with SIGSEGV in save_playlist()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/44912943/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/44912944/Disassembly.txt ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/44912945/GConfNonDefault.txt ** Attachment added: GstreamerVersions.txt http://launchpadlibrarian.net/44912946/GstreamerVersions.txt ** Attachment added: LogAlsaMixer.txt http://launchpadlibrarian.net/44912947/LogAlsaMixer.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/44912948/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/44912949/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/44912950/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/44912951/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/44912952/ThreadStacktrace.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/44912953/XorgLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/44912954/XsessionErrors.txt -- rhythmbox crashed with SIGSEGV in save_playlist() https://bugs.launchpad.net/bugs/567399 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 61235] Re: USB mass storage stops working after a while
Seeing this still on Karmic Beta:
Linux version 2.6.31-11-generic (bui...@yellow) (gcc version 4.4.1 (Ubuntu
4.4.1-4ubuntu4) ) #38-Ubuntu SMP Fri Oct 2 11:06:40 UTC 2009
It's a 1TB Toshiba USB drive and it also needs the afm. max_sectors
trick. However, i'm under the expression that the drive worked flawless
under Jaunty (since i managed to put a few hundred gigs onto it...).
~$ udevadm info --attribute-walk --name=/dev/sdg
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/host8/target8:0:0/8:0:0:0/block/sdg':
KERNEL==sdg
SUBSYSTEM==block
DRIVER==
ATTR{range}==16
ATTR{ext_range}==256
ATTR{removable}==0
ATTR{ro}==0
ATTR{size}==1953525168
ATTR{alignment_offset}==0
ATTR{capability}==52
ATTR{stat}== 380490 385 15773797 1487326065875 5634 8394456
264117604 759120 41284770
looking at parent device
'/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/host8/target8:0:0/8:0:0:0':
KERNELS==8:0:0:0
SUBSYSTEMS==scsi
DRIVERS==sd
ATTRS{device_blocked}==0
ATTRS{type}==0
ATTRS{scsi_level}==3
ATTRS{vendor}==TOSHIBA
ATTRS{model}==USB 3.5-HDD
ATTRS{rev}==100
ATTRS{state}==running
ATTRS{timeout}==30
ATTRS{iocounterbits}==32
ATTRS{iorequest_cnt}==0x6cfb7
ATTRS{iodone_cnt}==0x6cfb7
ATTRS{ioerr_cnt}==0x8
ATTRS{modalias}==scsi:t-0x00
ATTRS{evt_media_change}==0
ATTRS{queue_depth}==1
ATTRS{queue_type}==none
ATTRS{max_sectors}==128
looking at parent device
'/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/host8/target8:0:0':
KERNELS==target8:0:0
SUBSYSTEMS==scsi
DRIVERS==
looking at parent device
'/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/host8':
KERNELS==host8
SUBSYSTEMS==scsi
DRIVERS==
looking at parent device '/devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0':
KERNELS==1-3:1.0
SUBSYSTEMS==usb
DRIVERS==usb-storage
ATTRS{bInterfaceNumber}==00
ATTRS{bAlternateSetting}== 0
ATTRS{bNumEndpoints}==02
ATTRS{bInterfaceClass}==08
ATTRS{bInterfaceSubClass}==06
ATTRS{bInterfaceProtocol}==50
ATTRS{modalias}==usb:v0930p0B09d0112dc00dsc00dp00ic08isc06ip50
ATTRS{supports_autosuspend}==0
ATTRS{interface}==Bulk Only Interface
looking at parent device '/devices/pci:00/:00:12.2/usb1/1-3':
KERNELS==1-3
SUBSYSTEMS==usb
DRIVERS==usb
ATTRS{configuration}==Bulk Only Configuration
ATTRS{bNumInterfaces}== 1
ATTRS{bConfigurationValue}==1
ATTRS{bmAttributes}==c0
ATTRS{bMaxPower}== 2mA
ATTRS{urbnum}==3077626
ATTRS{idVendor}==0930
ATTRS{idProduct}==0b09
ATTRS{bcdDevice}==0112
ATTRS{bDeviceClass}==00
ATTRS{bDeviceSubClass}==00
ATTRS{bDeviceProtocol}==00
ATTRS{bNumConfigurations}==1
ATTRS{bMaxPacketSize0}==64
ATTRS{speed}==480
ATTRS{busnum}==1
ATTRS{devnum}==2
ATTRS{version}== 2.00
ATTRS{maxchild}==0
ATTRS{quirks}==0x0
ATTRS{authorized}==1
ATTRS{manufacturer}==TOSHIBA
ATTRS{product}==USB 3.5-HDD
ATTRS{serial}==000FF49a
looking at parent device '/devices/pci:00/:00:12.2/usb1':
KERNELS==usb1
SUBSYSTEMS==usb
DRIVERS==usb
ATTRS{configuration}==
ATTRS{bNumInterfaces}== 1
ATTRS{bConfigurationValue}==1
ATTRS{bmAttributes}==e0
ATTRS{bMaxPower}== 0mA
ATTRS{urbnum}==67
ATTRS{idVendor}==1d6b
ATTRS{idProduct}==0002
ATTRS{bcdDevice}==0206
ATTRS{bDeviceClass}==09
ATTRS{bDeviceSubClass}==00
ATTRS{bDeviceProtocol}==00
ATTRS{bNumConfigurations}==1
ATTRS{bMaxPacketSize0}==64
ATTRS{speed}==480
ATTRS{busnum}==1
ATTRS{devnum}==1
ATTRS{version}== 2.00
ATTRS{maxchild}==6
ATTRS{quirks}==0x0
ATTRS{authorized}==1
ATTRS{manufacturer}==Linux 2.6.31-11-generic ehci_hcd
ATTRS{product}==EHCI Host Controller
ATTRS{serial}==:00:12.2
ATTRS{authorized_default}==1
looking at parent device '/devices/pci:00/:00:12.2':
KERNELS==:00:12.2
SUBSYSTEMS==pci
DRIVERS==ehci_hcd
ATTRS{vendor}==0x1002
ATTRS{device}==0x4396
ATTRS{subsystem_vendor}==0x1849
ATTRS{subsystem_device}==0x4396
ATTRS{class}==0x0c0320
ATTRS{irq}==17
ATTRS{local_cpus}==,0003
ATTRS{local_cpulist}==0-1
ATTRS{modalias}==pci:v1002d4396sv1849sd4396bc0Csc03i20
ATTRS{numa_node}==0
ATTRS{broken_parity_status}==0
ATTRS{msi_bus}==
ATTRS{companion}==
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
--
USB mass storage stops working after a while
[Bug 222153] Re: Nokia 6233 usb-storage won't work
Bug seems to be fixed in Jaunty and can be closed. -- Nokia 6233 usb-storage won't work https://bugs.launchpad.net/bugs/222153 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 331691] Re: Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands.
One last feedback from me: At least on my motherboard (Asrock A770Crossfire) the reason for the missing _PSS tables is solved: The BIOS disables C'n'Q *silently* (even when the setting is set to Enabled) if memory modules from a certain vendor are used. In my case it were those: A-Data AD281GOU2 2x1024MB Kit A-DATA DDR2 800MHz CL5 If i use DIMMs from another manufacturer C'n'Q works. However, i still think that's a BIOS bug, since all DIMMs i use are JEDEC-compliant, CL5, 1,8V so no fancy overclocking/overvoltage modules. And for the decision to silently ignore a user setting without printing a message at POST the BIOS programmer needs a visit with a cluebat. -- Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands. https://bugs.launchpad.net/bugs/331691 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 331691] Re: Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands.
Well, i've entered the following bug in the kernel bug tracker: http://bugzilla.kernel.org/show_bug.cgi?id=12948 It was confirmed that the Asrock BIOS doesn't contained the required _PSS tables - which is an error on their part - nothing Linux can do about. The _PSS tables are needed for powernow-k8 in case of a multi- core CPU. So, i emailed Asrock about the problem. Guess what they'll tell you: regarding Linux: have to say sorry, ASRock does not test or support the use of Linux OS. We cannot guarantee that ASRock motherboards will work with Linux without problems. So, better refrain from Asrock for future buys. I surely won't recommend them to anyone in future. -- Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands. https://bugs.launchpad.net/bugs/331691 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 331691] Re: Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands.
I'm seeing the same on Jaunty Kernel version 2.6.28-11-generic since i swapped my Asus M2A-VM Mobo with an Asrock A770Crossfire Mobo (newest BIOS P1.20, C'n'Q enabled in the BIOS). Attaching the output of dmidecode and my dmesg. ** Attachment added: dbg.tgz http://launchpadlibrarian.net/24301060/dbg.tgz -- Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands. https://bugs.launchpad.net/bugs/331691 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 331691] Re: Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands.
And seems we have the same on another Asrock Mobo: https://bugs.launchpad.net/ubuntu/+bug/347002 -- Error on Boot: [Firmware Bug]:Powernow-k8: Your BIOS does not provide ACPI_PSS objects in a way that Linux understands. https://bugs.launchpad.net/bugs/331691 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 222153] [NEW] Nokia 6233 usb-storage won't work
Public bug reported: Binary package hint: linux-image-2.6.24-16-generic Usb-storage in the Hardy Heron kernel image doesn't work for the Nokia 6233. This is IMHO a re-apperance of bug #102965. I tracked down the issue to the following entry in drivers/usb/storage/unusual_devs.h: /* Reported by Manuel Osdoba [EMAIL PROTECTED] */ UNUSUAL_DEV( 0x0421, 0x0492, 0x0452, 0x0452, Nokia, Nokia 6233, US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_MAX_SECTORS_64 ), As my Cellphone has a newer firmware revision, the entry isn't considered. Changing that to UNUSUAL_DEV( 0x0421, 0x0492, 0x, 0x, Nokia, Nokia 6233, US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_MAX_SECTORS_64 ), and recompiling the kernel fixes the problem (the range from 0x0 ... 0x might be too radical, though). The relevant lsusb -v output: Bus 003 Device 003: ID 0421:0492 Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x0492 bcdDevice5.60 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower8mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Best regards, Peter ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Nokia 6233 usb-storage won't work https://bugs.launchpad.net/bugs/222153 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
