Attachment 109021 Details for Bug 225738

Messages after suspend to disk and resume

messages1 (text/plain), 47.45 KB, created by karl-dieter steinhoff on 2006-12-10 18:49:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: karl-dieter steinhoff

Created: 2006-12-10 18:49:12 UTC

Size: 47.45 KB

patch

obsolete

>Dec 10 16:09:51 tux dhclient: caught deadly SIGTERM
>Dec 10 16:09:51 tux dhclient: could not restore resolv.conf: No such file or directory
>Dec 10 16:09:52 tux dhclient: DHCPRELEASE on eth0 to 192.168.178.1 port 67
>Dec 10 16:09:52 tux dhclient: send_packet: Network is unreachable
>Dec 10 16:09:52 tux dhclient: send_packet: please consult README file regarding broadcast address.
>Dec 10 16:09:52 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 16:09:52 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 16:09:52 tux SuSEfirewall2: batch committing...
>Dec 10 16:09:52 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 16:09:54 tux kernel: ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[00023f3a45001b2c]
>Dec 10 17:04:13 tux kernel: Freezing cpus ...
>Dec 10 17:04:13 tux kernel: Stopping tasks: =================================================================================================================================|
>Dec 10 17:04:13 tux kernel: Shrinking memory...  -\|/-\done (69186 pages freed)
>Dec 10 17:04:13 tux kernel: pnp: Device 00:09 disabled.
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:02:04.0 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:02:02.0 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:00:1f.5 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
>Dec 10 17:04:13 tux kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled
>Dec 10 17:04:13 tux kernel: 
>Dec 10 17:04:13 tux syslog-ng[2537]: STATS: dropped 0
>Dec 10 17:04:13 tux kernel: swsusp: Need to copy 55350 pages
>Dec 10 17:04:13 tux kernel: Intel machine check architecture supported.
>Dec 10 17:04:13 tux kernel: Intel machine check reporting enabled on CPU#0.
>Dec 10 17:04:13 tux kernel: swsusp: Restoring Highmem
>Dec 10 17:04:13 tux kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:13 tux kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset f (was 10a, writing ffffffff)
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset e (was 0, writing ffffffff)
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset d (was 0, writing ffffffff)
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset c (was 0, writing ffffffff)
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset b (was 3c1025, writing ffffffff)
>Dec 10 17:04:13 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset a (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 9 (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 8 (was 1201, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 7 (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 6 (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 5 (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 4 (was 0, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 3 (was 800000, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 2 (was c030003, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 1 (was 2800005, writing ffffffff)
>Dec 10 17:04:14 tux kernel: PM: Writing back config space on device 0000:00:1d.0 at offset 0 (was 24c28086, writing ffffffff)
>Dec 10 17:04:14 tux kernel: uhci_hcd 0000:00:1d.0: HCRESET not completed yet!
>Dec 10 17:04:15 tux kernel: usb usb2: root hub lost power or was reset
>Dec 10 17:04:15 tux kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:15 tux kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset f (was 20b, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset e (was 0, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset d (was 0, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset c (was 0, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset b (was 3c1025, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset a (was 0, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 9 (was 0, writing ffffffff)
>Dec 10 17:04:15 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1601, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 7 (was 0, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 6 (was 0, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 5 (was 0, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 4 (was 0, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 3 (was 0, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 2 (was c030003, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 1 (was 2800005, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.1 at offset 0 (was 24c48086, writing ffffffff)
>Dec 10 17:04:16 tux kernel: uhci_hcd 0000:00:1d.1: HCRESET not completed yet!
>Dec 10 17:04:16 tux kernel: usb usb3: root hub lost power or was reset
>Dec 10 17:04:16 tux kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:16 tux kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset f (was 30b, writing ffffffff)
>Dec 10 17:04:16 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset e (was 0, writing ffffffff)
>Dec 10 17:04:14 tux zmd: ShutdownManager (WARN): Preparing to sleep...
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset d (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset c (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset b (was 3c1025, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset a (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 9 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1701, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 7 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 6 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 5 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 4 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 3 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 2 (was c030003, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 1 (was 2800005, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.2 at offset 0 (was 24c78086, writing ffffffff)
>Dec 10 17:04:17 tux kernel: uhci_hcd 0000:00:1d.2: HCRESET not completed yet!
>Dec 10 17:04:17 tux kernel: usb usb4: root hub lost power or was reset
>Dec 10 17:04:17 tux kernel: ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:17 tux kernel: PCI: Setting latency timer of device 0000:00:1d.7 to 64
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset f (was 40b, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset e (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset d (was 50, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset c (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset b (was 3c1025, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset a (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 9 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 8 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 7 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 6 (was 0, writing ffffffff)
>Dec 10 17:04:17 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 5 (was 0, writing ffffffff)
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was f4000000, writing ffffffff)
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 3 (was 0, writing ffffffff)
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 2 (was c032003, writing ffffffff)
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900006, writing ffffffff)
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1d.7 at offset 0 (was 24cd8086, writing ffffffff)
>Dec 10 17:04:18 tux kernel: usb usb1: root hub lost power or was reset
>Dec 10 17:04:18 tux kernel: ehci_hcd 0000:00:1d.7: debug port 1 IN USE
>Dec 10 17:04:18 tux kernel: PCI: cache line size of 32 is not supported by device 0000:00:1d.7
>Dec 10 17:04:18 tux kernel: ehci_hcd 0000:00:1d.7: PCI post-resume error -19!
>Dec 10 17:04:18 tux kernel: ehci_hcd 0000:00:1d.7: HC died; cleaning up
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1e.0 at offset 6 (was 20020200, writing 20060200)
>Dec 10 17:04:18 tux kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64
>Dec 10 17:04:18 tux kernel: PM: Writing back config space on device 0000:00:1f.5 at offset 1 (was 2900007, writing 2900000)
>Dec 10 17:04:18 tux kernel: PCI: Enabling device 0000:00:1f.5 (0000 -> 0003)
>Dec 10 17:04:18 tux kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:18 tux kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
>Dec 10 17:04:18 tux kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:18 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:19 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: PM: Writing back config space on device 0000:02:04.0 at offset f (was 1c00105, writing 5c00105)
>Dec 10 17:04:20 tux kernel: PM: Writing back config space on device 0000:02:04.0 at offset 3 (was 28008, writing 2a820)
>Dec 10 17:04:20 tux kernel: ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
>Dec 10 17:04:20 tux kernel: pnp: Device 00:06 does not support activation.
>Dec 10 17:04:20 tux kernel: pnp: Device 00:07 does not support activation.
>Dec 10 17:04:20 tux kernel: pnp: Device 00:09 activated.
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:20 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: FGR not stopped yet!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: FGR not stopped yet!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: host controller halted, very bad!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: HCRESET not completed yet!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.0: HC died; cleaning up
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host system error, PCI problems?
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host controller process error, something bad happened!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: host controller halted, very bad!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: HCRESET not completed yet!
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.1: HC died; cleaning up
>Dec 10 17:04:21 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: FGR not stopped yet!
>Dec 10 17:04:22 tux kernel: Restarting tasks...<3>hub 4-0:1.0: over-current change on port 1
>Dec 10 17:04:22 tux kernel:  done
>Dec 10 17:04:22 tux kernel: Thawing cpus ...
>Dec 10 17:04:22 tux kernel: usb 4-1: USB disconnect, address 2
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: host system error, PCI problems?
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: host controller process error, something bad happened!
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: host controller halted, very bad!
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: HCRESET not completed yet!
>Dec 10 17:04:22 tux kernel: uhci_hcd 0000:00:1d.2: HC died; cleaning up
>Dec 10 17:04:22 tux kernel: hub 4-0:1.0: hub_port_status failed (err = -19)
>Dec 10 17:04:22 tux kernel: hub 4-0:1.0: connect-debounce failed, port 1 disabled
>Dec 10 17:04:22 tux kernel: hub 4-0:1.0: cannot disable port 1 (err = -19)
>Dec 10 17:04:22 tux kernel: hub 4-0:1.0: hub_port_status failed (err = -19)
>Dec 10 17:04:22 tux kernel: ACPI: Power Button (FF) [PWRF]
>Dec 10 17:04:22 tux kernel: ACPI Error (evxfevnt-0189): Could not enable SleepButton event [20060707]
>Dec 10 17:04:22 tux kernel: ACPI Warning (evxface-0146): Could not enable fixed event 3 [20060707]
>Dec 10 17:04:22 tux kernel: ACPI: Lid Switch [LID]
>Dec 10 17:04:22 tux kernel: ACPI: Power Button (CM) [PWRB]
>Dec 10 17:04:22 tux kernel: ieee1394: Initialized config rom entry `ip1394'
>Dec 10 17:04:22 tux kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10]  MMIO=[d0001800-d0001fff]  Max Packet=[2048]  IR/IT contexts=[4/8]
>Dec 10 17:04:22 tux kernel: ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00023f3a45001b2c]
>Dec 10 17:04:23 tux kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
>Dec 10 17:04:23 tux kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>Dec 10 17:04:24 tux zmd: NetworkStatus (WARN): Network has been disconnected
>Dec 10 17:04:24 tux zmd: NetworkStatus (WARN): Network has been disconnected
>Dec 10 17:04:24 tux zmd: NetworkStatus (WARN): Network has been disconnected
>Dec 10 17:04:24 tux zmd: NetworkStatus (WARN): Network has been disconnected
>Dec 10 17:04:24 tux zmd: NetworkStatus (WARN): Network has been disconnected
>Dec 10 17:04:26 tux zmd: ShutdownManager (WARN): Going to sleep, waking up at 12/11/2006 15:38:28
>Dec 10 17:04:30 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
>Dec 10 17:04:31 tux dhclient: DHCPOFFER from 192.168.178.1
>Dec 10 17:04:35 tux dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
>Dec 10 17:04:35 tux dhclient: DHCPACK from 192.168.178.1
>Dec 10 17:04:35 tux dhclient: bound to 192.168.178.21 -- renewal in 67904 seconds.
>Dec 10 17:04:37 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:04:38 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:04:38 tux SuSEfirewall2: batch committing...
>Dec 10 17:04:38 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:04:46 tux kernel: eth0: no IPv6 routers present
>Dec 10 17:04:48 tux kernel: eth0: link down
>Dec 10 17:04:48 tux dhclient: caught deadly SIGTERM
>Dec 10 17:04:48 tux dhclient: could not restore resolv.conf: No such file or directory
>Dec 10 17:04:48 tux dhclient: DHCPRELEASE on eth0 to 192.168.178.1 port 67
>Dec 10 17:04:49 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:04:49 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:04:49 tux SuSEfirewall2: Warning: no interface active
>Dec 10 17:04:49 tux SuSEfirewall2: batch committing...
>Dec 10 17:04:49 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:05:21 tux kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>Dec 10 17:05:22 tux kernel: ieee80211_crypt: registered algorithm 'TKIP'
>Dec 10 17:05:29 tux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
>Dec 10 17:05:30 tux dhclient: DHCPOFFER from 192.168.178.1
>Dec 10 17:05:31 tux kernel: eth1: no IPv6 routers present
>Dec 10 17:05:34 tux dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
>Dec 10 17:05:34 tux dhclient: DHCPACK from 192.168.178.1
>Dec 10 17:05:34 tux dhclient: bound to 192.168.178.20 -- renewal in 74318 seconds.
>Dec 10 17:05:35 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:05:35 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:05:35 tux SuSEfirewall2: batch committing...
>Dec 10 17:05:35 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:05:46 tux kernel: eth1: no IPv6 routers present
>Dec 10 17:05:54 tux gconfd (sff-5201): (Version 2.14.0) wird gestartet, Prozesskennung 5201, Benutzer Â»sffÂ«
>Dec 10 17:05:54 tux gconfd (sff-5201): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatoryÂ« wurde an der Position 0 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:05:54 tux gconfd (sff-5201): Die Adresse Â»xml:readwrite:/home/sff/.gconfÂ« wurde an der Position 1 zu einer schreibbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:05:54 tux gconfd (sff-5201): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaultsÂ« wurde an der Position 2 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:05:54 tux gconfd (sff-5201): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.schemasÂ« wurde an der Position 3 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:07:01 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
>Dec 10 17:07:02 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
>Dec 10 17:12:09 tux su: (to root) sff on /dev/pts/3
>Dec 10 17:17:11 tux shutdown[5334]: shutting down for system reboot
>Dec 10 17:17:11 tux gconfd (sff-5201): Signal 15 erhalten, ordungsgemÃ¤Ães Herunterfahren
>Dec 10 17:17:11 tux gconfd (sff-5201): Beenden
>Dec 10 17:17:12 tux init: Switching to runlevel: 6
>Dec 10 17:17:13 tux kernel: bootsplash: status on console 0 changed to on
>Dec 10 17:17:13 tux auditd[2878]: The audit daemon is exiting.
>Dec 10 17:17:13 tux kernel: audit(1165767433.672:7): audit_pid=0 old=2878 by auid=4294967295
>Dec 10 17:17:15 tux sshd[3147]: Received signal 15; terminating.
>Dec 10 17:17:16 tux kernel: Kernel logging (proc) stopped.
>Dec 10 17:17:16 tux kernel: Kernel log daemon terminating.
>Dec 10 17:17:17 tux syslog-ng[2537]: syslog-ng version 1.6.11 going down
>Dec 10 17:19:06 tux syslog-ng[2548]: syslog-ng version 1.6.11 starting
>Dec 10 17:19:07 tux network: Starting the DHCP DBUS Daemon
>Dec 10 17:19:07 tux network: Starting the NetworkManagerDispatcher
>Dec 10 17:19:07 tux dhcdbd: Started up.
>Dec 10 17:19:07 tux network: Starting the NetworkManager
>Dec 10 17:19:08 tux auditd: Config file /etc/audit/auditd.conf doesn't exist, skipping
>Dec 10 17:19:09 tux auditd[2848]: Init complete, auditd 1.2.6 listening for events
>Dec 10 17:19:11 tux kernel: klogd 1.4.1, log source = /proc/kmsg started.
>Dec 10 17:19:11 tux kernel: NET: Registered protocol family 10
>Dec 10 17:19:11 tux kernel: lo: Disabled Privacy Extensions
>Dec 10 17:19:11 tux kernel: IPv6 over IPv4 tunneling driver
>Dec 10 17:19:11 tux syslog-ng[2548]: Changing permissions on special file /dev/xconsole
>Dec 10 17:19:11 tux syslog-ng[2548]: Changing permissions on special file /dev/tty10
>Dec 10 17:19:11 tux kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
>Dec 10 17:19:11 tux kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
>Dec 10 17:19:11 tux kernel: Netfilter messages via NETLINK v0.30.
>Dec 10 17:19:11 tux kernel: ip_conntrack version 2.4 (4095 buckets, 32760 max) - 228 bytes per conntrack
>Dec 10 17:19:11 tux kernel: ACPI: AC Adapter [ACAD] (off-line)
>Dec 10 17:19:11 tux kernel: ACPI: Battery Slot [BAT1] (battery present)
>Dec 10 17:19:11 tux kernel: ACPI: Power Button (FF) [PWRF]
>Dec 10 17:19:11 tux kernel: ACPI Error (evxfevnt-0189): Could not enable SleepButton event [20060707]
>Dec 10 17:19:11 tux kernel: ACPI Warning (evxface-0146): Could not enable fixed event 3 [20060707]
>Dec 10 17:19:11 tux kernel: ACPI: Lid Switch [LID]
>Dec 10 17:19:11 tux kernel: ACPI: Power Button (CM) [PWRB]
>Dec 10 17:19:11 tux kernel: audit(1165767549.010:3): audit_pid=2848 old=0 by auid=4294967295
>Dec 10 17:19:11 tux kernel: IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
>Dec 10 17:19:12 tux /usr/sbin/cron[3174]: (CRON) STARTUP (V5.0)
>Dec 10 17:19:13 tux rcpowersaved: s2ram identified your machine as being capable of suspend to RAM. See 's2ram -n' for details.
>Dec 10 17:19:13 tux sshd[3210]: Server listening on :: port 22.
>Dec 10 17:19:15 tux kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
>Dec 10 17:19:15 tux kernel: eth0: link down
>Dec 10 17:19:15 tux kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
>Dec 10 17:19:17 tux kernel: NET: Registered protocol family 17
>Dec 10 17:19:18 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
>Dec 10 17:19:18 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
>Dec 10 17:19:18 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
>Dec 10 17:19:18 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
>Dec 10 17:19:18 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:19:18 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:19:18 tux SuSEfirewall2: Warning: no interface active
>Dec 10 17:19:19 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
>Dec 10 17:19:20 tux SuSEfirewall2: batch committing...
>Dec 10 17:19:20 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:19:23 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
>Dec 10 17:19:29 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
>Dec 10 17:19:37 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
>Dec 10 17:19:48 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
>Dec 10 17:19:59 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
>Dec 10 17:20:01 tux dhclient: caught deadly SIGTERM
>Dec 10 17:20:01 tux dhclient: could not restore resolv.conf: No such file or directory
>Dec 10 17:20:01 tux dhclient: DHCPRELEASE on eth0 to 192.168.178.1 port 67
>Dec 10 17:20:01 tux dhclient: send_packet: Network is unreachable
>Dec 10 17:20:01 tux dhclient: send_packet: please consult README file regarding broadcast address.
>Dec 10 17:20:20 tux gconfd (sff-4026): (Version 2.14.0) wird gestartet, Prozesskennung 4026, Benutzer Â»sffÂ«
>Dec 10 17:20:21 tux gconfd (sff-4026): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatoryÂ« wurde an der Position 0 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:20:21 tux gconfd (sff-4026): Die Adresse Â»xml:readwrite:/home/sff/.gconfÂ« wurde an der Position 1 zu einer schreibbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:20:21 tux gconfd (sff-4026): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaultsÂ« wurde an der Position 2 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:20:21 tux gconfd (sff-4026): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.schemasÂ« wurde an der Position 3 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 17:20:22 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:20:22 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:20:22 tux SuSEfirewall2: Warning: no interface active
>Dec 10 17:20:22 tux SuSEfirewall2: batch committing...
>Dec 10 17:20:22 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:20:24 tux zmd: ServiceManager (ERROR): Service Refresh Failed: 
>Dec 10 17:20:52 tux kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>Dec 10 17:20:53 tux kernel: ieee80211_crypt: registered algorithm 'TKIP'
>Dec 10 17:20:56 tux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
>Dec 10 17:20:57 tux dhclient: DHCPOFFER from 192.168.178.1
>Dec 10 17:20:59 tux zmd: Daemon (WARN): Not starting remote web server
>Dec 10 17:21:01 tux dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
>Dec 10 17:21:01 tux dhclient: DHCPACK from 192.168.178.1
>Dec 10 17:21:01 tux dhclient: bound to 192.168.178.20 -- renewal in 79050 seconds.
>Dec 10 17:21:03 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 17:21:03 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 17:21:03 tux SuSEfirewall2: batch committing...
>Dec 10 17:21:03 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 17:21:12 tux kernel: eth1: no IPv6 routers present
>Dec 10 17:27:03 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
>Dec 10 17:27:04 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
>Dec 10 17:28:24 tux suse_register[4699]: Installed Products Dump: $VAR1 = [           [             'openSUSE-10.2-CD-download',             '10.2',             '0',             'i686'           ]         ]; 
>Dec 10 17:28:46 tux suse_register[4699]: dumpfile write(zypp/yum):http://ftp.uni-kl.de/pub/linux/suse/update/10.2?alias=SUSE-Linux-10.2-Updates 
>Dec 10 17:36:43 tux gconfd (sff-4026): Signal 15 erhalten, ordungsgemÃ¤Ães Herunterfahren
>Dec 10 17:36:43 tux gconfd (sff-4026): Beenden
>Dec 10 17:36:44 tux shutdown[5236]: shutting down for system halt
>Dec 10 17:36:45 tux init: Switching to runlevel: 0
>Dec 10 17:36:47 tux kernel: bootsplash: status on console 0 changed to on
>Dec 10 17:36:47 tux auditd[2848]: The audit daemon is exiting.
>Dec 10 17:36:47 tux kernel: audit(1165768607.412:7): audit_pid=0 old=2848 by auid=4294967295
>Dec 10 17:36:48 tux kernel: ACPI: PCI interrupt for device 0000:00:1f.5 disabled
>Dec 10 17:36:48 tux zmd: ShutdownManager (WARN): Preparing to shut down...
>Dec 10 17:36:48 tux zmd: ShutdownManager (WARN): Shutting down daemon...
>Dec 10 17:36:49 tux sshd[3210]: Received signal 15; terminating.
>Dec 10 17:36:51 tux kernel: Kernel logging (proc) stopped.
>Dec 10 17:36:51 tux kernel: Kernel log daemon terminating.
>Dec 10 17:36:52 tux syslog-ng[2548]: syslog-ng version 1.6.11 going down
>Dec 10 19:17:02 tux syslog-ng[2547]: syslog-ng version 1.6.11 starting
>Dec 10 19:17:03 tux network: Starting the DHCP DBUS Daemon
>Dec 10 19:17:03 tux network: Starting the NetworkManagerDispatcher
>Dec 10 19:17:03 tux dhcdbd: Started up.
>Dec 10 19:17:03 tux network: Starting the NetworkManager
>Dec 10 19:17:04 tux auditd: Config file /etc/audit/auditd.conf doesn't exist, skipping
>Dec 10 19:17:05 tux auditd[2847]: Init complete, auditd 1.2.6 listening for events
>Dec 10 19:17:07 tux kernel: klogd 1.4.1, log source = /proc/kmsg started.
>Dec 10 19:17:07 tux kernel: NET: Registered protocol family 10
>Dec 10 19:17:07 tux kernel: lo: Disabled Privacy Extensions
>Dec 10 19:17:07 tux kernel: IPv6 over IPv4 tunneling driver
>Dec 10 19:17:07 tux syslog-ng[2547]: Changing permissions on special file /dev/xconsole
>Dec 10 19:17:07 tux syslog-ng[2547]: Changing permissions on special file /dev/tty10
>Dec 10 19:17:07 tux kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
>Dec 10 19:17:07 tux kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
>Dec 10 19:17:07 tux kernel: Netfilter messages via NETLINK v0.30.
>Dec 10 19:17:07 tux kernel: ip_conntrack version 2.4 (4095 buckets, 32760 max) - 228 bytes per conntrack
>Dec 10 19:17:07 tux kernel: ACPI: AC Adapter [ACAD] (off-line)
>Dec 10 19:17:07 tux kernel: ACPI: Battery Slot [BAT1] (battery present)
>Dec 10 19:17:07 tux kernel: ACPI: Power Button (FF) [PWRF]
>Dec 10 19:17:07 tux kernel: ACPI Error (evxfevnt-0189): Could not enable SleepButton event [20060707]
>Dec 10 19:17:07 tux kernel: ACPI Warning (evxface-0146): Could not enable fixed event 3 [20060707]
>Dec 10 19:17:07 tux kernel: ACPI: Lid Switch [LID]
>Dec 10 19:17:07 tux kernel: ACPI: Power Button (CM) [PWRB]
>Dec 10 19:17:07 tux kernel: audit(1165774625.026:3): audit_pid=2847 old=0 by auid=4294967295
>Dec 10 19:17:07 tux kernel: IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
>Dec 10 19:17:07 tux kernel: microcode: CPU0 updated from revision 0x5 to 0x7, date = 11092004 
>Dec 10 19:17:08 tux rcpowersaved: s2ram identified your machine as being capable of suspend to RAM. See 's2ram -n' for details.
>Dec 10 19:17:10 tux sshd[3155]: Server listening on :: port 22.
>Dec 10 19:17:10 tux /usr/sbin/cron[3203]: (CRON) STARTUP (V5.0)
>Dec 10 19:17:13 tux kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
>Dec 10 19:17:13 tux kernel: eth0: link down
>Dec 10 19:17:13 tux kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
>Dec 10 19:17:13 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
>Dec 10 19:17:13 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
>Dec 10 19:17:13 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
>Dec 10 19:17:13 tux logger: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
>Dec 10 19:17:14 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 19:17:14 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 19:17:14 tux SuSEfirewall2: Warning: no interface active
>Dec 10 19:17:15 tux SuSEfirewall2: batch committing...
>Dec 10 19:17:15 tux kernel: NET: Registered protocol family 17
>Dec 10 19:17:16 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 19:17:16 tux kernel: bootsplash: status on console 0 changed to on
>Dec 10 19:17:19 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
>Dec 10 19:17:21 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
>Dec 10 19:17:25 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
>Dec 10 19:17:29 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
>Dec 10 19:17:40 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
>Dec 10 19:17:53 tux dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
>Dec 10 19:17:59 tux dhclient: caught deadly SIGTERM
>Dec 10 19:17:59 tux dhclient: could not restore resolv.conf: No such file or directory
>Dec 10 19:18:00 tux dhclient: DHCPRELEASE on eth0 to 192.168.178.1 port 67
>Dec 10 19:18:00 tux dhclient: send_packet: Network is unreachable
>Dec 10 19:18:00 tux dhclient: send_packet: please consult README file regarding broadcast address.
>Dec 10 19:18:07 tux zmd: ServiceManager (ERROR): Service Refresh Failed: Failed to parse XML metadata: Can't add repository at ftp://ftp.suse.com/pub/suse/update/10.2: Unknown source type for ftp://ftp.suse.com/pub/suse/update/10.2
>Dec 10 19:18:26 tux kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>Dec 10 19:18:27 tux kernel: ieee80211_crypt: registered algorithm 'TKIP'
>Dec 10 19:18:28 tux zmd: Daemon (WARN): Not starting remote web server
>Dec 10 19:18:31 tux dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
>Dec 10 19:18:32 tux dhclient: DHCPOFFER from 192.168.178.1
>Dec 10 19:18:36 tux dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
>Dec 10 19:18:36 tux dhclient: DHCPACK from 192.168.178.1
>Dec 10 19:18:36 tux dhclient: bound to 192.168.178.20 -- renewal in 82841 seconds.
>Dec 10 19:18:38 tux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
>Dec 10 19:18:38 tux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
>Dec 10 19:18:39 tux SuSEfirewall2: batch committing...
>Dec 10 19:18:39 tux SuSEfirewall2: Firewall rules successfully set
>Dec 10 19:18:47 tux kernel: eth1: no IPv6 routers present
>Dec 10 19:18:55 tux gconfd (sff-4423): (Version 2.14.0) wird gestartet, Prozesskennung 4423, Benutzer Â»sffÂ«
>Dec 10 19:18:55 tux gconfd (sff-4423): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatoryÂ« wurde an der Position 0 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 19:18:55 tux gconfd (sff-4423): Die Adresse Â»xml:readwrite:/home/sff/.gconfÂ« wurde an der Position 1 zu einer schreibbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 19:18:55 tux gconfd (sff-4423): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaultsÂ« wurde an der Position 2 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 19:18:55 tux gconfd (sff-4423): Die Adresse Â»xml:readonly:/etc/opt/gnome/gconf/gconf.xml.schemasÂ« wurde an der Position 3 zu einer nur lesbaren Konfigurationsquelle aufgelÃ¶st
>Dec 10 19:47:12 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -
>Dec 10 19:47:13 tux sudo:      sff : TTY=pts/2 ; PWD=/home/sff ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub -

Actions: View

Attachments on bug 225738: 109020 | 109021 | 109103 | 111836 | 111838 | 112000