I'm trying to hack/test a network driver's ability to suspend, resume, and wake-on-lan (while suspended). This is on a rawhide x86_64 desktop system. Is the Fedora pm-stuff documented anywhere? I can't seem to find anything on the wiki, and the only related manpage is for pm-pmu.
FWIW, suspend didn't seem to work, but hibernate did (aside from a bunch of lockdep warnings). As near as I can tell though, my network module is unloaded instead of suspended because I think it gets swept up in the modunload() function of /etc/pm/functions.
It'd help if I could find some documentation on Fedora power management, to try and get an understanding of how it's all supposed to work. Any ideas where I can find some docs?
Jay
On Sun, 2007-02-18 at 21:30 -0600, Jay Cliburn wrote:
I'm trying to hack/test a network driver's ability to suspend, resume, and wake-on-lan (while suspended). This is on a rawhide x86_64 desktop system. Is the Fedora pm-stuff documented anywhere? I can't seem to find anything on the wiki, and the only related manpage is for pm-pmu.
FWIW, suspend didn't seem to work, but hibernate did (aside from a bunch of lockdep warnings). As near as I can tell though, my network module is unloaded instead of suspended because I think it gets swept up in the modunload() function of /etc/pm/functions.
It'd help if I could find some documentation on Fedora power management, to try and get an understanding of how it's all supposed to work. Any ideas where I can find some docs?
Well, there's a link to quite an old presentation I wrote here http://people.freedesktop.org/~hughsient/public/gnome-power-manager.pdf which mentions how pm-utils fits into the stack, although the document needs updating with the latest PolicyKit and ConsoleKit coolness.
I've also attached the pm-utils README file from CVS which might help.
I agree, this stuff needs better documenting - a wiki page might be best, or maybe just manpages for the other tools.
Richard.
On Mon, 19 Feb 2007 09:11:10 +0000 Richard Hughes hughsient@gmail.com wrote:
Well, there's a link to quite an old presentation I wrote
I've also attached the pm-utils README file from CVS which might help.
Thanks a lot for this info Richard. I really appreciate it.
So to make my nic driver suspend (instead of being removed with "modprobe -r"), I need only add the module name to the SUSPEND_MODULES line of /etc/pm/config? Like this? (my driver name is atl1)
SUSPEND_MODULES="button atl1" HIBERNATE_RESUME_POST_VIDEO="no" DISABLE_HIBERNATE="no" DISABLE_SUSPEND="no"
On Mon, 2007-02-19 at 07:11 -0600, Jay Cliburn wrote:
On Mon, 19 Feb 2007 09:11:10 +0000 Richard Hughes hughsient@gmail.com wrote:
Well, there's a link to quite an old presentation I wrote
I've also attached the pm-utils README file from CVS which might help.
Thanks a lot for this info Richard. I really appreciate it.
So to make my nic driver suspend (instead of being removed with "modprobe -r"), I need only add the module name to the SUSPEND_MODULES line of /etc/pm/config? Like this? (my driver name is atl1)
The default is for the driver to be suspended normally; SUSPEND_MODULES is to list (broken) modules that have to be removed and reinserted around the suspend process.
Jeremy
On Mon, 19 Feb 2007 at 9:14am, Jeremy Katz wrote
The default is for the driver to be suspended normally; SUSPEND_MODULES is to list (broken) modules that have to be removed and reinserted around the suspend process.
Is it considered a (fixable, bugzillable) bug if normal suspending works but has undesirable effects? Example -- on my Thinkpad Z61t, suspend and wake-up worked out of the box with FC6, but the power drain was impressive (I have the figures at home, but it was >50% battery of capacity overnight). Some experimenting demonstarted that removing the USB modules before going to sleep dropped the sleeping power consumption considerably, so I put those in SUSPEND_MODULES. I figured this was model specific so I didn't bugzilla it. Should I?
On Mon, 2007-02-19 at 09:24 -0500, Joshua Baker-LePain wrote:
On Mon, 19 Feb 2007 at 9:14am, Jeremy Katz wrote
The default is for the driver to be suspended normally; SUSPEND_MODULES is to list (broken) modules that have to be removed and reinserted around the suspend process.
Is it considered a (fixable, bugzillable) bug if normal suspending works but has undesirable effects? Example -- on my Thinkpad Z61t, suspend and wake-up worked out of the box with FC6, but the power drain was impressive (I have the figures at home, but it was >50% battery of capacity overnight). Some experimenting demonstarted that removing the USB modules before going to sleep dropped the sleeping power consumption considerably, so I put those in SUSPEND_MODULES. I figured this was model specific so I didn't bugzilla it. Should I?
It definitely doesn't hurt to file it so that it can be tracked. And should probably be filed against kernel
Jeremy
On Mon, 19 Feb 2007 09:14:16 -0500 Jeremy Katz katzj@redhat.com wrote:
The default is for the driver to be suspended normally; SUSPEND_MODULES is to list (broken) modules that have to be removed and reinserted around the suspend process.
Thanks for the clarification.
I'm getting fairly spectacular failures whenever I execute pm-suspend. The failure mode is variable. In this particular example, I end up with slab corruption. I presume this should be passed upstream?
Feb 19 08:40:01 osprey ntpd[2061]: ntpd exiting on signal 15 Feb 19 08:40:05 osprey restorecond: Read error (Interrupted system call) Feb 19 08:40:05 osprey kernel: Stopping tasks ... done. Feb 19 08:40:05 osprey kernel: Suspending console(s) Feb 19 08:40:05 osprey kernel: pnp: Device 00:0c disabled. Feb 19 08:40:05 osprey kernel: pnp: Device 00:07 disabled. Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:02:00.0 disabled Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1f.2 disabled Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1f.1 disabled Feb 19 08:40:05 osprey kernel: pci_set_power_state(): 0000:00:1f.1: state=3, current state=5 Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1d.7 disabled Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1d.3 disabled Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled Feb 19 08:40:05 osprey kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled Feb 19 08:40:09 osprey kernel: ACPI: PCI interrupt for device 0000:00:1d.0 disabled Feb 19 08:40:09 osprey kernel: ACPI: PCI interrupt for device 0000:00:1b.0 disabled Feb 19 08:40:09 osprey kernel: Disabling non-boot CPUs ... Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: ======================================================= Feb 19 08:40:09 osprey kernel: [ INFO: possible circular locking dependency detected ] Feb 19 08:40:09 osprey kernel: 2.6.20-1.2932.fc7 #1 Feb 19 08:40:09 osprey kernel: ------------------------------------------------------- Feb 19 08:40:09 osprey kernel: pm-suspend/2840 is trying to acquire lock: Feb 19 08:40:09 osprey kernel: (cpu_bitmask_lock){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: but task is already holding lock: Feb 19 08:40:09 osprey kernel: (workqueue_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: which lock already depends on the new lock. Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: the existing dependency chain (in reverse order) is: Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: -> #3 (workqueue_mutex){--..}: Feb 19 08:40:09 osprey kernel: [<ffffffff802a4f63>] __lock_acquire+0xa1c/0xbc4 Feb 19 08:40:09 osprey kernel: [<ffffffff802a5501>] lock_acquire+0x4c/0x65 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff8029b71a>] __create_workqueue+0x78/0x160 Feb 19 08:40:09 osprey kernel: [<ffffffff882af6cd>] cpufreq_governor_dbs+0xb7/0x37b [cpufreq_ondemand] Feb 19 08:40:09 osprey kernel: [<ffffffff803fb456>] cpufreq_governor_userspace+0x207/0x214 Feb 19 08:40:09 osprey kernel: [<ffffffff803f9c82>] __cpufreq_governor+0x71/0xae Feb 19 08:40:09 osprey kernel: [<ffffffff803f9e4b>] __cpufreq_set_policy+0x18c/0x208 Feb 19 08:40:09 osprey kernel: [<ffffffff803fa0f4>] store_scaling_governor+0x18b/0x1eb Feb 19 08:40:09 osprey kernel: [<ffffffff803fae00>] handle_update+0x0/0x36 Feb 19 08:40:09 osprey kernel: [<ffffffff80272c9d>] store+0x4c/0x66 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ac93>] sysfs_write_file+0xec/0x123 Feb 19 08:40:09 osprey kernel: [<ffffffff802162fc>] vfs_write+0xcf/0x178 Feb 19 08:40:09 osprey kernel: [<ffffffff80216d11>] sys_write+0x47/0x70 Feb 19 08:40:09 osprey kernel: [<ffffffff8025d11e>] system_call+0x7e/0x83 Feb 19 08:40:09 osprey kernel: [<ffffffffffffffff>] 0xffffffffffffffff Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: -> #2 (dbs_mutex){--..}: Feb 19 08:40:09 osprey kernel: [<ffffffff802a4f63>] __lock_acquire+0xa1c/0xbc4 Feb 19 08:40:09 osprey kernel: [<ffffffff802a5501>] lock_acquire+0x4c/0x65 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 Feb 19 08:40:09 osprey kernel: [<ffffffff802a40c4>] trace_hardirqs_on+0x136/0x15a Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff882af6ab>] cpufreq_governor_dbs+0x95/0x37b [cpufreq_ondemand] Feb 19 08:40:09 osprey kernel: [<ffffffff803fb456>] cpufreq_governor_userspace+0x207/0x214 Feb 19 08:40:09 osprey kernel: [<ffffffff803f9c82>] __cpufreq_governor+0x71/0xae Feb 19 08:40:09 osprey kernel: [<ffffffff803f9e4b>] __cpufreq_set_policy+0x18c/0x208 Feb 19 08:40:09 osprey kernel: [<ffffffff803fa0f4>] store_scaling_governor+0x18b/0x1eb Feb 19 08:40:09 osprey kernel: [<ffffffff803fae00>] handle_update+0x0/0x36 Feb 19 08:40:09 osprey kernel: [<ffffffff80272c9d>] store+0x4c/0x66 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ac93>] sysfs_write_file+0xec/0x123 Feb 19 08:40:09 osprey kernel: [<ffffffff802162fc>] vfs_write+0xcf/0x178 Feb 19 08:40:09 osprey kernel: [<ffffffff80216d11>] sys_write+0x47/0x70 Feb 19 08:40:09 osprey kernel: [<ffffffff8025d11e>] system_call+0x7e/0x83 Feb 19 08:40:09 osprey kernel: [<ffffffffffffffff>] 0xffffffffffffffff Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: -> #1 (&policy->lock){--..}: Feb 19 08:40:09 osprey kernel: [<ffffffff802a4f63>] __lock_acquire+0xa1c/0xbc4 Feb 19 08:40:09 osprey kernel: [<ffffffff802a5501>] lock_acquire+0x4c/0x65 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff803f9efe>] cpufreq_set_policy+0x37/0xa2 Feb 19 08:40:09 osprey kernel: [<ffffffff803fa9cc>] cpufreq_add_dev+0x3ea/0x4f4 Feb 19 08:40:09 osprey kernel: [<ffffffff803fae00>] handle_update+0x0/0x36 Feb 19 08:40:09 osprey kernel: [<ffffffff80264e26>] _spin_unlock_irqrestore+0x3f/0x47 Feb 19 08:40:09 osprey kernel: [<ffffffff803b6cf0>] sysdev_driver_register+0x7d/0xd1 Feb 19 08:40:09 osprey kernel: [<ffffffff803f9b35>] cpufreq_register_driver+0xc2/0x19e Feb 19 08:40:09 osprey kernel: [<ffffffff8067fdc2>] centrino_init+0xbb/0xc4 Feb 19 08:40:09 osprey kernel: [<ffffffff8026ad4b>] init+0x1e7/0x3ae Feb 19 08:40:09 osprey kernel: [<ffffffff802a40c4>] trace_hardirqs_on+0x136/0x15a Feb 19 08:40:09 osprey kernel: [<ffffffff8025df38>] child_rip+0xa/0x12 Feb 19 08:40:09 osprey kernel: [<ffffffff80264db0>] _spin_unlock_irq+0x2b/0x31 Feb 19 08:40:09 osprey kernel: [<ffffffff8025d6bc>] restore_args+0x0/0x30 Feb 19 08:40:09 osprey kernel: [<ffffffff8026ab64>] init+0x0/0x3ae Feb 19 08:40:09 osprey kernel: [<ffffffff8025df2e>] child_rip+0x0/0x12 Feb 19 08:40:09 osprey kernel: [<ffffffffffffffff>] 0xffffffffffffffff Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: -> #0 (cpu_bitmask_lock){--..}: Feb 19 08:40:09 osprey kernel: [<ffffffff802a2bc0>] print_circular_bug_entry+0x48/0x4f Feb 19 08:40:09 osprey kernel: [<ffffffff802a4e5d>] __lock_acquire+0x916/0xbc4 Feb 19 08:40:09 osprey kernel: [<ffffffff802a5501>] lock_acquire+0x4c/0x65 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 Feb 19 08:40:09 osprey kernel: [<ffffffff802a40c4>] trace_hardirqs_on+0x136/0x15a Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802a8ac1>] lock_cpu_hotplug+0x7a/0x86 Feb 19 08:40:09 osprey kernel: [<ffffffff803fa33d>] cpufreq_driver_target+0x37/0x75 Feb 19 08:40:09 osprey kernel: [<ffffffff803fab28>] cpufreq_cpu_callback+0x52/0x63 Feb 19 08:40:09 osprey kernel: [<ffffffff80267559>] notifier_call_chain+0x29/0x3e Feb 19 08:40:09 osprey kernel: [<ffffffff8029835b>] raw_notifier_call_chain+0x9/0xb Feb 19 08:40:09 osprey kernel: [<ffffffff802a875c>] _cpu_down+0x58/0x21e Feb 19 08:40:09 osprey kernel: [<ffffffff802a8b5a>] disable_nonboot_cpus+0x8d/0x11c Feb 19 08:40:09 osprey kernel: [<ffffffff802ac11e>] enter_state+0x11f/0x1b0 Feb 19 08:40:09 osprey kernel: [<ffffffff802ac217>] state_store+0x68/0x86 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ab48>] subsys_attr_store+0x24/0x26 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ac93>] sysfs_write_file+0xec/0x123 Feb 19 08:40:09 osprey kernel: [<ffffffff802162fc>] vfs_write+0xcf/0x178 Feb 19 08:40:09 osprey kernel: [<ffffffff80216d11>] sys_write+0x47/0x70 Feb 19 08:40:09 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:09 osprey kernel: [<ffffffffffffffff>] 0xffffffffffffffff Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: other info that might help us debug this: Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: 4 locks held by pm-suspend/2840: Feb 19 08:40:09 osprey kernel: #0: (pm_mutex){--..}, at: [<ffffffff802ac043>] enter_state+0x44/0x1b0 Feb 19 08:40:09 osprey kernel: #1: (cpu_add_remove_lock){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: #2: (cache_chain_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: #3: (workqueue_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: stack backtrace: Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: Call Trace: Feb 19 08:40:09 osprey kernel: [<ffffffff802a3556>] print_circular_bug_tail+0x70/0x7b Feb 19 08:40:09 osprey kernel: [<ffffffff802a2bc0>] print_circular_bug_entry+0x48/0x4f Feb 19 08:40:09 osprey kernel: [<ffffffff802a4e5d>] __lock_acquire+0x916/0xbc4 Feb 19 08:40:09 osprey kernel: [<ffffffff802a5501>] lock_acquire+0x4c/0x65 Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 Feb 19 08:40:09 osprey kernel: [<ffffffff802a40c4>] trace_hardirqs_on+0x136/0x15a Feb 19 08:40:09 osprey kernel: [<ffffffff80263385>] mutex_lock+0x2a/0x2e Feb 19 08:40:09 osprey kernel: [<ffffffff802a8ac1>] lock_cpu_hotplug+0x7a/0x86 Feb 19 08:40:09 osprey kernel: [<ffffffff803fa33d>] cpufreq_driver_target+0x37/0x75 Feb 19 08:40:09 osprey kernel: [<ffffffff803fab28>] cpufreq_cpu_callback+0x52/0x63 Feb 19 08:40:09 osprey kernel: [<ffffffff80267559>] notifier_call_chain+0x29/0x3e Feb 19 08:40:09 osprey kernel: [<ffffffff8029835b>] raw_notifier_call_chain+0x9/0xb Feb 19 08:40:09 osprey kernel: [<ffffffff802a875c>] _cpu_down+0x58/0x21e Feb 19 08:40:09 osprey kernel: [<ffffffff802a8b5a>] disable_nonboot_cpus+0x8d/0x11c Feb 19 08:40:09 osprey kernel: [<ffffffff802ac11e>] enter_state+0x11f/0x1b0 Feb 19 08:40:09 osprey kernel: [<ffffffff802ac217>] state_store+0x68/0x86 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ab48>] subsys_attr_store+0x24/0x26 Feb 19 08:40:09 osprey kernel: [<ffffffff8030ac93>] sysfs_write_file+0xec/0x123 Feb 19 08:40:09 osprey kernel: [<ffffffff802162fc>] vfs_write+0xcf/0x178 Feb 19 08:40:09 osprey kernel: [<ffffffff80216d11>] sys_write+0x47/0x70 Feb 19 08:40:09 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: Breaking affinity for irq 14 Feb 19 08:40:09 osprey kernel: Breaking affinity for irq 20 Feb 19 08:40:09 osprey kernel: Breaking affinity for irq 23 Feb 19 08:40:09 osprey kernel: Breaking affinity for irq 2301 Feb 19 08:40:09 osprey kernel: CPU 1 is now offline Feb 19 08:40:09 osprey kernel: lockdep: not fixing up alternatives. Feb 19 08:40:09 osprey kernel: CPU1 is down Feb 19 08:40:09 osprey kernel: Enabling non-boot CPUs ... Feb 19 08:40:09 osprey kernel: lockdep: not fixing up alternatives. Feb 19 08:40:09 osprey kernel: Booting processor 1/2 APIC 0x1 Feb 19 08:40:09 osprey kernel: Initializing CPU#1 Feb 19 08:40:09 osprey kernel: Calibrating delay using timer specific routine.. 4265.91 BogoMIPS (lpj=2132957) Feb 19 08:40:09 osprey kernel: CPU: L1 I cache: 32K, L1 D cache: 32K Feb 19 08:40:09 osprey kernel: CPU: L2 cache: 2048K Feb 19 08:40:09 osprey kernel: CPU 1/1 -> Node 0 Feb 19 08:40:09 osprey kernel: CPU: Physical Processor ID: 0 Feb 19 08:40:09 osprey kernel: CPU: Processor Core ID: 1 Feb 19 08:40:09 osprey kernel: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz stepping 06 Feb 19 08:40:09 osprey kernel: speedstep-centrino with X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated. Feb 19 08:40:09 osprey kernel: Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead. Feb 19 08:40:09 osprey kernel: CPU1 is up Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 19 (level, low) -> IRQ 19 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 20 Feb 19 08:40:09 osprey kernel: usb usb1: root hub lost power or was reset Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17 Feb 19 08:40:09 osprey kernel: usb usb2: root hub lost power or was reset Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18 Feb 19 08:40:09 osprey kernel: usb usb3: root hub lost power or was reset Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19 Feb 19 08:40:09 osprey kernel: usb usb4: root hub lost power or was reset Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 23 (level, low) -> IRQ 23 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 23 (level, low) -> IRQ 23 Feb 19 08:40:09 osprey kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 Feb 19 08:40:09 osprey kernel: atl1: eth0 link is up 100 Mbps full duplex Feb 19 08:40:09 osprey kernel: pnp: Device 00:07 activated. Feb 19 08:40:09 osprey kernel: pnp: Failed to activate device 00:0a. Feb 19 08:40:09 osprey kernel: pnp: Device 00:0c activated. Feb 19 08:40:09 osprey kernel: ttyS0: LSR safety check engaged! Feb 19 08:40:09 osprey kernel: ATA: abnormal status 0x7F on port 0x0000000000010177 Feb 19 08:40:09 osprey kernel: ATA: abnormal status 0x7F on port 0x000000000001b007 Feb 19 08:40:09 osprey kernel: usbdev1.3_ep00: PM: resume from 0, parent 1-1 still 2 Feb 19 08:40:09 osprey kernel: usbhid 1-1:1.0: PM: resume from 2, parent 1-1 still 2 Feb 19 08:40:09 osprey kernel: usbdev1.3_ep81: PM: resume from 0, parent 1-1:1.0 still 2 Feb 19 08:40:09 osprey kernel: usbdev1.3: PM: resume from 0, parent 1-1 still 2 Feb 19 08:40:09 osprey kernel: Restarting tasks ... <6>usb 1-1: USB disconnect, address 3 Feb 19 08:40:09 osprey kernel: done. Feb 19 08:40:09 osprey kernel: ttyS0: LSR safety check engaged! Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 1 Feb 19 08:40:09 osprey kernel: input: Power Button (FF) as /class/input/input7 Feb 19 08:40:09 osprey kernel: ACPI: Power Button (FF) [PWRF] Feb 19 08:40:09 osprey kernel: input: Power Button (CM) as /class/input/input8 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 2 Feb 19 08:40:09 osprey kernel: ACPI: Power Button (CM) [PWRB] Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 3 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 4 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 5 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 6 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 7 Feb 19 08:40:09 osprey kernel: hub 5-0:1.0: over-current change on port 8 Feb 19 08:40:09 osprey kernel: ata1.00: configured for UDMA/33 Feb 19 08:40:09 osprey kernel: usb 1-1: new low speed USB device using uhci_hcd and address 4 Feb 19 08:40:09 osprey kernel: usb 1-1: configuration #1 chosen from 1 choice Feb 19 08:40:09 osprey kernel: input: HID 1241:1177 as /class/input/input9 Feb 19 08:40:09 osprey kernel: input: USB HID v1.00 Mouse [HID 1241:1177] on usb-0000:00:1d.0-1 Feb 19 08:40:09 osprey kernel: ata3.00: configured for UDMA/133 Feb 19 08:40:09 osprey kernel: SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) Feb 19 08:40:09 osprey kernel: sda: Write Protect is off Feb 19 08:40:09 osprey kernel: SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 19 08:40:09 osprey kernel: vbetool[3100]: segfault at 000000000048d810 rip 0000000000425e46 rsp 00007ffff8db90e0 error 4 Feb 19 08:40:09 osprey kernel: Slab corruption: (Not tainted) start=ffff810037c33d68, len=512 Feb 19 08:40:09 osprey kernel: Redzone: 0x5a2cf071/0x5a2cf071. Feb 19 08:40:09 osprey kernel: Last user: [<ffffffff80407b4e>](skb_release_data+0x95/0x9a) Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: Call Trace: Feb 19 08:40:09 osprey kernel: [<ffffffff80207153>] check_poison_obj+0x7f/0x1f9 Feb 19 08:40:09 osprey kernel: [<ffffffff80218941>] load_elf_binary+0xcfb/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff80218941>] load_elf_binary+0xcfb/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff8020c8b7>] cache_alloc_debugcheck_after+0x35/0x1db Feb 19 08:40:09 osprey kernel: [<ffffffff802a0d3c>] up_write+0x26/0x2a Feb 19 08:40:09 osprey kernel: [<ffffffff802d92cc>] __kmalloc+0x147/0x157 Feb 19 08:40:09 osprey kernel: [<ffffffff80218941>] load_elf_binary+0xcfb/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff8024ef72>] load_script+0x0/0x1c4 Feb 19 08:40:09 osprey kernel: [<ffffffff80217c46>] load_elf_binary+0x0/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff80217c46>] load_elf_binary+0x0/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff802405b1>] search_binary_handler+0xcc/0x273 Feb 19 08:40:09 osprey kernel: [<ffffffff8024ef72>] load_script+0x0/0x1c4 Feb 19 08:40:09 osprey kernel: [<ffffffff8024f121>] load_script+0x1af/0x1c4 Feb 19 08:40:09 osprey kernel: [<ffffffff80217c46>] load_elf_binary+0x0/0x18c1 Feb 19 08:40:09 osprey kernel: [<ffffffff802405b1>] search_binary_handler+0xcc/0x273 Feb 19 08:40:09 osprey kernel: [<ffffffff8023fa4e>] do_execve+0x1a4/0x261 Feb 19 08:40:09 osprey kernel: [<ffffffff80254d20>] sys_execve+0x36/0x4d Feb 19 08:40:09 osprey kernel: [<ffffffff8025d517>] stub_execve+0x67/0xb0 Feb 19 08:40:09 osprey kernel: Feb 19 08:40:09 osprey kernel: 090: 6b 6b 6b 6b 6b 6b 6b 6b 5a 5a 5a 5a 5a 5a 5a 5a Feb 19 08:40:09 osprey kernel: 0a0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a Feb 19 08:40:09 osprey kernel: 0b0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a Feb 19 08:40:09 osprey kernel: 0c0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a Feb 19 08:40:10 osprey kernel: 0d0: 5a 5a 5a 5a 5a 5a 5a 5a 6b 6b 6b 6b 6b 6b 6b 6b Feb 19 08:40:10 osprey kernel: Prev obj: start=ffff810037c33b50, len=512 Feb 19 08:40:10 osprey kernel: Redzone: 0x170fc2a5/0x170fc2a5. Feb 19 08:40:10 osprey kernel: Last user: [<ffffffff802d8d8e>](__kmalloc_node+0x25/0x2a) Feb 19 08:40:10 osprey kernel: 000: 00 00 00 00 20 00 00 00 10 00 00 00 00 00 00 00 Feb 19 08:40:10 osprey kernel: 010: 01 00 00 00 ad 4e ad de ff ff ff ff 5a 5a 5a 5a Feb 19 08:40:13 osprey kernel: Slab corruption: (Not tainted) start=ffff81001e565000, len=4096 Feb 19 08:40:13 osprey kernel: Feb 19 08:40:13 osprey kernel: Call Trace: Feb 19 08:40:13 osprey kernel: [<ffffffff80207153>] check_poison_obj+0x7f/0x1f9 Feb 19 08:40:13 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:13 osprey kernel: [<ffffffff8020c8b7>] cache_alloc_debugcheck_after+0x35/0x1db Feb 19 08:40:13 osprey kernel: [<ffffffff8022eb84>] __alloc_skb+0x41/0x144 Feb 19 08:40:13 osprey kernel: [<ffffffff802d8d5c>] kmem_cache_alloc_node+0x129/0x136 Feb 19 08:40:13 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:13 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:13 osprey kernel: [<ffffffff8022ebb0>] __alloc_skb+0x6d/0x144 Feb 19 08:40:13 osprey kernel: [<ffffffff80404c90>] sock_alloc_send_skb+0x80/0x1e1 Feb 19 08:40:13 osprey kernel: [<ffffffff8024b2c2>] unix_stream_sendmsg+0x172/0x350 Feb 19 08:40:13 osprey kernel: [<ffffffff8024848b>] sock_aio_write+0x127/0x13f Feb 19 08:40:13 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:13 osprey kernel: [<ffffffff80248364>] sock_aio_write+0x0/0x13f Feb 19 08:40:13 osprey kernel: [<ffffffff802ddb03>] do_sync_readv_writev+0xe0/0x128 Feb 19 08:40:13 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:13 osprey kernel: [<ffffffff80322544>] file_has_perm+0xa7/0xb6 Feb 19 08:40:13 osprey kernel: [<ffffffff8029e8ac>] autoremove_wake_function+0x0/0x38 Feb 19 08:40:13 osprey kernel: [<ffffffff802ddf8d>] do_readv_writev+0xe1/0x1bc Feb 19 08:40:13 osprey kernel: [<ffffffff802bae4c>] audit_syscall_entry+0x148/0x17e Feb 19 08:40:13 osprey kernel: [<ffffffff802de0a6>] vfs_writev+0x3e/0x49 Feb 19 08:40:13 osprey kernel: [<ffffffff802de0f8>] sys_writev+0x47/0x94 Feb 19 08:40:13 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:13 osprey kernel: Feb 19 08:40:13 osprey kernel: 2c0: 41 4c 49 44 00 00 00 00 17 00 00 00 52 4f 4c 45 Feb 19 08:40:13 osprey kernel: 2d0: 5f 41 43 43 45 4c 45 52 41 54 4f 52 5f 4c 41 42 Feb 19 08:40:13 osprey kernel: 2e0: 45 4c 00 00 0b 00 00 00 52 4f 4c 45 5f 41 4c 45 Feb 19 08:40:13 osprey kernel: 2f0: 52 54 00 00 0f 00 00 00 52 4f 4c 45 5f 41 4e 49 Feb 19 08:40:19 osprey kernel: ttyS0: LSR safety check engaged! Feb 19 08:40:26 osprey ntpd[3145]: ntpd 4.2.4@1.1437 Mon Jan 29 13:39:14 UTC 2007 (1) Feb 19 08:40:26 osprey ntpd[3146]: precision = 1.000 usec Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #1 wildcard, ::#123 Disabled Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #2 lo, ::1#123 Enabled Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #3 eth0, fe80::218:f3ff:fe74:5924#123 Enabled Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #4 lo, 127.0.0.1#123 Enabled Feb 19 08:40:26 osprey ntpd[3146]: Listening on interface #5 eth0, 192.168.1.3#123 Enabled Feb 19 08:40:26 osprey ntpd[3146]: kernel time sync status 0040 Feb 19 08:40:28 osprey ntpd[3146]: frequency initialized -0.870 PPM from /var/lib/ntp/drift Feb 19 08:40:29 osprey kernel: ttyS0: LSR safety check engaged! Feb 19 08:40:31 osprey kernel: Slab corruption: (Not tainted) start=ffff810037c140d8, len=512 Feb 19 08:40:31 osprey kernel: Redzone: 0x5a2cf071/0x170fc2a5. Feb 19 08:40:31 osprey kernel: Last user: [<ffffffff802d8db8>](__kmalloc_node_track_caller+0x25/0x2a) Feb 19 08:40:31 osprey kernel: Feb 19 08:40:31 osprey kernel: Call Trace: Feb 19 08:40:31 osprey kernel: [<ffffffff80207153>] check_poison_obj+0x7f/0x1f9 Feb 19 08:40:31 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:31 osprey kernel: [<ffffffff8020c8b7>] cache_alloc_debugcheck_after+0x35/0x1db Feb 19 08:40:31 osprey kernel: [<ffffffff8022eb84>] __alloc_skb+0x41/0x144 Feb 19 08:40:31 osprey kernel: [<ffffffff802d8d5c>] kmem_cache_alloc_node+0x129/0x136 Feb 19 08:40:31 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:31 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:31 osprey kernel: [<ffffffff8022ebb0>] __alloc_skb+0x6d/0x144 Feb 19 08:40:31 osprey kernel: [<ffffffff80404c90>] sock_alloc_send_skb+0x80/0x1e1 Feb 19 08:40:31 osprey kernel: [<ffffffff8024b2c2>] unix_stream_sendmsg+0x172/0x350 Feb 19 08:40:31 osprey kernel: [<ffffffff8024848b>] sock_aio_write+0x127/0x13f Feb 19 08:40:31 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:31 osprey kernel: [<ffffffff80296153>] __sigqueue_free+0x3b/0x3f Feb 19 08:40:31 osprey kernel: [<ffffffff80248364>] sock_aio_write+0x0/0x13f Feb 19 08:40:31 osprey kernel: [<ffffffff802ddb03>] do_sync_readv_writev+0xe0/0x128 Feb 19 08:40:31 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:31 osprey kernel: [<ffffffff80322544>] file_has_perm+0xa7/0xb6 Feb 19 08:40:31 osprey kernel: [<ffffffff8029e8ac>] autoremove_wake_function+0x0/0x38 Feb 19 08:40:31 osprey kernel: [<ffffffff802ddf8d>] do_readv_writev+0xe1/0x1bc Feb 19 08:40:31 osprey kernel: [<ffffffff802444ee>] sys_rt_sigreturn+0x28f/0x357 Feb 19 08:40:31 osprey kernel: [<ffffffff802bae4c>] audit_syscall_entry+0x148/0x17e Feb 19 08:40:31 osprey kernel: [<ffffffff802de0a6>] vfs_writev+0x3e/0x49 Feb 19 08:40:31 osprey kernel: [<ffffffff802de0f8>] sys_writev+0x47/0x94 Feb 19 08:40:31 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:31 osprey kernel: Feb 19 08:40:31 osprey kernel: 1e0: 6b 6b 6b 6b 6b 6b 6b 6b 5a 5a 5a 5a 5a 5a 5a 5a Feb 19 08:40:31 osprey kernel: 1f0: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5 Feb 19 08:40:31 osprey kernel: Next obj: start=ffff810037c142f0, len=512 Feb 19 08:40:31 osprey kernel: Redzone: 0x170fc2a5/0x5a2cf071. Feb 19 08:40:31 osprey kernel: Last user: [<ffffffff80407b4e>](skb_release_data+0x95/0x9a) Feb 19 08:40:31 osprey kernel: 000: 3c 34 3e 46 65 62 20 31 39 20 30 38 3a 34 30 3a Feb 19 08:40:31 osprey kernel: 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Feb 19 08:40:31 osprey kernel: slab error in cache_alloc_debugcheck_after(): cache `size-512': double free, or memory outside object was overwritten Feb 19 08:40:31 osprey kernel: Feb 19 08:40:31 osprey kernel: Call Trace: Feb 19 08:40:31 osprey kernel: [<ffffffff802d8652>] __slab_error+0x24/0x26 Feb 19 08:40:31 osprey kernel: [<ffffffff8020c92d>] cache_alloc_debugcheck_after+0xab/0x1db Feb 19 08:40:31 osprey kernel: [<ffffffff8022eb84>] __alloc_skb+0x41/0x144 Feb 19 08:40:31 osprey kernel: [<ffffffff802d8d5c>] kmem_cache_alloc_node+0x129/0x136 Feb 19 08:40:31 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:31 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:31 osprey kernel: [<ffffffff8022ebb0>] __alloc_skb+0x6d/0x144 Feb 19 08:40:31 osprey kernel: [<ffffffff80404c90>] sock_alloc_send_skb+0x80/0x1e1 Feb 19 08:40:31 osprey kernel: [<ffffffff8024b2c2>] unix_stream_sendmsg+0x172/0x350 Feb 19 08:40:31 osprey kernel: [<ffffffff8024848b>] sock_aio_write+0x127/0x13f Feb 19 08:40:31 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:31 osprey kernel: [<ffffffff80296153>] __sigqueue_free+0x3b/0x3f Feb 19 08:40:31 osprey kernel: [<ffffffff80248364>] sock_aio_write+0x0/0x13f Feb 19 08:40:31 osprey kernel: [<ffffffff802ddb03>] do_sync_readv_writev+0xe0/0x128 Feb 19 08:40:31 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:32 osprey kernel: [<ffffffff80322544>] file_has_perm+0xa7/0xb6 Feb 19 08:40:32 osprey kernel: [<ffffffff8029e8ac>] autoremove_wake_function+0x0/0x38 Feb 19 08:40:32 osprey kernel: [<ffffffff802ddf8d>] do_readv_writev+0xe1/0x1bc Feb 19 08:40:32 osprey kernel: [<ffffffff802444ee>] sys_rt_sigreturn+0x28f/0x357 Feb 19 08:40:32 osprey kernel: [<ffffffff802bae4c>] audit_syscall_entry+0x148/0x17e Feb 19 08:40:32 osprey kernel: [<ffffffff802de0a6>] vfs_writev+0x3e/0x49 Feb 19 08:40:32 osprey kernel: [<ffffffff802de0f8>] sys_writev+0x47/0x94 Feb 19 08:40:32 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:32 osprey kernel: Feb 19 08:40:32 osprey kernel: ffff810037c140d0: redzone 1:0x5a2cf071, redzone 2:0x170fc2a5 Feb 19 08:40:32 osprey kernel: Slab corruption: (Not tainted) start=ffff810037c142f0, len=512 Feb 19 08:40:32 osprey kernel: Redzone: 0x170fc2a5/0x5a2cf071. Feb 19 08:40:32 osprey kernel: Last user: [<ffffffff80407b4e>](skb_release_data+0x95/0x9a) Feb 19 08:40:32 osprey kernel: Feb 19 08:40:32 osprey kernel: Call Trace: Feb 19 08:40:32 osprey kernel: [<ffffffff80207153>] check_poison_obj+0x7f/0x1f9 Feb 19 08:40:32 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:32 osprey kernel: [<ffffffff8020c8b7>] cache_alloc_debugcheck_after+0x35/0x1db Feb 19 08:40:32 osprey kernel: [<ffffffff8022eb84>] __alloc_skb+0x41/0x144 Feb 19 08:40:32 osprey kernel: [<ffffffff802d8d5c>] kmem_cache_alloc_node+0x129/0x136 Feb 19 08:40:32 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:32 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:32 osprey kernel: [<ffffffff8022ebb0>] __alloc_skb+0x6d/0x144 Feb 19 08:40:32 osprey kernel: [<ffffffff80404c90>] sock_alloc_send_skb+0x80/0x1e1 Feb 19 08:40:32 osprey kernel: [<ffffffff8024b2c2>] unix_stream_sendmsg+0x172/0x350 Feb 19 08:40:32 osprey kernel: [<ffffffff8024848b>] sock_aio_write+0x127/0x13f Feb 19 08:40:32 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:32 osprey kernel: [<ffffffff80296153>] __sigqueue_free+0x3b/0x3f Feb 19 08:40:32 osprey kernel: [<ffffffff80248364>] sock_aio_write+0x0/0x13f Feb 19 08:40:32 osprey kernel: [<ffffffff802ddb03>] do_sync_readv_writev+0xe0/0x128 Feb 19 08:40:32 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:32 osprey kernel: [<ffffffff80322544>] file_has_perm+0xa7/0xb6 Feb 19 08:40:32 osprey kernel: [<ffffffff8029e8ac>] autoremove_wake_function+0x0/0x38 Feb 19 08:40:32 osprey kernel: [<ffffffff802ddf8d>] do_readv_writev+0xe1/0x1bc Feb 19 08:40:32 osprey kernel: [<ffffffff802444ee>] sys_rt_sigreturn+0x28f/0x357 Feb 19 08:40:32 osprey kernel: [<ffffffff802bae4c>] audit_syscall_entry+0x148/0x17e Feb 19 08:40:32 osprey kernel: [<ffffffff802de0a6>] vfs_writev+0x3e/0x49 Feb 19 08:40:32 osprey kernel: [<ffffffff802de0f8>] sys_writev+0x47/0x94 Feb 19 08:40:32 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:32 osprey kernel: Feb 19 08:40:32 osprey kernel: 000: 3c 34 3e 46 65 62 20 31 39 20 30 38 3a 34 30 3a Feb 19 08:40:32 osprey kernel: Prev obj: start=ffff810037c140d8, len=512 Feb 19 08:40:32 osprey kernel: Redzone: 0x170fc2a5/0x170fc2a5. Feb 19 08:40:32 osprey kernel: Last user: [<ffffffff802d8db8>](__kmalloc_node_track_caller+0x25/0x2a) Feb 19 08:40:32 osprey kernel: 000: 6e 02 f2 08 6f e8 1e 00 01 00 00 00 00 00 00 00 Feb 19 08:40:32 osprey kernel: 010: 00 00 00 00 00 00 00 00 00 08 00 20 04 04 00 00 Feb 19 08:40:32 osprey kernel: Next obj: start=ffff810037c14508, len=512 Feb 19 08:40:32 osprey kernel: Redzone: 0x170fc2a5/0x170fc2a5. Feb 19 08:40:32 osprey kernel: Last user: [<ffffffff803a0fa4>](vc_allocate+0x88/0x135) Feb 19 08:40:32 osprey kernel: 000: 07 00 00 00 50 00 00 00 19 00 00 00 a0 00 00 00 Feb 19 08:40:32 osprey kernel: 010: 90 01 00 00 00 00 00 00 00 90 a5 1d 00 81 ff ff Feb 19 08:40:32 osprey kernel: slab error in cache_alloc_debugcheck_after(): cache `size-512': double free, or memory outside object was overwritten Feb 19 08:40:32 osprey kernel: Feb 19 08:40:32 osprey kernel: Call Trace: Feb 19 08:40:32 osprey kernel: [<ffffffff802d8652>] __slab_error+0x24/0x26 Feb 19 08:40:32 osprey kernel: [<ffffffff8020c92d>] cache_alloc_debugcheck_after+0xab/0x1db Feb 19 08:40:32 osprey kernel: [<ffffffff8022eb84>] __alloc_skb+0x41/0x144 Feb 19 08:40:32 osprey kernel: [<ffffffff802d8d5c>] kmem_cache_alloc_node+0x129/0x136 Feb 19 08:40:32 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:32 osprey kernel: [<ffffffff802d8db8>] __kmalloc_node_track_caller+0x25/0x2a Feb 19 08:40:32 osprey kernel: [<ffffffff8022ebb0>] __alloc_skb+0x6d/0x144 Feb 19 08:40:32 osprey kernel: [<ffffffff80404c90>] sock_alloc_send_skb+0x80/0x1e1 Feb 19 08:40:32 osprey kernel: [<ffffffff8024b2c2>] unix_stream_sendmsg+0x172/0x350 Feb 19 08:40:32 osprey kernel: [<ffffffff8024848b>] sock_aio_write+0x127/0x13f Feb 19 08:40:32 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:32 osprey kernel: [<ffffffff80296153>] __sigqueue_free+0x3b/0x3f Feb 19 08:40:32 osprey kernel: [<ffffffff80248364>] sock_aio_write+0x0/0x13f Feb 19 08:40:32 osprey kernel: [<ffffffff802ddb03>] do_sync_readv_writev+0xe0/0x128 Feb 19 08:40:32 osprey kernel: [<ffffffff8032171d>] avc_has_perm+0x49/0x5b Feb 19 08:40:32 osprey kernel: [<ffffffff80322544>] file_has_perm+0xa7/0xb6 Feb 19 08:40:32 osprey kernel: [<ffffffff8029e8ac>] autoremove_wake_function+0x0/0x38 Feb 19 08:40:32 osprey kernel: [<ffffffff802ddf8d>] do_readv_writev+0xe1/0x1bc Feb 19 08:40:32 osprey kernel: [<ffffffff802444ee>] sys_rt_sigreturn+0x28f/0x357 Feb 19 08:40:32 osprey kernel: [<ffffffff802bae4c>] audit_syscall_entry+0x148/0x17e Feb 19 08:40:32 osprey kernel: [<ffffffff802de0a6>] vfs_writev+0x3e/0x49 Feb 19 08:40:32 osprey kernel: [<ffffffff802de0f8>] sys_writev+0x47/0x94 Feb 19 08:40:32 osprey kernel: [<ffffffff8025d2b5>] tracesys+0xdc/0xe1 Feb 19 08:40:32 osprey kernel: Feb 19 08:40:32 osprey kernel: ffff810037c142e8: redzone 1:0x170fc2a5, redzone 2:0x5a2cf071 Feb 19 08:40:39 osprey kernel: ttyS0: LSR safety check engaged!
2007/2/19, Jeremy Katz katzj@redhat.com:
On Mon, 2007-02-19 at 07:11 -0600, Jay Cliburn wrote:
On Mon, 19 Feb 2007 09:11:10 +0000 Richard Hughes hughsient@gmail.com wrote:
Well, there's a link to quite an old presentation I wrote
I've also attached the pm-utils README file from CVS which might help.
Thanks a lot for this info Richard. I really appreciate it.
So to make my nic driver suspend (instead of being removed with "modprobe -r"), I need only add the module name to the SUSPEND_MODULES line of /etc/pm/config? Like this? (my driver name is atl1)
The default is for the driver to be suspended normally; SUSPEND_MODULES is to list (broken) modules that have to be removed and reinserted around the suspend process.
Speaking of SUSPEND_MODULES, there seems to be a bug in /etc/pm/functions that causes the parsing to fail if more than one modules are listed (in my case, /etc/pm/config lists "button", but I need to have it unload ath_pci as well)
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230488
--- Jay Cliburn jacliburn@bellsouth.net wrote:
I'm trying to hack/test a network driver's ability to suspend, resume, and wake-on-lan (while suspended). This is on a rawhide x86_64 desktop system. Is the Fedora pm-stuff documented anywhere? I can't seem to find anything on the wiki, and the only related manpage is for pm-pmu.
I would specifically like to know the process for moving to a new swap partition(file?) or creating a new one after install. I.e. how the whole suspend1 hibernate pulls that in. Does mkinitrd pull in the first swap entry from fstab? Is there any user documentation that explains limitations. I.e. is it possible to use swapfiles now with the default suspend. I admit, my case of using the atrpms suspend2 packages probably makes my case unsupportable, but it does seem to me that suspend1 was added in fc5 with no documentation, and I haven't run into any documentation since.
Just my 2 cents worth of end user confusion...
-dmc/jdog
P.S. also, if anyone can help me with suspend2, the cpuspeed management seems to stop working on my core duo after the first hibernate, and occasionally I get in a state where hibernation fails and the machine enters swap thrash effectively failure mode. I'm sure the answer is "suspend2 is crap", but having to use swap partitions I find rather crappy as well. (again, if that limitation of default hibernate in fc6 is gone, I'd love to be pointed towards any kind of reasonable documentation. Also, can default fc6 suspend do hibernate to lvm swap partition?).
____________________________________________________________________________________ Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097
-
Jane Dogalt -
Jay Cliburn -
Jeremy Katz -
Joshua Baker-LePain -
Michel Salim -
Richard Hughes