xbmc unmounts all my device and shuts down the network

This forum is for topics specific to the Raspberry Pi and Arch Linux ARM
Topic locked

xbmc unmounts all my device and shuts down the network

Postby studioai » Thu Jul 17, 2014 2:56 am

Hi,

I installed xbmc-rbp (13.1.2)

When I run xbmc, I get the log below

please, check the symptom on my TV = http://youtu.be/ipZ2dupxoA0

    Message on screen: Pulse-Eight CEC adaptor - Configration updated
    Message on screen: Successfully removed device (this was not I meant)
    Message on screen: Mounted removable harddrive - hdd (already mounted by fstab)
    and the screen is cracked when I enter the sub menues

Does anyone have a clue?

Thanks
$this->bbcode_second_pass_code('', '
---------------------------------------------log------------------------------------------
Jan 1 15:40:20 alarmpi kernel: irq 32: nobody cared (try booting with the "irqpoll" option)
Jan 1 15:40:20 alarmpi kernel: CPU: 0 PID: 862 Comm: xbmc.bin Not tainted 3.12.20-4-ARCH #1
Jan 1 15:40:20 alarmpi kernel: [<c0013a1c>] (unwind_backtrace+0x0/0xec) from [<c0011800>] (show_stack+0x10/0x14)
Jan 1 15:40:20 alarmpi kernel: [<c0011800>] (show_stack+0x10/0x14) from [<c006202c>] (__report_bad_irq.isra.6+0x20/0xec)
Jan 1 15:40:20 alarmpi kernel: [<c006202c>] (__report_bad_irq.isra.6+0x20/0xec) from [<c00622cc>] (note_interrupt+0x15c/0x220)
Jan 1 15:40:20 alarmpi kernel: [<c00622cc>] (note_interrupt+0x15c/0x220) from [<c0060398>] (handle_irq_event_percpu+0x114/0x2b8)
Jan 1 15:40:20 alarmpi kernel: [<c0060398>] (handle_irq_event_percpu+0x114/0x2b8) from [<c006058c>] (handle_irq_event+0x50/0x78)
Jan 1 15:40:20 alarmpi kernel: [<c006058c>] (handle_irq_event+0x50/0x78) from [<c006298c>] (handle_level_irq+0x88/0x10c)
Jan 1 15:40:20 alarmpi kernel: [<c006298c>] (handle_level_irq+0x88/0x10c) from [<c005fbfc>] (generic_handle_irq+0x28/0x40)
Jan 1 15:40:20 alarmpi kernel: [<c005fbfc>] (generic_handle_irq+0x28/0x40) from [<c000e98c>] (handle_IRQ+0x30/0x84)
Jan 1 15:40:20 alarmpi kernel: [<c000e98c>] (handle_IRQ+0x30/0x84) from [<c05cf9d4>] (__irq_svc+0x34/0xc8)
Jan 1 15:40:20 alarmpi kernel: [<c05cf9d4>] (__irq_svc+0x34/0xc8) from [<c00277c8>] (__do_softirq+0x80/0x2c8)
Jan 1 15:40:20 alarmpi kernel: [<c00277c8>] (__do_softirq+0x80/0x2c8) from [<c0027ab0>] (do_softirq+0x5c/0x64)
Jan 1 15:40:20 alarmpi kernel: [<c0027ab0>] (do_softirq+0x5c/0x64) from [<c0027d60>] (irq_exit+0xa8/0xf0)
Jan 1 15:40:20 alarmpi kernel: [<c0027d60>] (irq_exit+0xa8/0xf0) from [<c000e990>] (handle_IRQ+0x34/0x84)
Jan 1 15:40:20 alarmpi kernel: [<c000e990>] (handle_IRQ+0x34/0x84) from [<c05cf9d4>] (__irq_svc+0x34/0xc8)
Jan 1 15:40:20 alarmpi kernel: [<c05cf9d4>] (__irq_svc+0x34/0xc8) from [<c03f3060>] (remote_event_signal+0x10/0x40)
Jan 1 15:40:20 alarmpi kernel: [<c03f3060>] (remote_event_signal+0x10/0x40) from [<c03ea69c>] (queue_message+0x434/0x9bc)
Jan 1 15:40:20 alarmpi kernel: [<c03ea69c>] (queue_message+0x434/0x9bc) from [<c03ecb04>] (vchiq_queue_message+0xf4/0x12c)
Jan 1 15:40:20 alarmpi kernel: [<c03ecb04>] (vchiq_queue_message+0xf4/0x12c) from [<c03f0c60>] (vchiq_ioctl+0x530/0x160c)
Jan 1 15:40:20 alarmpi kernel: [<c03f0c60>] (vchiq_ioctl+0x530/0x160c) from [<c0116404>] (do_vfs_ioctl+0x404/0x5f8)
Jan 1 15:40:20 alarmpi kernel: [<c0116404>] (do_vfs_ioctl+0x404/0x5f8) from [<c0116630>] (SyS_ioctl+0x38/0x64)
Jan 1 15:40:20 alarmpi kernel: [<c0116630>] (SyS_ioctl+0x38/0x64) from [<c000e0e0>] (ret_fast_syscall+0x0/0x30)
Jan 1 15:40:20 alarmpi kernel: handlers:
Jan 1 15:40:20 alarmpi kernel: [<c04344b4>] dwc_otg_common_irq
Jan 1 15:40:20 alarmpi kernel: [<c04418fc>] dwc_otg_pcd_irq
Jan 1 15:40:20 alarmpi kernel: [<c04253ac>] usb_hcd_irq
Jan 1 15:40:20 alarmpi kernel: Disabling IRQ #32
Jan 1 15:40:20 alarmpi kernel: ERROR::dwc_otg_hcd_urb_enqueue:505: Not connected\x0a
Jan 1 15:40:20 alarmpi kernel: ERROR::dwc_otg_hcd_urb_enqueue:505: Not connected\x0a
Jan 1 15:40:20 alarmpi kernel: ERROR::dwc_otg_hcd_urb_enqueue:505: Not connected\x0a
Jan 1 15:40:20 alarmpi kernel: usb 1-1: USB disconnect, device number 2
Jan 1 15:40:20 alarmpi kernel: usb 1-1.1: USB disconnect, device number 3
Jan 1 15:40:20 alarmpi kernel: smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Jan 1 15:40:20 alarmpi kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan 1 15:40:20 alarmpi kernel: usblp0: removed
Jan 1 15:40:20 alarmpi kernel: usblp: can't set desired altsetting 0 on interface 1
Jan 1 15:40:21 alarmpi kernel: usb 1-1.2: USB disconnect, device number 4
Jan 1 15:40:21 alarmpi kernel: usb 1-1.3: USB disconnect, device number 5
Jul 17 11:38:42 alarmpi dhcpcd[285]: eth0: carrier lost
Jul 17 11:38:42 alarmpi avahi-daemon[134]: Interface eth0.IPv4 no longer relevant for mDNS.
Jul 17 11:38:42 alarmpi avahi-daemon[134]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.219.12.
Jul 17 11:38:42 alarmpi avahi-daemon[134]: Withdrawing address record for 192.168.219.12 on eth0.
Jul 17 11:38:42 alarmpi avahi-daemon[134]: Withdrawing workstation service for eth0.
Jul 17 11:38:42 alarmpi dhcpcd[285]: eth0: deleting route to 192.168.219.0/24
Jul 17 11:38:42 alarmpi dhcpcd[285]: eth0: deleting default route via 192.168.219.1
Jul 17 11:38:42 alarmpi dhcpcd[285]: script_runreason: /usr/lib/dhcpcd/dhcpcd-run-hooks: Terminated
Jul 17 11:38:42 alarmpi systemd[1]: Stopping Automatic wired network connection using netctl profiles...
Jul 17 11:38:43 alarmpi systemd[1]: Stopping Local File Systems.
Jul 17 11:38:43 alarmpi systemd[1]: Stopped target Local File Systems.
Jul 17 11:38:43 alarmpi systemd[1]: Unmounting /media/hdd...
Jul 17 11:38:43 alarmpi systemd[1]: Service printer.target is not needed anymore. Stopping.
Jul 17 11:38:43 alarmpi systemd[1]: Stopping Printer.
Jul 17 11:38:43 alarmpi systemd[1]: Stopped target Printer.
Jul 17 11:38:43 alarmpi systemd[1]: media-hdd.mount mount process exited, code=exited status=32
Jul 17 11:38:43 alarmpi systemd[1]: Failed unmounting /media/hdd.
Jul 17 11:38:44 alarmpi ifplugd[132]: Using detection mode: IFF_RUNNING
Jul 17 11:38:44 alarmpi ifplugd[132]: Link beat lost.
Jul 17 11:38:44 alarmpi ifplugd[132]: Executing '/etc/ifplugd/netctl.action eth0 down'.
Jul 17 11:38:44 alarmpi colord[159]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Jul 17 11:38:44 alarmpi colord[159]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Jul 17 11:38:44 alarmpi colord[159]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Jul 17 11:38:44 alarmpi colord[159]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Jul 17 11:38:44 alarmpi colord[159]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Jul 17 11:38:44 alarmpi umount[932]: umount: /media/hdd: target is busy
Jul 17 11:38:44 alarmpi umount[932]: (In some cases useful info about processes that
Jul 17 11:38:44 alarmpi umount[932]: use the device is found by lsof(8) or fuser(1).)
Jul 17 11:38:44 alarmpi ifplugd[132]: client: Stopping network profile 'eth0'...
Jul 17 11:38:44 alarmpi dhcpcd[993]: sending signal TERM to pid 285
Jul 17 11:38:44 alarmpi dhcpcd[993]: waiting for pid 285 to exit
Jul 17 11:38:44 alarmpi dhcpcd[285]: eth0: removing interface
Jul 17 11:38:46 alarmpi dhcpcd[285]: exited
Jul 17 11:38:46 alarmpi ifplugd[132]: client: /usr/lib/network/network: line 37: /sys/class/net/eth0/flags: No such file or directory
Jul 17 11:38:46 alarmpi ifplugd[132]: client: Stopped network profile 'eth0'
Jul 17 11:38:46 alarmpi ifplugd[132]: Program executed successfully.
Jul 17 11:38:46 alarmpi ifplugd[132]: Exiting.
Jul 17 11:38:46 alarmpi systemd[1]: Stopped Automatic wired network connection using netctl profiles.
')
Last edited by studioai on Fri Jul 18, 2014 6:33 am, edited 4 times in total.
studioai
 
Posts: 5
Joined: Thu Jul 17, 2014 2:46 am
Top

Re: xbmc unmounts all my device and shuts down the network

Postby WarheadsSE » Thu Jul 17, 2014 1:14 pm

No, xbmc just happens to be running. Reading this log, your USB host controller took a crap, and reset the entire bus & hub.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: xbmc unmounts all my device and shuts down the network

Postby studioai » Thu Jul 17, 2014 2:12 pm

But It never happens before I run xbmc, and after that xbmc is still running
studioai
 
Posts: 5
Joined: Thu Jul 17, 2014 2:46 am
Top

Re: xbmc unmounts all my device and shuts down the network

Postby WarheadsSE » Thu Jul 17, 2014 2:37 pm

Right, but that doesn't mean that XBMC is directly at fault. That leads to the conclusion that it is causing the condition that results in this fault, not that XBMC itself is the cause/fault itself.

This line right here is very telling:
$this->bbcode_second_pass_code('', 'Jan 1 15:40:20 alarmpi kernel: usb 1-1: USB disconnect, device number 2')
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: xbmc unmounts all my device and shuts down the network

Postby studioai » Mon Jul 21, 2014 11:14 am

I change a power cable and a USB power supply. And It's done thanks for your advice
studioai
 
Posts: 5
Joined: Thu Jul 17, 2014 2:46 am
Top
Topic locked

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 82 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group    © Arch Linux ARM