pulseaudio verursacht sleep-modus?

21/08/2009 - 16:29 von Chris | Report spam
Moin,
irgendwie hat sich einer meiner Rechner von selbst in den Standbymodus (oder sowas) geworfen.
Unten anbei die Logs. Kann auch sein dass irgendjemand irgendwie den Modus getriggert hat, aber
irgendwie startet die Initiierung ja mit dem Aufruf der pulseaudio-Fehlermeldung.
Normal oder Bug?
Thx,
Chris

Aug 4 13:07:16 tmgf_epi_514 ntpd[2269]: kernel time sync status change 0001
Aug 4 13:22:32 tmgf_epi_514 pulseaudio[19085]: pid.c: Failed to open PID file '/home/admin/.pulse/61f90e20f39bfd5ec608aa004684d52f:runtime/pid': Datei oder Verzeichnis nicht gefunden
Aug 4 13:22:32 tmgf_epi_514 pulseaudio[19085]: pid.c: Failed to open PID file '/home/admin/.pulse/61f90e20f39bfd5ec608aa004684d52f:runtime/pid': Datei oder Verzeichnis nicht gefunden
Aug 4 13:22:42 tmgf_epi_514 NetworkManager: <info> Sleeping...
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): now unmanaged
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): device state change: 8 -> 1
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): deactivating device (reason: 37).
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): cleaning up...
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): taking down device.
Aug 4 13:22:43 tmgf_epi_514 NetworkManager: <info> (eth0): carrier now OFF (device state 1)
Aug 4 13:22:43 tmgf_epi_514 dnsmasq[2675]: no servers found in /etc/resolv.conf, will retry
Aug 4 13:22:43 tmgf_epi_514 avahi-daemon[2588]: Withdrawing address record for 192.168.2.42 on eth0.
Aug 4 13:22:43 tmgf_epi_514 avahi-daemon[2588]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.42.
Aug 4 13:22:43 tmgf_epi_514 avahi-daemon[2588]: Interface eth0.IPv4 no longer relevant for mDNS.
Aug 4 13:22:43 tmgf_epi_514 avahi-daemon[2588]: Withdrawing address record for fe80::211:43ff:fe05:b9d6 on eth0.
Aug 4 13:22:44 tmgf_epi_514 ntpd[2269]: Deleting interface #3 eth0, fe80::211:43ff:fe05:b9d6#123, interface stats: received=0, sent=0, dropped=0, active_time739897 secs
Aug 4 13:22:44 tmgf_epi_514 ntpd[2269]: Deleting interface #26 eth0, 192.168.2.42#123, interface stats: received446, sent!407, dropped=0, active_time%18119 secs
Aug 4 13:22:46 tmgf_epi_514 klogd: irq 16: nobody cared (try booting with the "irqpoll" option)
Aug 4 13:22:46 tmgf_epi_514 klogd: Pid: 0, comm: swapper Tainted: P W 2.6.27.15-170.2.24.fc10.x86_64 #1
Aug 4 13:22:46 tmgf_epi_514 klogd:
Aug 4 13:22:46 tmgf_epi_514 klogd: Call Trace:
Aug 4 13:22:46 tmgf_epi_514 klogd: <IRQ> [<ffffffff810834df>] __report_bad_irq+0x38/0x7c
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff8108372b>] note_interrupt+0x208/0x26d
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff81083e58>] handle_fasteoi_irq+0xbb/0xeb
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff810130ce>] do_IRQ+0xf7/0x169
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff81010963>] ret_from_intr+0x0/0x2e
Aug 4 13:22:46 tmgf_epi_514 klogd: <EOI> [<ffffffff8102571e>] ? native_safe_halt+0x6/0x8
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff810172fb>] ? need_resched+0x1e/0x28
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff810173e0>] ? default_idle+0x2a/0x4c
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff8100f2a7>] ? cpu_idle+0xb2/0x10b
Aug 4 13:22:46 tmgf_epi_514 klogd: [<ffffffff813204dd>] ? rest_init+0x61/0x63
Aug 4 13:22:46 tmgf_epi_514 klogd:
Aug 4 13:22:46 tmgf_epi_514 klogd: handlers:
Aug 4 13:22:47 tmgf_epi_514 klogd: [<ffffffff8123c26a>] (usb_hcd_irq+0x0/0xb3)
Aug 4 13:22:47 tmgf_epi_514 klogd: [<ffffffff8123c26a>] (usb_hcd_irq+0x0/0xb3)
Aug 4 13:22:47 tmgf_epi_514 klogd: [<ffffffffa010087d>] (irq_handler+0x0/0x3ab [firewire_ohci])
Aug 4 13:22:47 tmgf_epi_514 klogd: [<ffffffffa05959b5>] (nv_kern_isr+0x0/0x8d [nvidia])
Aug 4 13:22:47 tmgf_epi_514 klogd: Disabling IRQ #16
Aug 21 16:19:35 tmgf_epi_514 klogd: PM: Syncing filesystems ... done.
Aug 21 16:19:44 tmgf_epi_514 klogd: Freezing user space processes ... (elapsed 0.05 seconds) done.
Aug 21 16:19:44 tmgf_epi_514 klogd: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Aug 21 16:19:44 tmgf_epi_514 klogd: Suspending console(s) (use no_console_suspend to debug)
Aug 21 16:19:44 tmgf_epi_514 klogd: sd 4:0:2:0: [sdc] Synchronizing SCSI cache
Aug 21 16:19:44 tmgf_epi_514 klogd: sd 4:0:1:0: [sdb] Synchronizing SCSI cache
Aug 21 16:19:44 tmgf_epi_514 klogd: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Aug 21 16:19:44 tmgf_epi_514 klogd: serial 00:0b: disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: serial 00:0a: disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: parport_pc 00:09: disabled
Aug 21 16:19:44 tmgf_epi_514 gdm-simple-greeter[21980]: WARNING: Couldn't suspend: Message did not receive a reply (timeout by message bus)
Aug 21 16:19:44 tmgf_epi_514 klogd: NVRM: RmPowerManagement: 4
Aug 21 16:19:44 tmgf_epi_514 klogd: e1000 0000:03:0e.0: PME# enabled
Aug 21 16:19:44 tmgf_epi_514 klogd: e1000 0000:03:0e.0: PME# enabled
Aug 21 16:19:44 tmgf_epi_514 klogd: e1000 0000:03:0e.0: PCI INT A disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: aic79xx 0000:02:0e.0: PCI INT A disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: Intel ICH 0000:00:1f.5: PCI INT B disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: ata_piix 0000:00:1f.2: PCI INT A disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: ata_piix 0000:00:1f.1: PCI INT A disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: ehci_hcd 0000:00:1d.7: PCI INT D disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: uhci_hcd 0000:00:1d.3: PCI INT A disabled
Aug 21 16:19:44 tmgf_epi_514 klogd: uhci_hcd 0000:00:1d.2: PCI INT C disabled



Linux is great for calculating how much hemp-based tofu it might take to fill
your bio-gas-powered eco-dome, but for all serious jobs you need a serious
operating system such as Microsoft Windows.
<http://shelleytherepublican.com>
 

Lesen sie die antworten

#1 Henning Paul
21/08/2009 - 17:30 | Warnen spam
Chris schrieb:

irgendwie hat sich einer meiner Rechner von selbst in den Standbymodus
(oder sowas) geworfen. Unten anbei die Logs. Kann auch sein dass
irgendjemand irgendwie den Modus getriggert hat, aber irgendwie
startet die Initiierung ja mit dem Aufruf der
pulseaudio-Fehlermeldung.



Kann ich nicht erkennen.

Gruß
Henning
henning paul home: http://home.arcor.de/henning.paul
PM: , ICQ: 111044613

Ähnliche fragen