[Bug 660783] Re: after suspend: trackpoint and touchpad unresponsive for 5-10 sec
I'm experiencing this intermittently as well, on a Lenovo T61 (hardware info attached), in addition to #659712. ** Attachment added: "hardware.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/660783/+attachment/1773098/+files/hardware.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660783 Title: after suspend: trackpoint and touchpad unresponsive for 5-10 sec -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 460857] Re: ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
I'm seeing behavior like this too. I'm running the 32-bit version of 10.10 on an Acer Aspire X3400, with kernel version: 2.6.35-23-generic #41-Ubuntu SMP and an nVidia USB controller: lspci | grep USB 00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) 00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) The kernel log looks like this: When the device is inserted: [ 263.624073] usb 3-4: new full speed USB device using ohci_hcd and address 5 [ 263.858104] ftdi_sio 3-4:1.0: FTDI USB Serial Device converter detected [ 263.858164] usb 3-4: Detected FT232RL [ 263.858170] usb 3-4: Number of endpoints 2 [ 263.858176] usb 3-4: Endpoint 1 MaxPacketSize 64 [ 263.858181] usb 3-4: Endpoint 2 MaxPacketSize 64 [ 263.858186] usb 3-4: Setting MaxPacketSize 64 [ 263.861051] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB0 The FTDI chip works for a while, then stops transmitting data. When I try to close our java-based program that is using USB (ReplicatorG), I get this: [ 720.488759] INFO: task java:2099 blocked for more than 120 seconds. [ 720.488768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 720.488775] java D f388fe1c 0 2099 1989 0x [ 720.488788] f388fe2c 00200086 0002 f388fe1c c05d89e0 c08c3700 c08c3700 [ 720.488804] 45cf69b9 007f c08c3700 c08c3700 45ced064 007f c08c3700 [ 720.488818] c08c3700 f4434c20 0001 f6453780 f6453788 f388fe34 f388fe54 c0471f7d [ 720.488832] Call Trace: [ 720.488849] [] usb_kill_urb+0x6d/0xa0 [ 720.488861] [] ? autoremove_wake_function+0x0/0x50 [ 720.488871] [] usb_start_wait_urb+0xac/0xc0 [ 720.40] [] usb_control_msg+0xc4/0x130 [ 720.488890] [] ? __netif_receive_skb+0x33f/0x530 [ 720.488903] [] ftdi_tiocmget+0xda/0x1ac [ftdi_sio] [ 720.488916] [] serial_tiocmget+0x3b/0x80 [usbserial] [ 720.488925] [] tty_ioctl+0x2a6/0x620 [ 720.488933] [] ? copy_to_user+0x39/0x130 [ 720.488941] [] vfs_ioctl+0x32/0xb0 [ 720.488948] [] ? tty_ioctl+0x0/0x620 [ 720.488955] [] do_vfs_ioctl+0x79/0x2d0 [ 720.488961] [] sys_ioctl+0x67/0x80 [ 720.488970] [] syscall_call+0x7/0xb [ 840.488110] INFO: task java:2099 blocked for more than 120 seconds. [ 840.488119] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Kendrik's proposed workaround in #43 seems to recover a little better, but eventually this happens again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/460857 Title: ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214385] Re: [hardy] f-spot SIGSEGV at startup
I spoke too soon; f-spot started and ran correctly once. It crashed on shutdown, then refused to start again, even after resetting the system. The crash at startup appears to be the same as before. -- [hardy] f-spot SIGSEGV at startup https://bugs.launchpad.net/bugs/214385 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 214385] Re: [hardy] f-spot SIGSEGV at startup
After updating the system today (April 9th), the issue seems to be resolved. The version info for f-spot seems to be the same, so it must have been an issue with a different package. Question: If a bug I have reported goes away, should I change its status? -- [hardy] f-spot SIGSEGV at startup https://bugs.launchpad.net/bugs/214385 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 214385] Re: [hardy] f-spot SIGSEGV at startup
** Attachment added: "Crash output" http://launchpadlibrarian.net/13270113/f-spot.txt -- [hardy] f-spot SIGSEGV at startup https://bugs.launchpad.net/bugs/214385 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 214385] [NEW] [hardy] f-spot SIGSEGV at startup
Public bug reported: Binary package hint: f-spot f-spot has refused to start since an update late last week (unfortunately, I don't remember which one). I tried re-naming the .gnome2/f-spot config directory, but this did not change anything. The error message I get when running 'f-spot --debug &> f-spot.txt' is attached. 1. Ubuntu release $ lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 2. Package version $ apt-cache policy f-spot f-spot: Installed: 0.4.2-1ubuntu2 Candidate: 0.4.2-1ubuntu2 Version table: *** 0.4.2-1ubuntu2 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- [hardy] f-spot SIGSEGV at startup https://bugs.launchpad.net/bugs/214385 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
