Open GoogleCodeExporter opened 8 years ago
Looks like a kernel issue to me, boblightd just opens a socket for clients and
writes its output to the serial port, it shouldn't have this much influence on
the rest of the system even if it would freeze.
Original comment by bob.loo...@gmail.com
on 11 Oct 2012 at 10:29
OK, now I tried the following:
I completely reinstalled Ubuntu 12.04.1 (minimal), which currently uses Linux
3.2.0-32-generic #51-Ubuntu SMP
The periodical crashes seems to be gone, but now boblightd will not exit when
sending sigint. Here is the last debug-output:
(SignalHandler) caught SIGINT
(CClientsHandler::GetReadableFd)select() Interrupted system call
(main) signaling devices to stop
(CClientsHandler::Cleanup) disconnecting clients
(CClientsHandler::Cleanup) closing listening socket
(CClientsHandler::Cleanup) clients handler stopped
(main) waiting for devices to stop
/dev/ttyUSB0 write: 5a b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 a5
This can now be found in Syslog:
Oct 28 16:29:28 hostname kernel: [243360.480133] INFO: task boblightd:2176
blocked for more than 120 seconds.
Oct 28 16:29:28 hostname kernel: [243360.480142] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 28 16:29:28 hostname kernel: [243360.480149] boblightd D
ffffffff81806200 0 2176 2165 0x00000000
Oct 28 16:29:28 hostname kernel: [243360.480161] ffff880067617c98
0000000000000082 ffff880067617c48 ffffffff8130d547
Oct 28 16:29:28 hostname kernel: [243360.480173] ffff880067617fd8
ffff880067617fd8 ffff880067617fd8 00000000000137c0
Oct 28 16:29:28 hostname kernel: [243360.480184] ffff880074331700
ffff8800725b0000 ffff880067617ca8 ffff8800733d6600
Oct 28 16:29:28 hostname kernel: [243360.480193] Call Trace:
Oct 28 16:29:28 hostname kernel: [243360.480210] [<ffffffff8130d547>] ?
kobject_put+0x27/0x60
Oct 28 16:29:28 hostname kernel: [243360.480222] [<ffffffff81658f2f>]
schedule+0x3f/0x60
Oct 28 16:29:28 hostname kernel: [243360.480231] [<ffffffff81494ffd>]
usb_kill_urb.part.4+0x5d/0xa0
Oct 28 16:29:28 hostname kernel: [243360.480241] [<ffffffff8108ab80>] ?
add_wait_queue+0x60/0x60
Oct 28 16:29:28 hostname kernel: [243360.480248] [<ffffffff81495071>]
usb_kill_urb+0x31/0x40
Oct 28 16:29:28 hostname kernel: [243360.480273] [<ffffffffa0120f20>]
generic_cleanup+0x50/0xe0 [usbserial]
Oct 28 16:29:28 hostname kernel: [243360.480288] [<ffffffffa0121053>]
usb_serial_generic_close+0x23/0x50 [usbserial]
Oct 28 16:29:28 hostname kernel: [243360.480301] [<ffffffffa013b259>]
ftdi_close+0x39/0x70 [ftdi_sio]
Oct 28 16:29:28 hostname kernel: [243360.480313] [<ffffffffa011e029>]
serial_down+0x29/0x30 [usbserial]
Oct 28 16:29:28 hostname kernel: [243360.480322] [<ffffffff813c3f02>]
tty_port_shutdown+0x62/0x70
Oct 28 16:29:28 hostname kernel: [243360.480330] [<ffffffff813c4a0c>]
tty_port_close+0x2c/0x60
Oct 28 16:29:28 hostname kernel: [243360.480342] [<ffffffffa011ecc2>]
serial_close+0x42/0x80 [usbserial]
Oct 28 16:29:28 hostname kernel: [243360.480352] [<ffffffff813bc016>]
tty_release+0x166/0x5c0
Oct 28 16:29:28 hostname kernel: [243360.480361] [<ffffffff8104df53>] ?
__wake_up+0x53/0x70
Oct 28 16:29:28 hostname kernel: [243360.480369] [<ffffffff81055fad>] ?
set_next_entity+0xad/0xd0
Oct 28 16:29:28 hostname kernel: [243360.480378] [<ffffffff811794ee>]
__fput+0xbe/0x210
Oct 28 16:29:28 hostname kernel: [243360.480385] [<ffffffff81179665>]
fput+0x25/0x30
Oct 28 16:29:28 hostname kernel: [243360.480392] [<ffffffff81176206>]
filp_close+0x66/0x90
Oct 28 16:29:28 hostname kernel: [243360.480399] [<ffffffff811762e2>]
sys_close+0xb2/0x120
Oct 28 16:29:28 hostname kernel: [243360.480407] [<ffffffff81663442>]
system_call_fastpath+0x16/0x1b
Oct 28 16:29:28 hostname kernel: [243360.480420] INFO: task sshd:4034 blocked
for more than 120 seconds.
Oct 28 16:29:28 hostname kernel: [243360.480425] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 28 16:29:28 hostname kernel: [243360.480431] sshd D
ffffffff81806200 0 4034 994 0x00000000
Oct 28 16:29:28 hostname kernel: [243360.480441] ffff88002b43fb28
0000000000000082 ffffffff8118af00 00000000000000db
Oct 28 16:29:28 hostname kernel: [243360.480451] ffff88002b43ffd8
ffff88002b43ffd8 ffff88002b43ffd8 00000000000137c0
Oct 28 16:29:28 hostname kernel: [243360.480461] ffffffff81c0d020
ffff88006017dc00 ffff880000000000 ffffffff81c726e0
Oct 28 16:29:28 hostname kernel: [243360.480469] Call Trace:
Oct 28 16:29:28 hostname kernel: [243360.480478] [<ffffffff8118af00>] ?
poll_freewait+0xe0/0xe0
Oct 28 16:29:28 hostname kernel: [243360.480488] [<ffffffff81658f2f>]
schedule+0x3f/0x60
Oct 28 16:29:28 hostname kernel: [243360.480495] [<ffffffff81659d37>]
__mutex_lock_slowpath+0xd7/0x150
That's all, nothing more, waited about 10 min's, nothing happened... In this
situation I again can't login with SSH as mentioned above, no USB Device works
any more, I have to hard reset the machine...
I use a SEDU-ambilight from here: www.sedu-board.de together with XBMC and the
boblight-addon.
The top of the boblight.conf is this:
[global]
interface 127.0.0.1
port 19333
[device]
name ambilight
output /dev/ttyUSB0
channels 234
type momo
interval 10000
prefix 5A B0
postfix A5
rate 500000
debug on
Original comment by borin1...@googlemail.com
on 28 Oct 2012 at 3:48
I'm having the same problem with gentoo (kernel 3.0.4) and with ubuntu 12.04.1
(kernel 3.2.0-32).
Is there any news about it?
Original comment by satguber...@googlemail.com
on 3 Nov 2012 at 12:38
I suggest reporting this to the linux kernel developers, a process should not
be able to hang the kernel.
Original comment by bob.loo...@gmail.com
on 3 Nov 2012 at 7:04
I filed a Kernel-Bug Report here:
https://bugzilla.kernel.org/show_bug.cgi?id=50121
let's see their reaction...
@satguber: What kind of hardware do you have? A SEDU Board, too?
Original comment by borin1...@googlemail.com
on 7 Nov 2012 at 7:22
Thank's for filling the report.
I have a sedu board too.
Let's hope the there will be a solution soon...
Original comment by satguber...@googlemail.com
on 9 Nov 2012 at 3:14
OK, I think I figured out what is responsible:
When I had this behaviour the SEDU-Box was connected to an USB1.1 Port ...
making sure that it is connected to an USB2.0 Port seems to solve the
problem....
Original comment by borin1...@googlemail.com
on 15 Nov 2012 at 8:56
The connection to an USB 2.0 port works for you?
On my systems the problem is still there...
Original comment by satguber...@googlemail.com
on 21 Nov 2012 at 5:22
yes, USB2.0 works fine for me
Original comment by borin1...@googlemail.com
on 21 Nov 2012 at 5:27
Original issue reported on code.google.com by
borin1...@googlemail.com
on 11 Oct 2012 at 9:15