suspending to disk on FC6 not working

suspending to disk on FC6 not working

[Louis Garcia]

When I first installed FC6 test 2 suspend to disk worked on my box which
is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
has stopped working. Now kernel-2.6.18 has come out and I'm having the
same problems. I have tried to get this resolved on there mailing list
but it's not high on there things todo. I would like to debug suspend to
see what is happening. What is the proper way to do this? Has this been
discussed before? Is there a separate mailing-list for suspend?

-Louis

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> When I first installed FC6 test 2 suspend to disk worked on my box which
> is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> has stopped working. Now kernel-2.6.18 has come out and I'm having the
> same problems. I have tried to get this resolved on there mailing list
> but it's not high on there things todo. I would like to debug suspend to
> see what is happening. What is the proper way to do this? Has this been
> discussed before? Is there a separate mailing-list for suspend?

Generally you're not giving enough information to trace the problem.

First, what doesn't work, the suspend to disk or the resume?

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > When I first installed FC6 test 2 suspend to disk worked on my box which
> > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > same problems. I have tried to get this resolved on there mailing list
> > but it's not high on there things todo. I would like to debug suspend to
> > see what is happening. What is the proper way to do this? Has this been
> > discussed before? Is there a separate mailing-list for suspend?
> 
> Generally you're not giving enough information to trace the problem.
> 
> First, what doesn't work, the suspend to disk or the resume?
> 
> Rafael
> 
> 

Suspend to disk does not work. When trying to suspend, from gnome, it
goes normally. The power button blinks and then restarts. I'm back to
the screensaver lock screen but the mouse and keyboard are dead.

-Louis

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > same problems. I have tried to get this resolved on there mailing list
> > > but it's not high on there things todo. I would like to debug suspend to
> > > see what is happening. What is the proper way to do this? Has this been
> > > discussed before? Is there a separate mailing-list for suspend?
> > 
> > Generally you're not giving enough information to trace the problem.
> > 
> > First, what doesn't work, the suspend to disk or the resume?
> > 
> > Rafael
> > 
> > 
> 
> Suspend to disk does not work. When trying to suspend, from gnome, it
> goes normally. The power button blinks and then restarts. I'm back to
> the screensaver lock screen but the mouse and keyboard are dead.

Can you please try booting the kernel with init=/bin/bash, mount /proc,
mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > same problems. I have tried to get this resolved on there mailing list
> > > > but it's not high on there things todo. I would like to debug suspend to
> > > > see what is happening. What is the proper way to do this? Has this been
> > > > discussed before? Is there a separate mailing-list for suspend?
> > > 
> > > Generally you're not giving enough information to trace the problem.
> > > 
> > > First, what doesn't work, the suspend to disk or the resume?
> > > 
> > > Rafael
> > > 
> > > 
> > 
> > Suspend to disk does not work. When trying to suspend, from gnome, it
> > goes normally. The power button blinks and then restarts. I'm back to
> > the screensaver lock screen but the mouse and keyboard are dead.
> 
> Can you please try booting the kernel with init=/bin/bash, mount /proc,
> mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> 
> Rafael
> 
> 
After the echo command the box turned off. The power button was not
blinking. I restarted it and went into grub, linux booted into bash. 

When suspend was working the power button flashed and when I pressed it
the box booted right into linux and the screensaver lock screen
bypassing grub altogether.

-Louis

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > 
> > > > Generally you're not giving enough information to trace the problem.
> > > > 
> > > > First, what doesn't work, the suspend to disk or the resume?
> > > > 
> > > > Rafael
> > > > 
> > > > 
> > > 
> > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > goes normally. The power button blinks and then restarts. I'm back to
> > > the screensaver lock screen but the mouse and keyboard are dead.
> > 
> > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > 
> > Rafael
> > 
> > 
> After the echo command the box turned off. The power button was not
> blinking. I restarted it and went into grub,

Did you append init=/bin/bash to the kernel command line after it had gone
into GRUB?

> linux booted into bash.

Had it been displaying a progress meter before the bash came up?

> When suspend was working the power button flashed and when I pressed it
> the box booted right into linux and the screensaver lock screen
> bypassing grub altogether.

That's because if you suspend "normally", some scripts run before the suspend
that change your GRUB configuration and use the "platform" suspend method.
However, the problem seems to be on much lower level and to debug it we need
to bypass these things.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Mon, 2006-09-25 at 22:15 +0200, Rafael J. Wysocki wrote:
> On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> > On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > > 
> > > > > Generally you're not giving enough information to trace the problem.
> > > > > 
> > > > > First, what doesn't work, the suspend to disk or the resume?
> > > > > 
> > > > > Rafael
> > > > > 
> > > > > 
> > > > 
> > > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > > goes normally. The power button blinks and then restarts. I'm back to
> > > > the screensaver lock screen but the mouse and keyboard are dead.
> > > 
> > > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > > 
> > > Rafael
> > > 
> > > 
> > After the echo command the box turned off. The power button was not
> > blinking. I restarted it and went into grub,
> 
> Did you append init=/bin/bash to the kernel command line after it had gone
> into GRUB?

No, first I booted with init=/bin/bash. Then I did the things you said,
When the box was off I booted normally. You saying I should append
init=/bin/bash before and after trying to suspend.

> > linux booted into bash.
> 
> Had it been displaying a progress meter before the bash came up?

Never saw a meter before.

> > When suspend was working the power button flashed and when I pressed it
> > the box booted right into linux and the screensaver lock screen
> > bypassing grub altogether.
> 
> That's because if you suspend "normally", some scripts run before the suspend
> that change your GRUB configuration and use the "platform" suspend method.
> However, the problem seems to be on much lower level and to debug it we need
> to bypass these things.

Yes, something in the kernel I assume. How do I debug this further? 

> Greetings,
> Rafael

-Louis

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Tuesday, 26 September 2006 01:04, Louis Garcia wrote:
> On Mon, 2006-09-25 at 22:15 +0200, Rafael J. Wysocki wrote:
> > On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> > > On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > > > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > > > 
> > > > > > Generally you're not giving enough information to trace the problem.
> > > > > > 
> > > > > > First, what doesn't work, the suspend to disk or the resume?
> > > > > > 
> > > > > > Rafael
> > > > > > 
> > > > > > 
> > > > > 
> > > > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > > > goes normally. The power button blinks and then restarts. I'm back to
> > > > > the screensaver lock screen but the mouse and keyboard are dead.
> > > > 
> > > > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > > > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > > > 
> > > > Rafael
> > > > 
> > > > 
> > > After the echo command the box turned off. The power button was not
> > > blinking. I restarted it and went into grub,
> > 
> > Did you append init=/bin/bash to the kernel command line after it had gone
> > into GRUB?
> 
> No, first I booted with init=/bin/bash. Then I did the things you said,
> When the box was off I booted normally. You saying I should append
> init=/bin/bash before and after trying to suspend.

Well, it shouldn't matter if you append init=/bin/bash after trying to
suspend, but if the shell appears without it, this means the system actually
suspended and resumed.

> > > linux booted into bash.
> > 
> > Had it been displaying a progress meter before the bash came up?
> 
> Never saw a meter before.
> 
> > > When suspend was working the power button flashed and when I pressed it
> > > the box booted right into linux and the screensaver lock screen
> > > bypassing grub altogether.
> > 
> > That's because if you suspend "normally", some scripts run before the suspend
> > that change your GRUB configuration and use the "platform" suspend method.
> > However, the problem seems to be on much lower level and to debug it we need
> > to bypass these things.
> 
> Yes, something in the kernel I assume. How do I debug this further? 

Please boot the kernel with "2" appended to the command line, so the system
goes to the 2nd runlevel (ie. without network servers and X).  Then log in
as root, do "echo 8 > /proc/sys/kernel/printk" and
"echo disk > /sys/power/state".  The system should suspend to disk and power
off the machine.  If it doesn't do that (ie. if it returns to the shell
immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
to me.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Louis Garcia]

[-- Attachment #1: Type: text/plain, Size: 3736 bytes --]

On Tue, 2006-09-26 at 12:00 +0200, Rafael J. Wysocki wrote:
> On Tuesday, 26 September 2006 01:04, Louis Garcia wrote:
> > On Mon, 2006-09-25 at 22:15 +0200, Rafael J. Wysocki wrote:
> > > On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> > > > On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > > > > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > > > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > > > > 
> > > > > > > Generally you're not giving enough information to trace the problem.
> > > > > > > 
> > > > > > > First, what doesn't work, the suspend to disk or the resume?
> > > > > > > 
> > > > > > > Rafael
> > > > > > > 
> > > > > > > 
> > > > > > 
> > > > > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > > > > goes normally. The power button blinks and then restarts. I'm back to
> > > > > > the screensaver lock screen but the mouse and keyboard are dead.
> > > > > 
> > > > > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > > > > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > > > > 
> > > > > Rafael
> > > > > 
> > > > > 
> > > > After the echo command the box turned off. The power button was not
> > > > blinking. I restarted it and went into grub,
> > > 
> > > Did you append init=/bin/bash to the kernel command line after it had gone
> > > into GRUB?
> > 
> > No, first I booted with init=/bin/bash. Then I did the things you said,
> > When the box was off I booted normally. You saying I should append
> > init=/bin/bash before and after trying to suspend.
> 
> Well, it shouldn't matter if you append init=/bin/bash after trying to
> suspend, but if the shell appears without it, this means the system actually
> suspended and resumed.
> 
> > > > linux booted into bash.
> > > 
> > > Had it been displaying a progress meter before the bash came up?
> > 
> > Never saw a meter before.
> > 
> > > > When suspend was working the power button flashed and when I pressed it
> > > > the box booted right into linux and the screensaver lock screen
> > > > bypassing grub altogether.
> > > 
> > > That's because if you suspend "normally", some scripts run before the suspend
> > > that change your GRUB configuration and use the "platform" suspend method.
> > > However, the problem seems to be on much lower level and to debug it we need
> > > to bypass these things.
> > 
> > Yes, something in the kernel I assume. How do I debug this further? 
> 
> Please boot the kernel with "2" appended to the command line, so the system
> goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> as root, do "echo 8 > /proc/sys/kernel/printk" and
> "echo disk > /sys/power/state".  The system should suspend to disk and power
> off the machine.  If it doesn't do that (ie. if it returns to the shell
> immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> to me.

The system didn't power off, it returned to the shell. I attached dmesg.

> Greetings,
> Rafael

-Louis

[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 22398 bytes --]

Linux version 2.6.18-1.2693.fc6 (brewbuilder@hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20060920 (Red Hat 4.1.1-24)) #1 SMP Fri Sep 22 18:03:54 EDT 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002ff77000 (usable)
 BIOS-e820: 000000002ff77000 - 000000002ff79000 (ACPI NVS)
 BIOS-e820: 000000002ff79000 - 0000000030000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
 BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
767MB LOWMEM available.
found SMP MP-table at 000fe710
Using x86 segment limits to approximate NX protection
On node 0 totalpages: 196471
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 192375 pages, LIFO batch:31
DMI 2.3 present.
Using APIC driver default
ACPI: RSDP (v000 DELL                                  ) @ 0x000fd550
ACPI: RSDT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd564
ACPI: FADT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd598
ACPI: SSDT (v001   DELL    st_ex 0x00001000 MSFT 0x0100000d) @ 0xfffe5d92
ACPI: MADT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd60c
ACPI: BOOT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd678
ACPI: DSDT (v001   DELL    dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
Detected 1993.997 MHz processor.
Built 1 zonelists.  Total pages: 196471
Kernel command line: ro root=LABEL=/1 2
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0820000 soft=c0800000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:    8
... MAX_LOCK_DEPTH:          30
... MAX_LOCKDEP_KEYS:        2048
... CLASSHASH_SIZE:           1024
... MAX_LOCKDEP_ENTRIES:     8192
... MAX_LOCKDEP_CHAINS:      8192
... CHAINHASH_SIZE:          4096
 memory used by lock dependency info: 696 kB
 per task-struct memory footprint: 1200 bytes
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 770196k/785884k available (2141k kernel code, 14948k reserved, 1128k data, 240k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3993.42 BogoMIPS (lpj=7986854)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: 3febf3ff 00000000 00000000 00000080 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
CPU0: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
Total of 1 processors activated (3993.42 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Brought up 1 CPUs
sizeof(vma)=84 bytes
sizeof(page)=32 bytes
sizeof(inode)=568 bytes
sizeof(dentry)=160 bytes
sizeof(ext3inode)=804 bytes
sizeof(buffer_head)=52 bytes
sizeof(skbuff)=172 bytes
checking if image is initramfs... it is
Freeing initrd memory: 1360k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfbe9e, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
PM: Adding info for acpi:acpi
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.1
PM: Adding info for pci:0000:00:1f.2
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.4
PM: Adding info for pci:0000:01:00.0
PM: Adding info for pci:0000:01:00.1
PM: Adding info for pci:0000:02:08.0
PM: Adding info for pci:0000:02:09.0
PM: Adding info for pci:0000:02:09.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
PM: Adding info for No Bus:pnp0
PM: Adding info for pnp:00:00
PM: Adding info for pnp:00:01
PM: Adding info for pnp:00:02
PM: Adding info for pnp:00:03
PM: Adding info for pnp:00:04
PM: Adding info for pnp:00:05
PM: Adding info for pnp:00:06
PM: Adding info for pnp:00:07
PM: Adding info for pnp:00:08
PM: Adding info for pnp:00:09
PM: Adding info for pnp:00:0a
PM: Adding info for pnp:00:0b
pnp: PnP ACPI: found 12 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
pnp: 00:0b: ioport range 0x800-0x85f could not be reserved
pnp: 00:0b: ioport range 0xc00-0xc7f has been reserved
pnp: 00:0b: ioport range 0x860-0x8ff could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: e000-efff
  MEM window: ff800000-ff9fffff
  PREFETCH window: e8000000-f7ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: d000-dfff
  MEM window: ff600000-ff7fffff
  PREFETCH window: 40000000-400fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 9, 2097152 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
PM: Adding info for platform:pcspkr
Simple Boot Flag at 0x7a set to 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1159303729.944:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key E4C973ACF8B7482
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PM: Adding info for platform:vesafb.0
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x2
PM: Adding info for No Bus:pnp1
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel i850 Chipset.
agpgart: AGP aperture is 128M @ 0xe0000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PM: Adding info for platform:serial8250
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
PM: Adding info for No Bus:isa
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 4
ICH2: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST3120026A, ATA DISK drive
PM: Adding info for No Bus:ide0
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
PM: Adding info for ide:0.0
Probing IDE interface ide1...
hdc: PIONEER DVD-RW DVR-110D, ATAPI CD/DVD-ROM drive
PM: Adding info for No Bus:ide1
ide1 at 0x170-0x177,0x376 on irq 15
PM: Adding info for ide:1.0
hda: max request size: 512KiB
hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
ide-floppy driver 0.99.newide
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio0
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Time: tsc clocksource has been installed.
PM: Adding info for serio:serio1
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory: 240k freed
Write protecting the kernel read-only data: 400k
input: AT Translated Set 2 keyboard as /class/input/input0
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 169, io base 0x0000ff80
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev1.1_ep81
ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1f.4 to 64
uhci_hcd 0000:00:1f.4: UHCI Host Controller
uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1f.4: irq 177, io base 0x0000ff60
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev2.1_ep81
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
usb 1-1: new full speed USB device using uhci_hcd and address 2
input: ImPS/2 Logitech Wheel Mouse as /class/input/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
PM: Adding info for usb:1-1
PM: Adding info for No Bus:usbdev1.2_ep00
usb 1-1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-1:1.0
PM: Adding info for No Bus:usbdev1.2_ep87
PM: Adding info for usb:1-1:1.1
PM: Adding info for usb:1-1:1.2
PM: Adding info for usb:1-1:1.3
audit(1159303736.576:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1542 types, 162 bools, 1 sens, 1024 cats
security:  58 classes, 47701 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev hda3, type ext3), uses xattr
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
audit(1159303736.884:3): policy loaded auid=4294967295
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 17 (level, low) -> IRQ 185
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:02:08.0: 3Com PCI 3c905C Tornado at f0836c00.
hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
gameport: EMU10K1 is pci0000:02:09.1/gameport0, io 0xdc58, speed 917kHz
PM: Adding info for gameport:gameport0
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 185
PM: Adding info for No Bus:i2c-0
input: PC Speaker as /class/input/input2
PM: Adding info for No Bus:usbdev1.2_ep86
cannot find the slot for index 0 (range 0-0)
EMU10K1_Audigy: probe of 0000:02:09.0 failed with error -12
2:3:1: cannot set freq 0 to ep 0x86
PM: Removing info for No Bus:usbdev1.2_ep86
PM: Adding info for No Bus:usbdev1.2_ep86
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
PM: Adding info for platform:floppy.0
Intel 82802 RNG detected
2:3:2: cannot set freq 0 to ep 0x86
PM: Removing info for No Bus:usbdev1.2_ep86
PM: Adding info for No Bus:usbdev1.2_ep86
PM: Removing info for No Bus:usbdev1.2_ep86
usbcore: registered new driver snd-usb-audio
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [VBTN]
ibm_acpi: ec object not found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
EXT3 FS on hda3, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda2, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda6, type ext3), uses xattr
Adding 1020088k swap on /dev/hda5.  Priority:-1 extents:1 across:1020088k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (6139 buckets, 49112 max) - 228 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead.
eth0:  setting full-duplex.
Bluetooth: Core ver 2.10
PM: Adding info for platform:bluetooth
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
eth0: no IPv6 routers present
Disabling non-boot CPUs ...
Stopping tasks: ====================================|
Shrinking memory...  \b-\bdone (0 pages freed)
platform bluetooth: freeze
platform floppy.0: freeze
snd-usb-audio 1-1:1.3: freeze
snd-usb-audio 1-1:1.3: no suspend for driver snd-usb-audio?
snd-usb-audio 1-1:1.2: freeze
snd-usb-audio 1-1:1.2: no suspend for driver snd-usb-audio?
usb 1-1:1.1: PM: suspend 1-->1
 usbdev1.2_ep87: PM: suspend 0->1, parent 1-1:1.0 already 1
usb 1-1:1.0: PM: suspend 1-->1
usb 1-1: freeze
hub 2-0:1.0: freeze
usb usb2: freeze
hub 1-0:1.0: freeze
usb usb1: freeze
i8042 i8042: freeze
ide-cdrom 1.0: freeze
ide-disk 0.0: freeze
serial8250 serial8250: freeze
platform vesafb.0: freeze
pcspkr pcspkr: freeze
system 00:0b: freeze
parport_pc 00:0a: freeze
pnp: Device 00:0a disabled.
serial 00:09: freeze
pnp: Device 00:09 disabled.
i8042 aux 00:08: freeze
i8042 kbd 00:07: freeze
pnp 00:06: freeze
pnp 00:05: freeze
pnp 00:04: freeze
pnp 00:03: freeze
pnp 00:02: freeze
pnp 00:01: freeze
system 00:00: freeze
Emu10k1_gameport 0000:02:09.1: freeze
pci 0000:02:09.0: freeze
3c59x 0000:02:08.0: freeze
ACPI: PCI interrupt for device 0000:02:08.0 disabled
pci 0000:01:00.1: freeze
pci 0000:01:00.0: freeze
uhci_hcd 0000:00:1f.4: freeze
ACPI: PCI interrupt for device 0000:00:1f.4 disabled
i801_smbus 0000:00:1f.3: freeze
uhci_hcd 0000:00:1f.2: freeze
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
PIIX_IDE 0000:00:1f.1: freeze
pci 0000:00:1f.0: freeze
pci 0000:00:1e.0: freeze
pci 0000:00:01.0: freeze
agpgart-intel 0000:00:00.0: freeze
acpi acpi: freeze
PM: snapshotting memory.
Class driver suspend failed for cpu0
Could not power down device &q->lock: error -22
Some devices failed to power down, aborting suspend
acpi acpi: resuming
agpgart-intel 0000:00:00.0: resuming
pci 0000:00:01.0: resuming
pci 0000:00:1e.0: resuming
PCI: Setting latency timer of device 0000:00:1e.0 to 64
pci 0000:00:1f.0: resuming
PIIX_IDE 0000:00:1f.1: resuming
uhci_hcd 0000:00:1f.2: resuming
PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1f.2 to 64
i801_smbus 0000:00:1f.3: resuming
uhci_hcd 0000:00:1f.4: resuming
PCI: Enabling device 0000:00:1f.4 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1f.4 to 64
usb usb2: root hub lost power or was reset
pci 0000:01:00.0: resuming
pci 0000:01:00.1: resuming
3c59x 0000:02:08.0: resuming
PM: Writing back config space on device 0000:02:08.0 at offset f (was a0a0100, writing a0a010a)
PM: Writing back config space on device 0000:02:08.0 at offset c (was 0, writing ff700000)
PM: Writing back config space on device 0000:02:08.0 at offset 5 (was 0, writing ff6ffc00)
PM: Writing back config space on device 0000:02:08.0 at offset 4 (was 1, writing dc81)
PM: Writing back config space on device 0000:02:08.0 at offset 3 (was 0, writing 4010)
PM: Writing back config space on device 0000:02:08.0 at offset 1 (was 2100000, writing 2100117)
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 17 (level, low) -> IRQ 185
eth0:  setting full-duplex.
pci 0000:02:09.0: resuming
Emu10k1_gameport 0000:02:09.1: resuming
system 00:00: resuming
pnp 00:01: resuming
pnp 00:02: resuming
pnp 00:03: resuming
pnp 00:04: resuming
pnp 00:05: resuming
pnp 00:06: resuming
i8042 kbd 00:07: resuming
pnp: Failed to activate device 00:07.
i8042 aux 00:08: resuming
pnp: Failed to activate device 00:08.
serial 00:09: resuming
pnp: Device 00:09 activated.
parport_pc 00:0a: resuming
pnp: Device 00:0a activated.
system 00:0b: resuming
pcspkr pcspkr: resuming
platform vesafb.0: resuming
serial8250 serial8250: resuming
ide-disk 0.0: resuming
ide-cdrom 1.0: resuming
i8042 i8042: resuming
psmouse serio0: resuming
atkbd serio1: resuming
usb usb1: resuming
hub 1-0:1.0: resuming
usb usb2: resuming
hub 2-0:1.0: resuming
usb 1-1: resuming
 usbdev1.2_ep87: PM: resume from 0, parent 1-1:1.0 still 1
snd-usb-audio 1-1:1.2: resuming
snd-usb-audio 1-1:1.2: no resume for driver snd-usb-audio?
snd-usb-audio 1-1:1.3: resuming
snd-usb-audio 1-1:1.3: no resume for driver snd-usb-audio?
platform floppy.0: resuming
platform bluetooth: resuming
Restarting tasks... done
Enabling non-boot CPUs ...

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Tuesday, 26 September 2006 23:47, Louis Garcia wrote:
> On Tue, 2006-09-26 at 12:00 +0200, Rafael J. Wysocki wrote:
> > On Tuesday, 26 September 2006 01:04, Louis Garcia wrote:
> > > On Mon, 2006-09-25 at 22:15 +0200, Rafael J. Wysocki wrote:
> > > > On Monday, 25 September 2006 21:34, Louis Garcia wrote:
> > > > > On Mon, 2006-09-25 at 20:43 +0200, Rafael J. Wysocki wrote:
> > > > > > On Monday, 25 September 2006 19:10, Louis Garcia wrote:
> > > > > > > On Mon, 2006-09-25 at 09:16 +0200, Rafael J. Wysocki wrote:
> > > > > > > > On Monday, 25 September 2006 00:55, Louis Garcia wrote:
> > > > > > > > > When I first installed FC6 test 2 suspend to disk worked on my box which
> > > > > > > > > is a Dell dimension 8200 (P4). During the kernel-2.6.17-xxx updates this
> > > > > > > > > has stopped working. Now kernel-2.6.18 has come out and I'm having the
> > > > > > > > > same problems. I have tried to get this resolved on there mailing list
> > > > > > > > > but it's not high on there things todo. I would like to debug suspend to
> > > > > > > > > see what is happening. What is the proper way to do this? Has this been
> > > > > > > > > discussed before? Is there a separate mailing-list for suspend?
> > > > > > > > 
> > > > > > > > Generally you're not giving enough information to trace the problem.
> > > > > > > > 
> > > > > > > > First, what doesn't work, the suspend to disk or the resume?
> > > > > > > > 
> > > > > > > > Rafael
> > > > > > > > 
> > > > > > > > 
> > > > > > > 
> > > > > > > Suspend to disk does not work. When trying to suspend, from gnome, it
> > > > > > > goes normally. The power button blinks and then restarts. I'm back to
> > > > > > > the screensaver lock screen but the mouse and keyboard are dead.
> > > > > > 
> > > > > > Can you please try booting the kernel with init=/bin/bash, mount /proc,
> > > > > > mount /sys, do "/sbin/swapon -a" and "echo disk > /sys/power/state"?
> > > > > > 
> > > > > > Rafael
> > > > > > 
> > > > > > 
> > > > > After the echo command the box turned off. The power button was not
> > > > > blinking. I restarted it and went into grub,
> > > > 
> > > > Did you append init=/bin/bash to the kernel command line after it had gone
> > > > into GRUB?
> > > 
> > > No, first I booted with init=/bin/bash. Then I did the things you said,
> > > When the box was off I booted normally. You saying I should append
> > > init=/bin/bash before and after trying to suspend.
> > 
> > Well, it shouldn't matter if you append init=/bin/bash after trying to
> > suspend, but if the shell appears without it, this means the system actually
> > suspended and resumed.
> > 
> > > > > linux booted into bash.
> > > > 
> > > > Had it been displaying a progress meter before the bash came up?
> > > 
> > > Never saw a meter before.
> > > 
> > > > > When suspend was working the power button flashed and when I pressed it
> > > > > the box booted right into linux and the screensaver lock screen
> > > > > bypassing grub altogether.
> > > > 
> > > > That's because if you suspend "normally", some scripts run before the suspend
> > > > that change your GRUB configuration and use the "platform" suspend method.
> > > > However, the problem seems to be on much lower level and to debug it we need
> > > > to bypass these things.
> > > 
> > > Yes, something in the kernel I assume. How do I debug this further? 
> > 
> > Please boot the kernel with "2" appended to the command line, so the system
> > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > to me.
> 
> The system didn't power off, it returned to the shell. I attached dmesg.

Thanks.

Pavel, it looks like we have a problem with the CPU suspend on this box:

acpi acpi: freeze
PM: snapshotting memory.
Class driver suspend failed for cpu0
Could not power down device &q->lock: error -22
Some devices failed to power down, aborting suspend
acpi acpi: resuming

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Pavel Machek]

Hi!

> > > Please boot the kernel with "2" appended to the command line, so the system
> > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > to me.
> > 
> > The system didn't power off, it returned to the shell. I attached dmesg.
> 
> Thanks.
> 
> Pavel, it looks like we have a problem with the CPU suspend on this box:
> 
> acpi acpi: freeze
> PM: snapshotting memory.
> Class driver suspend failed for cpu0
> Could not power down device &q->lock: error -22
> Some devices failed to power down, aborting suspend
> acpi acpi: resuming

That looks like cpufreq/acpi, no?

Can we get bugzilla.kernel.org report?

Can you try without acpi processor and cpufreq?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> Hi!
> 
> > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > to me.
> > > 
> > > The system didn't power off, it returned to the shell. I attached dmesg.
> > 
> > Thanks.
> > 
> > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > 
> > acpi acpi: freeze
> > PM: snapshotting memory.
> > Class driver suspend failed for cpu0
> > Could not power down device &q->lock: error -22
> > Some devices failed to power down, aborting suspend
> > acpi acpi: resuming
> 
> That looks like cpufreq/acpi, no?
> 
> Can we get bugzilla.kernel.org report?

Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188

> Can you try without acpi processor and cpufreq?

First, please try to remove the acpi_cpufreq module before the suspend.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > Hi!
> > 
> > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > to me.
> > > > 
> > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > 
> > > Thanks.
> > > 
> > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > 
> > > acpi acpi: freeze
> > > PM: snapshotting memory.
> > > Class driver suspend failed for cpu0
> > > Could not power down device &q->lock: error -22
> > > Some devices failed to power down, aborting suspend
> > > acpi acpi: resuming
> > 
> > That looks like cpufreq/acpi, no?
> > 
> > Can we get bugzilla.kernel.org report?
> 
> Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> 
> > Can you try without acpi processor and cpufreq?
> 
> First, please try to remove the acpi_cpufreq module before the suspend.
> 
> Greetings,
> Rafael

Yep sure is. I removed the acpi_cpufreq module and my box suspended and
resumed nicely, from gnome even.

This has not been working since 2.6.17. Something in cpufreq in the
2.6.18pre series broke.

-Louis

Re: suspending to disk on FC6 not working

[Pavel Machek]

On Tue 2006-09-26 18:39:13, Louis Garcia wrote:
> On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > > to me.
> > > > > 
> > > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > > 
> > > > Thanks.
> > > > 
> > > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > > 
> > > > acpi acpi: freeze
> > > > PM: snapshotting memory.
> > > > Class driver suspend failed for cpu0
> > > > Could not power down device &q->lock: error -22
> > > > Some devices failed to power down, aborting suspend
> > > > acpi acpi: resuming
> > > 
> > > That looks like cpufreq/acpi, no?
> > > 
> > > Can we get bugzilla.kernel.org report?
> > 
> > Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> > 
> > > Can you try without acpi processor and cpufreq?
> > 
> > First, please try to remove the acpi_cpufreq module before the suspend.
> > 
> > Greetings,
> > Rafael
> 
> Yep sure is. I removed the acpi_cpufreq module and my box suspended and
> resumed nicely, from gnome even.
> 
> This has not been working since 2.6.17. Something in cpufreq in the
> 2.6.18pre series broke.

bugzilla time, cc dave jones and acpi people.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Wednesday, 27 September 2006 00:45, Pavel Machek wrote:
> On Tue 2006-09-26 18:39:13, Louis Garcia wrote:
> > On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > > > Hi!
> > > > 
> > > > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > > > to me.
> > > > > > 
> > > > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > > > 
> > > > > Thanks.
> > > > > 
> > > > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > > > 
> > > > > acpi acpi: freeze
> > > > > PM: snapshotting memory.
> > > > > Class driver suspend failed for cpu0
> > > > > Could not power down device &q->lock: error -22
> > > > > Some devices failed to power down, aborting suspend
> > > > > acpi acpi: resuming
> > > > 
> > > > That looks like cpufreq/acpi, no?
> > > > 
> > > > Can we get bugzilla.kernel.org report?
> > > 
> > > Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> > > 
> > > > Can you try without acpi processor and cpufreq?
> > > 
> > > First, please try to remove the acpi_cpufreq module before the suspend.
> > > 
> > > Greetings,
> > > Rafael
> > 
> > Yep sure is. I removed the acpi_cpufreq module and my box suspended and
> > resumed nicely, from gnome even.
> > 
> > This has not been working since 2.6.17. Something in cpufreq in the
> > 2.6.18pre series broke.
> 
> bugzilla time, cc dave jones and acpi people.

We _already_ _have_ a bugzilla entry for that (please see above).

Louis, could you please add a "me too" to the bugzilla entry at the above
address?

Greetings,
Rafael 


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Pavel Machek]

On Wed 2006-09-27 00:54:13, Rafael J. Wysocki wrote:
> On Wednesday, 27 September 2006 00:45, Pavel Machek wrote:
> > On Tue 2006-09-26 18:39:13, Louis Garcia wrote:
> > > On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> > > > On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > > > > Hi!
> > > > > 
> > > > > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > > > > to me.
> > > > > > > 
> > > > > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > > > > 
> > > > > > Thanks.
> > > > > > 
> > > > > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > > > > 
> > > > > > acpi acpi: freeze
> > > > > > PM: snapshotting memory.
> > > > > > Class driver suspend failed for cpu0
> > > > > > Could not power down device &q->lock: error -22
> > > > > > Some devices failed to power down, aborting suspend
> > > > > > acpi acpi: resuming
> > > > > 
> > > > > That looks like cpufreq/acpi, no?
> > > > > 
> > > > > Can we get bugzilla.kernel.org report?
> > > > 
> > > > Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> > > > 
> > > > > Can you try without acpi processor and cpufreq?
> > > > 
> > > > First, please try to remove the acpi_cpufreq module before the suspend.
> > > > 
> > > > Greetings,
> > > > Rafael
> > > 
> > > Yep sure is. I removed the acpi_cpufreq module and my box suspended and
> > > resumed nicely, from gnome even.
> > > 
> > > This has not been working since 2.6.17. Something in cpufreq in the
> > > 2.6.18pre series broke.
> > 
> > bugzilla time, cc dave jones and acpi people.
> 
> We _already_ _have_ a bugzilla entry for that (please see above).

Sorry.

> Louis, could you please add a "me too" to the bugzilla entry at the above
> address?

Also state that it worked okay in 2.6.17...

...hmm, and at this point you should be able to git bisect...

...or perhaps it is easier to add printks into acpi_cpufreq and find
_why_ its class suspend fails?
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Wed, 2006-09-27 at 00:58 +0200, Pavel Machek wrote:
> On Wed 2006-09-27 00:54:13, Rafael J. Wysocki wrote:
> > On Wednesday, 27 September 2006 00:45, Pavel Machek wrote:
> > > On Tue 2006-09-26 18:39:13, Louis Garcia wrote:
> > > > On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> > > > > On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > > > > > Hi!
> > > > > > 
> > > > > > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > > > > > to me.
> > > > > > > > 
> > > > > > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > > > > > 
> > > > > > > Thanks.
> > > > > > > 
> > > > > > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > > > > > 
> > > > > > > acpi acpi: freeze
> > > > > > > PM: snapshotting memory.
> > > > > > > Class driver suspend failed for cpu0
> > > > > > > Could not power down device &q->lock: error -22
> > > > > > > Some devices failed to power down, aborting suspend
> > > > > > > acpi acpi: resuming
> > > > > > 
> > > > > > That looks like cpufreq/acpi, no?
> > > > > > 
> > > > > > Can we get bugzilla.kernel.org report?
> > > > > 
> > > > > Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> > > > > 
> > > > > > Can you try without acpi processor and cpufreq?
> > > > > 
> > > > > First, please try to remove the acpi_cpufreq module before the suspend.
> > > > > 
> > > > > Greetings,
> > > > > Rafael
> > > > 
> > > > Yep sure is. I removed the acpi_cpufreq module and my box suspended and
> > > > resumed nicely, from gnome even.
> > > > 
> > > > This has not been working since 2.6.17. Something in cpufreq in the
> > > > 2.6.18pre series broke.
> > > 
> > > bugzilla time, cc dave jones and acpi people.
> > 
> > We _already_ _have_ a bugzilla entry for that (please see above).
> 
> Sorry.
> 
> > Louis, could you please add a "me too" to the bugzilla entry at the above
> > address?
> 
> Also state that it worked okay in 2.6.17...
> 
> ...hmm, and at this point you should be able to git bisect...
> 
> ...or perhaps it is easier to add printks into acpi_cpufreq and find
> _why_ its class suspend fails?

Sorry this is beyond my abilities. If you can provide a patch with the
necessary printks I can recompile and test.
 
> 								Pavel
> 

-Louis

Re: suspending to disk on FC6 not working

[Pavel Machek]

On Tue 2006-09-26 19:09:01, Louis Garcia wrote:
> On Wed, 2006-09-27 at 00:58 +0200, Pavel Machek wrote:
> > On Wed 2006-09-27 00:54:13, Rafael J. Wysocki wrote:
> > > On Wednesday, 27 September 2006 00:45, Pavel Machek wrote:
> > > > On Tue 2006-09-26 18:39:13, Louis Garcia wrote:
> > > > > On Wed, 2006-09-27 at 00:26 +0200, Rafael J. Wysocki wrote:
> > > > > > On Wednesday, 27 September 2006 00:15, Pavel Machek wrote:
> > > > > > > Hi!
> > > > > > > 
> > > > > > > > > > Please boot the kernel with "2" appended to the command line, so the system
> > > > > > > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
> > > > > > > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > > > > > > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
> > > > > > > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
> > > > > > > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
> > > > > > > > > > to me.
> > > > > > > > > 
> > > > > > > > > The system didn't power off, it returned to the shell. I attached dmesg.
> > > > > > > > 
> > > > > > > > Thanks.
> > > > > > > > 
> > > > > > > > Pavel, it looks like we have a problem with the CPU suspend on this box:
> > > > > > > > 
> > > > > > > > acpi acpi: freeze
> > > > > > > > PM: snapshotting memory.
> > > > > > > > Class driver suspend failed for cpu0
> > > > > > > > Could not power down device &q->lock: error -22
> > > > > > > > Some devices failed to power down, aborting suspend
> > > > > > > > acpi acpi: resuming
> > > > > > > 
> > > > > > > That looks like cpufreq/acpi, no?
> > > > > > > 
> > > > > > > Can we get bugzilla.kernel.org report?
> > > > > > 
> > > > > > Ah, it may be the same bug as http://bugzilla.kernel.org/show_bug.cgi?id=7188
> > > > > > 
> > > > > > > Can you try without acpi processor and cpufreq?
> > > > > > 
> > > > > > First, please try to remove the acpi_cpufreq module before the suspend.
> > > > > > 
> > > > > > Greetings,
> > > > > > Rafael
> > > > > 
> > > > > Yep sure is. I removed the acpi_cpufreq module and my box suspended and
> > > > > resumed nicely, from gnome even.
> > > > > 
> > > > > This has not been working since 2.6.17. Something in cpufreq in the
> > > > > 2.6.18pre series broke.
> > > > 
> > > > bugzilla time, cc dave jones and acpi people.
> > > 
> > > We _already_ _have_ a bugzilla entry for that (please see above).
> > 
> > Sorry.
> > 
> > > Louis, could you please add a "me too" to the bugzilla entry at the above
> > > address?
> > 
> > Also state that it worked okay in 2.6.17...
> > 
> > ...hmm, and at this point you should be able to git bisect...
> > 
> > ...or perhaps it is easier to add printks into acpi_cpufreq and find
> > _why_ its class suspend fails?
> 
> Sorry this is beyond my abilities. If you can provide a patch with the
> necessary printks I can recompile and test.

Okay, I guess that's "git bisect" for you, then. There are good
descriptions how to do it on the net ;-).
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Dave Jones]

On Wed, Sep 27, 2006 at 12:15:56AM +0200, Pavel Machek wrote:
 > Hi!
 > 
 > > > > Please boot the kernel with "2" appended to the command line, so the system
 > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
 > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
 > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
 > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
 > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
 > > > > to me.
 > > > 
 > > > The system didn't power off, it returned to the shell. I attached dmesg.
 > > 
 > > Pavel, it looks like we have a problem with the CPU suspend on this box:
 > > 
 > > acpi acpi: freeze
 > > PM: snapshotting memory.
 > > Class driver suspend failed for cpu0
 > > Could not power down device &q->lock: error -22

That's an interesting device name.

 > > Some devices failed to power down, aborting suspend
 > > acpi acpi: resuming
 > 
 > That looks like cpufreq/acpi, no?

Looking at drivers/cpufreq/cpufreq.c:cpufreq_suspend(),
There's only two ways we can fail that function. In one way,
we'll see a printk, and the other we silently -EINVAL.
Given the log doesn't show the printk, we must be failing here..

    cpu_policy = cpufreq_cpu_get(cpu);
    if (!cpu_policy)
        return -EINVAL;

cpufreq_cpu_get has a number of potential ways it could fail however,
and isn't very chatty about failing, so we've no real idea
what's falling apart there.

	Dave

Re: suspending to disk on FC6 not working

[Dave Jones]

On Tue, Sep 26, 2006 at 10:36:31PM -0400, Dave Jones wrote:
 > On Wed, Sep 27, 2006 at 12:15:56AM +0200, Pavel Machek wrote:
 >  > Hi!
 >  > 
 >  > > > > Please boot the kernel with "2" appended to the command line, so the system
 >  > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
 >  > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
 >  > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
 >  > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
 >  > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
 >  > > > > to me.
 >  > > > 
 >  > > > The system didn't power off, it returned to the shell. I attached dmesg.
 >  > > 
 >  > > Pavel, it looks like we have a problem with the CPU suspend on this box:
 >  > > 
 >  > > acpi acpi: freeze
 >  > > PM: snapshotting memory.
 >  > > Class driver suspend failed for cpu0
 >  > > Could not power down device &q->lock: error -22
 > 
 > That's an interesting device name.
 > 
 >  > > Some devices failed to power down, aborting suspend
 >  > > acpi acpi: resuming
 >  > 
 >  > That looks like cpufreq/acpi, no?
 > 
 > Looking at drivers/cpufreq/cpufreq.c:cpufreq_suspend(),
 > There's only two ways we can fail that function. In one way,
 > we'll see a printk, and the other we silently -EINVAL.
 > Given the log doesn't show the printk, we must be failing here..
 > 
 >     cpu_policy = cpufreq_cpu_get(cpu);
 >     if (!cpu_policy)
 >         return -EINVAL;
 > 
 > cpufreq_cpu_get has a number of potential ways it could fail however,
 > and isn't very chatty about failing, so we've no real idea
 > what's falling apart there.

This patch might give us some more clues.

	Dave
 
--- 1/drivers/cpufreq/cpufreq.c	2006-09-24 00:26:42.000000000 -0400
+++ 2/drivers/cpufreq/cpufreq.c	2006-09-26 22:48:49.000000000 -0400
@@ -63,27 +63,36 @@ struct cpufreq_policy *cpufreq_cpu_get(u
 	struct cpufreq_policy *data;
 	unsigned long flags;
 
-	if (cpu >= NR_CPUS)
+	if (cpu >= NR_CPUS) {
+		printk(KERN_DEBUG "cpufreq_cpu_get failed (!>=NR_CPUS)\n");
 		goto err_out;
+	}
 
 	/* get the cpufreq driver */
 	spin_lock_irqsave(&cpufreq_driver_lock, flags);
 
-	if (!cpufreq_driver)
+	if (!cpufreq_driver) {
+		printk(KERN_DEBUG "cpufreq_cpu_get failed (!driver)\n");
 		goto err_out_unlock;
+	}
 
-	if (!try_module_get(cpufreq_driver->owner))
+	if (!try_module_get(cpufreq_driver->owner)) {
+		printk(KERN_DEBUG "cpufreq_cpu_get failed (!try_module_get)\n");
 		goto err_out_unlock;
-
+	}
 
 	/* get the CPU */
 	data = cpufreq_cpu_data[cpu];
 
-	if (!data)
+	if (!data) {
+		printk(KERN_DEBUG "cpufreq_cpu_get failed (!data)\n");
 		goto err_out_put_module;
+	}
 
-	if (!kobject_get(&data->kobj))
+	if (!kobject_get(&data->kobj)) {
+		printk(KERN_DEBUG "cpufreq_cpu_get failed (!kobject_get)\n");
 		goto err_out_put_module;
+	}
 
 	spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
 	return data;

Re: suspending to disk on FC6 not working

[Louis Garcia]

[-- Attachment #1: Type: text/plain, Size: 3287 bytes --]

On Tue, 2006-09-26 at 22:51 -0400, Dave Jones wrote:
> On Tue, Sep 26, 2006 at 10:36:31PM -0400, Dave Jones wrote:
>  > On Wed, Sep 27, 2006 at 12:15:56AM +0200, Pavel Machek wrote:
>  >  > Hi!
>  >  > 
>  >  > > > > Please boot the kernel with "2" appended to the command line, so the system
>  >  > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
>  >  > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
>  >  > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
>  >  > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
>  >  > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
>  >  > > > > to me.
>  >  > > > 
>  >  > > > The system didn't power off, it returned to the shell. I attached dmesg.
>  >  > > 
>  >  > > Pavel, it looks like we have a problem with the CPU suspend on this box:
>  >  > > 
>  >  > > acpi acpi: freeze
>  >  > > PM: snapshotting memory.
>  >  > > Class driver suspend failed for cpu0
>  >  > > Could not power down device &q->lock: error -22
>  > 
>  > That's an interesting device name.
>  > 
>  >  > > Some devices failed to power down, aborting suspend
>  >  > > acpi acpi: resuming
>  >  > 
>  >  > That looks like cpufreq/acpi, no?
>  > 
>  > Looking at drivers/cpufreq/cpufreq.c:cpufreq_suspend(),
>  > There's only two ways we can fail that function. In one way,
>  > we'll see a printk, and the other we silently -EINVAL.
>  > Given the log doesn't show the printk, we must be failing here..
>  > 
>  >     cpu_policy = cpufreq_cpu_get(cpu);
>  >     if (!cpu_policy)
>  >         return -EINVAL;
>  > 
>  > cpufreq_cpu_get has a number of potential ways it could fail however,
>  > and isn't very chatty about failing, so we've no real idea
>  > what's falling apart there.
> 
> This patch might give us some more clues.
> 
> 	Dave
>  
> --- 1/drivers/cpufreq/cpufreq.c	2006-09-24 00:26:42.000000000 -0400
> +++ 2/drivers/cpufreq/cpufreq.c	2006-09-26 22:48:49.000000000 -0400
> @@ -63,27 +63,36 @@ struct cpufreq_policy *cpufreq_cpu_get(u
>  	struct cpufreq_policy *data;
>  	unsigned long flags;
>  
> -	if (cpu >= NR_CPUS)
> +	if (cpu >= NR_CPUS) {
> +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!>=NR_CPUS)\n");
>  		goto err_out;
> +	}
>  
>  	/* get the cpufreq driver */
>  	spin_lock_irqsave(&cpufreq_driver_lock, flags);
>  
> -	if (!cpufreq_driver)
> +	if (!cpufreq_driver) {
> +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!driver)\n");
>  		goto err_out_unlock;
> +	}
>  
> -	if (!try_module_get(cpufreq_driver->owner))
> +	if (!try_module_get(cpufreq_driver->owner)) {
> +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!try_module_get)\n");
>  		goto err_out_unlock;
> -
> +	}
>  
>  	/* get the CPU */
>  	data = cpufreq_cpu_data[cpu];
>  
> -	if (!data)
> +	if (!data) {
> +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!data)\n");
>  		goto err_out_put_module;
> +	}
>  
> -	if (!kobject_get(&data->kobj))
> +	if (!kobject_get(&data->kobj)) {
> +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!kobject_get)\n");
>  		goto err_out_put_module;
> +	}
>  
>  	spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
>  	return data;
> 

I recompiled the kernel with this patch an am attaching a new dmesg.

-Louis

[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 22512 bytes --]

Linux version 2.6.18-1.2693.cpufreqdebug (root@soncomputer) (gcc version 4.1.1 20060923 (Red Hat 4.1.1-25)) #1 SMP Tue Sep 26 23:49:59 EDT 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002ff77000 (usable)
 BIOS-e820: 000000002ff77000 - 000000002ff79000 (ACPI NVS)
 BIOS-e820: 000000002ff79000 - 0000000030000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
 BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
767MB LOWMEM available.
found SMP MP-table at 000fe710
Using x86 segment limits to approximate NX protection
On node 0 totalpages: 196471
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 192375 pages, LIFO batch:31
DMI 2.3 present.
Using APIC driver default
ACPI: RSDP (v000 DELL                                  ) @ 0x000fd550
ACPI: RSDT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd564
ACPI: FADT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd598
ACPI: SSDT (v001   DELL    st_ex 0x00001000 MSFT 0x0100000d) @ 0xfffe5d92
ACPI: MADT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd60c
ACPI: BOOT (v001 DELL    8200    0x00000008 ASL  0x00000061) @ 0x000fd678
ACPI: DSDT (v001   DELL    dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
Detected 1994.149 MHz processor.
Built 1 zonelists.  Total pages: 196471
Kernel command line: ro root=LABEL=/1 2
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0820000 soft=c0800000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:    8
... MAX_LOCK_DEPTH:          30
... MAX_LOCKDEP_KEYS:        2048
... CLASSHASH_SIZE:           1024
... MAX_LOCKDEP_ENTRIES:     8192
... MAX_LOCKDEP_CHAINS:      8192
... CHAINHASH_SIZE:          4096
 memory used by lock dependency info: 696 kB
 per task-struct memory footprint: 1200 bytes
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 770196k/785884k available (2141k kernel code, 14948k reserved, 1128k data, 240k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3993.21 BogoMIPS (lpj=7986423)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 3febfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: 3febf3ff 00000000 00000000 00000080 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
CPU0: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 04
Total of 1 processors activated (3993.21 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Brought up 1 CPUs
sizeof(vma)=84 bytes
sizeof(page)=32 bytes
sizeof(inode)=568 bytes
sizeof(dentry)=160 bytes
sizeof(ext3inode)=804 bytes
sizeof(buffer_head)=52 bytes
sizeof(skbuff)=172 bytes
checking if image is initramfs... it is
Freeing initrd memory: 1360k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfbe9e, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
PM: Adding info for acpi:acpi
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
Boot video device is 0000:01:00.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.1
PM: Adding info for pci:0000:00:1f.2
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.4
PM: Adding info for pci:0000:01:00.0
PM: Adding info for pci:0000:01:00.1
PM: Adding info for pci:0000:02:08.0
PM: Adding info for pci:0000:02:09.0
PM: Adding info for pci:0000:02:09.1
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 6 7 9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
PM: Adding info for No Bus:pnp0
PM: Adding info for pnp:00:00
PM: Adding info for pnp:00:01
PM: Adding info for pnp:00:02
PM: Adding info for pnp:00:03
PM: Adding info for pnp:00:04
PM: Adding info for pnp:00:05
PM: Adding info for pnp:00:06
PM: Adding info for pnp:00:07
PM: Adding info for pnp:00:08
PM: Adding info for pnp:00:09
PM: Adding info for pnp:00:0a
PM: Adding info for pnp:00:0b
pnp: PnP ACPI: found 12 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
pnp: 00:0b: ioport range 0x800-0x85f could not be reserved
pnp: 00:0b: ioport range 0xc00-0xc7f has been reserved
pnp: 00:0b: ioport range 0x860-0x8ff could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: e000-efff
  MEM window: ff800000-ff9fffff
  PREFETCH window: e8000000-f7ffffff
PCI: Bridge: 0000:00:1e.0
  IO window: d000-dfff
  MEM window: ff600000-ff7fffff
  PREFETCH window: 40000000-400fffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 9, 2097152 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
PM: Adding info for platform:pcspkr
Simple Boot Flag at 0x7a set to 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1159339388.952:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 8DB1556DF0FA334C
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PM: Adding info for platform:vesafb.0
cpufreq_cpu_get failed (!driver)
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x2
PM: Adding info for No Bus:pnp1
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel i850 Chipset.
agpgart: AGP aperture is 128M @ 0xe0000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PM: Adding info for platform:serial8250
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
PM: Adding info for No Bus:isa
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 4
ICH2: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST3120026A, ATA DISK drive
PM: Adding info for No Bus:ide0
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
PM: Adding info for ide:0.0
Probing IDE interface ide1...
hdc: PIONEER DVD-RW DVR-110D, ATAPI CD/DVD-ROM drive
PM: Adding info for No Bus:ide1
ide1 at 0x170-0x177,0x376 on irq 15
PM: Adding info for ide:1.0
hda: max request size: 512KiB
hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
ide-floppy driver 0.99.newide
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio0
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
PM: Adding info for serio:serio1
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory: 240k freed
Write protecting the kernel read-only data: 401k
Time: tsc clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 169, io base 0x0000ff80
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev1.1_ep81
ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1f.4 to 64
uhci_hcd 0000:00:1f.4: UHCI Host Controller
uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1f.4: irq 177, io base 0x0000ff60
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev2.1_ep81
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
usb 1-1: new full speed USB device using uhci_hcd and address 2
input: ImPS/2 Logitech Wheel Mouse as /class/input/input1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
PM: Adding info for usb:1-1
PM: Adding info for No Bus:usbdev1.2_ep00
usb 1-1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-1:1.0
PM: Adding info for No Bus:usbdev1.2_ep87
PM: Adding info for usb:1-1:1.1
PM: Adding info for usb:1-1:1.2
PM: Adding info for usb:1-1:1.3
audit(1159339395.588:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1542 types, 162 bools, 1 sens, 1024 cats
security:  58 classes, 47701 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev hda3, type ext3), uses xattr
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
audit(1159339395.896:3): policy loaded auid=4294967295
hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
input: PC Speaker as /class/input/input2
gameport: EMU10K1 is pci0000:02:09.1/gameport0, io 0xdc58, speed 932kHz
PM: Adding info for gameport:gameport0
PM: Adding info for No Bus:usbdev1.2_ep86
cannot find the slot for index 0 (range 0-0)
EMU10K1_Audigy: probe of 0000:02:09.0 failed with error -12
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 185
PM: Adding info for No Bus:i2c-0
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
PM: Adding info for platform:floppy.0
2:3:1: cannot set freq 0 to ep 0x86
PM: Removing info for No Bus:usbdev1.2_ep86
PM: Adding info for No Bus:usbdev1.2_ep86
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 17 (level, low) -> IRQ 185
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:02:08.0: 3Com PCI 3c905C Tornado at f0870c00.
2:3:2: cannot set freq 0 to ep 0x86
PM: Removing info for No Bus:usbdev1.2_ep86
PM: Adding info for No Bus:usbdev1.2_ep86
Intel 82802 RNG detected
PM: Removing info for No Bus:usbdev1.2_ep86
usbcore: registered new driver snd-usb-audio
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [VBTN]
ibm_acpi: ec object not found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
EXT3 FS on hda3, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda2, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev hda6, type ext3), uses xattr
Adding 1020088k swap on /dev/hda5.  Priority:-1 extents:1 across:1020088k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
cpufreq_cpu_get failed (!data)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (6139 buckets, 49112 max) - 228 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead.
eth0:  setting full-duplex.
cpufreq_cpu_get failed (!data)
Bluetooth: Core ver 2.10
PM: Adding info for platform:bluetooth
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
eth0: no IPv6 routers present
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Disabling non-boot CPUs ...
Stopping tasks: =====================================|
Shrinking memory...  \b-\bdone (0 pages freed)
platform bluetooth: freeze
platform floppy.0: freeze
snd-usb-audio 1-1:1.3: freeze
snd-usb-audio 1-1:1.3: no suspend for driver snd-usb-audio?
snd-usb-audio 1-1:1.2: freeze
snd-usb-audio 1-1:1.2: no suspend for driver snd-usb-audio?
usb 1-1:1.1: PM: suspend 1-->1
 usbdev1.2_ep87: PM: suspend 0->1, parent 1-1:1.0 already 1
usb 1-1:1.0: PM: suspend 1-->1
usb 1-1: freeze
hub 2-0:1.0: freeze
usb usb2: freeze
hub 1-0:1.0: freeze
usb usb1: freeze
i8042 i8042: freeze
ide-cdrom 1.0: freeze
ide-disk 0.0: freeze
serial8250 serial8250: freeze
platform vesafb.0: freeze
pcspkr pcspkr: freeze
system 00:0b: freeze
parport_pc 00:0a: freeze
pnp: Device 00:0a disabled.
serial 00:09: freeze
pnp: Device 00:09 disabled.
i8042 aux 00:08: freeze
i8042 kbd 00:07: freeze
pnp 00:06: freeze
pnp 00:05: freeze
pnp 00:04: freeze
pnp 00:03: freeze
pnp 00:02: freeze
pnp 00:01: freeze
system 00:00: freeze
Emu10k1_gameport 0000:02:09.1: freeze
pci 0000:02:09.0: freeze
3c59x 0000:02:08.0: freeze
ACPI: PCI interrupt for device 0000:02:08.0 disabled
pci 0000:01:00.1: freeze
pci 0000:01:00.0: freeze
uhci_hcd 0000:00:1f.4: freeze
ACPI: PCI interrupt for device 0000:00:1f.4 disabled
i801_smbus 0000:00:1f.3: freeze
uhci_hcd 0000:00:1f.2: freeze
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
PIIX_IDE 0000:00:1f.1: freeze
pci 0000:00:1f.0: freeze
pci 0000:00:1e.0: freeze
pci 0000:00:01.0: freeze
agpgart-intel 0000:00:00.0: freeze
acpi acpi: freeze
PM: snapshotting memory.
cpufreq_cpu_get failed (!data)
Class driver suspend failed for cpu0
Could not power down device &q->lock: error -22
Some devices failed to power down, aborting suspend
acpi acpi: resuming
agpgart-intel 0000:00:00.0: resuming
pci 0000:00:01.0: resuming
pci 0000:00:1e.0: resuming
PCI: Setting latency timer of device 0000:00:1e.0 to 64
pci 0000:00:1f.0: resuming
PIIX_IDE 0000:00:1f.1: resuming
uhci_hcd 0000:00:1f.2: resuming
PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1f.2 to 64
i801_smbus 0000:00:1f.3: resuming
uhci_hcd 0000:00:1f.4: resuming
PCI: Enabling device 0000:00:1f.4 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:1f.4[C] -> GSI 23 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1f.4 to 64
usb usb2: root hub lost power or was reset
pci 0000:01:00.0: resuming
pci 0000:01:00.1: resuming
3c59x 0000:02:08.0: resuming
PM: Writing back config space on device 0000:02:08.0 at offset f (was a0a0100, writing a0a010a)
PM: Writing back config space on device 0000:02:08.0 at offset c (was 0, writing ff700000)
PM: Writing back config space on device 0000:02:08.0 at offset 5 (was 0, writing ff6ffc00)
PM: Writing back config space on device 0000:02:08.0 at offset 4 (was 1, writing dc81)
PM: Writing back config space on device 0000:02:08.0 at offset 3 (was 0, writing 4010)
PM: Writing back config space on device 0000:02:08.0 at offset 1 (was 2100000, writing 2100117)
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 17 (level, low) -> IRQ 185
eth0:  setting full-duplex.
pci 0000:02:09.0: resuming
Emu10k1_gameport 0000:02:09.1: resuming
system 00:00: resuming
pnp 00:01: resuming
pnp 00:02: resuming
pnp 00:03: resuming
pnp 00:04: resuming
pnp 00:05: resuming
pnp 00:06: resuming
i8042 kbd 00:07: resuming
pnp: Failed to activate device 00:07.
i8042 aux 00:08: resuming
pnp: Failed to activate device 00:08.
serial 00:09: resuming
pnp: Device 00:09 activated.
parport_pc 00:0a: resuming
pnp: Device 00:0a activated.
system 00:0b: resuming
pcspkr pcspkr: resuming
platform vesafb.0: resuming
serial8250 serial8250: resuming
ide-disk 0.0: resuming
ide-cdrom 1.0: resuming
i8042 i8042: resuming
psmouse serio0: resuming
atkbd serio1: resuming
usb usb1: resuming
hub 1-0:1.0: resuming
usb usb2: resuming
hub 2-0:1.0: resuming
usb 1-1: resuming
 usbdev1.2_ep87: PM: resume from 0, parent 1-1:1.0 still 1
snd-usb-audio 1-1:1.2: resuming
snd-usb-audio 1-1:1.2: no resume for driver snd-usb-audio?
snd-usb-audio 1-1:1.3: resuming
snd-usb-audio 1-1:1.3: no resume for driver snd-usb-audio?
platform floppy.0: resuming
platform bluetooth: resuming
Restarting tasks... done
Enabling non-boot CPUs ...

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: suspending to disk on FC6 not working

[Dave Jones]

[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]

On Wed, Sep 27, 2006 at 02:55:29AM -0400, Louis Garcia wrote:

 > >  >  > > > > goes to the 2nd runlevel (ie. without network servers and X).  Then log in
 > >  >  > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
 > >  >  > > > > "echo disk > /sys/power/state".  The system should suspend to disk and power
 > >  >  > > > > off the machine.  If it doesn't do that (ie. if it returns to the shell
 > >  >  > > > > immediately), please do "dmesg > dmesg.log" and send the dmesg.log file
 > >  >  > > > > to me.
 > >  >  > > > 
 > >  >  > > > The system didn't power off, it returned to the shell. I attached dmesg.
 > >  >  > > 
 > >  >  > > Pavel, it looks like we have a problem with the CPU suspend on this box:
 > >  >  > > 
 > >  >  > > acpi acpi: freeze
 > >  >  > > PM: snapshotting memory.
 > >  >  > > Class driver suspend failed for cpu0
 > >  >  > > Could not power down device &q->lock: error -22
 > >  >  > > Some devices failed to power down, aborting suspend
 > >  >  > > acpi acpi: resuming
 > >  >  > 
 > >  >  > That looks like cpufreq/acpi, no?
 > >  > 
 > >  > Looking at drivers/cpufreq/cpufreq.c:cpufreq_suspend(),
 > >  > There's only two ways we can fail that function. In one way,
 > >  > we'll see a printk, and the other we silently -EINVAL.
 > >  > Given the log doesn't show the printk, we must be failing here..
 > >  > 
 > >  >     cpu_policy = cpufreq_cpu_get(cpu);
 > >  >     if (!cpu_policy)
 > >  >         return -EINVAL;
 > >  > 
 > >  > cpufreq_cpu_get has a number of potential ways it could fail however,
 > >  > and isn't very chatty about failing, so we've no real idea
 > >  > what's falling apart there.
 > > 
 > > This patch might give us some more clues.
 > >  
 > > --- 1/drivers/cpufreq/cpufreq.c	2006-09-24 00:26:42.000000000 -0400
 > > +++ 2/drivers/cpufreq/cpufreq.c	2006-09-26 22:48:49.000000000 -0400
 > > @@ -63,27 +63,36 @@ struct cpufreq_policy *cpufreq_cpu_get(u
 > >  	struct cpufreq_policy *data;
 > >  	unsigned long flags;
 > >  
 > > -	if (cpu >= NR_CPUS)
 > > +	if (cpu >= NR_CPUS) {
 > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!>=NR_CPUS)\n");
 > >  		goto err_out;
 > > +	}
 > >  
 > >  	/* get the cpufreq driver */
 > >  	spin_lock_irqsave(&cpufreq_driver_lock, flags);
 > >  
 > > -	if (!cpufreq_driver)
 > > +	if (!cpufreq_driver) {
 > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!driver)\n");
 > >  		goto err_out_unlock;
 > > +	}
 > >  
 > > -	if (!try_module_get(cpufreq_driver->owner))
 > > +	if (!try_module_get(cpufreq_driver->owner)) {
 > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!try_module_get)\n");
 > >  		goto err_out_unlock;
 > > -
 > > +	}
 > >  
 > >  	/* get the CPU */
 > >  	data = cpufreq_cpu_data[cpu];
 > >  
 > > -	if (!data)
 > > +	if (!data) {
 > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!data)\n");
 > >  		goto err_out_put_module;
 > > +	}
 > >  
 > > -	if (!kobject_get(&data->kobj))
 > > +	if (!kobject_get(&data->kobj)) {
 > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!kobject_get)\n");
 > >  		goto err_out_put_module;
 > > +	}
 > >  
 > >  	spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
 > >  	return data;
 > >
 > ... 
 > PM: snapshotting memory.
 > cpufreq_cpu_get failed (!data)
 > Class driver suspend failed for cpu0
 > Could not power down device &q->lock: error -22
 > Some devices failed to power down, aborting suspend

Ok, I'm not quite sure how we got into this state.  Venkatesh, any ideas ?
acpi-cpufreq got quite a few changes between .17 and .18, including the
two large 'P-state coordination' change.

Louis, I'm attaching two smaller changes that went into .18.
Can you apply those with -R, and see if either of those makes a difference?

	Dave


[-- Attachment #2: commit-a0cc621 --]
[-- Type: text/plain, Size: 1715 bytes --]

commit a0cc621f52a4dea10c34eeed6eb4e36b26db63dc
Author: Dave Jones <davej@redhat.com>
Date:   Sun Aug 27 01:23:35 2006 -0700

    [PATCH] cpufreq: acpi-cpufreq: Ignore failure from acpi_cpufreq_early_init_acpi
    
    Ignore the return value of early_init_acpi(), as it can give false error
    messages.  If there is something really wrong, then register_driver will
    fail cleanly with EINVAL later.
    
    [ background: modprobe acpi-cpufreq on systems not capable of speed-scaling
      started failing with 'invalid argument', where previously it would only
      ever -ENODEV
    
      I'm not 100% happy with the solution. It'd be better to handle
      failure properly, but this is a low-impact change for 2.6.18
      We can always revisit doing this better in .19   --davej.]
    
    Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Signed-off-by: Dave Jones <davej@redhat.com>
    Cc: Greg KH <greg@kroah.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>

diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
index efb41e8..e6ea00e 100644
--- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -567,16 +567,11 @@ static struct cpufreq_driver acpi_cpufre
 static int __init
 acpi_cpufreq_init (void)
 {
-	int                     result = 0;
-
 	dprintk("acpi_cpufreq_init\n");
 
-	result = acpi_cpufreq_early_init_acpi();
+	acpi_cpufreq_early_init_acpi();
 
-	if (!result)
- 		result = cpufreq_register_driver(&acpi_cpufreq_driver);
-	
-	return (result);
+ 	return cpufreq_register_driver(&acpi_cpufreq_driver);
 }
 
 

[-- Attachment #3: commit-12e704d --]
[-- Type: text/plain, Size: 893 bytes --]

commit 12e704db809cd4101b7d3594fc9a96f30fe88a31
Author: bert hubert <bert.hubert@netherlabs.nl>
Date:   Sun Jul 30 21:19:32 2006 +0200

    [CPUFREQ] Propagate acpi_processor_preregister_performance return value.
    
    Note how any error from acpi_processor_preregister_performance is ignored.
    
    From: bert hubert <bert.hubert@netherlabs.nl>
    Signed-off-by: Dave Jones <davej@redhat.com>

diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
index 567b39b..efb41e8 100644
--- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -384,8 +384,7 @@ static int acpi_cpufreq_early_init_acpi(
 	}
 
 	/* Do initialization in ACPI core */
-	acpi_processor_preregister_performance(acpi_perf_data);
-	return 0;
+	return acpi_processor_preregister_performance(acpi_perf_data);
 }
 
 static int

[-- Attachment #4: Type: text/plain, Size: 0 bytes --]

Re: suspending to disk on FC6 not working

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Dave Jones [mailto:davej@redhat.com] 
>Sent: Friday, September 29, 2006 1:54 PM
>To: Louis Garcia
>Cc: Pallipadi, Venkatesh; Pavel Machek; linux-pm@lists.osdl.org
>Subject: Re: [linux-pm] suspending to disk on FC6 not working
>
>On Wed, Sep 27, 2006 at 02:55:29AM -0400, Louis Garcia wrote:
>
> > >  >  > > > > goes to the 2nd runlevel (ie. without network 
>servers and X).  Then log in
> > >  >  > > > > as root, do "echo 8 > /proc/sys/kernel/printk" and
> > >  >  > > > > "echo disk > /sys/power/state".  The system 
>should suspend to disk and power
> > >  >  > > > > off the machine.  If it doesn't do that (ie. 
>if it returns to the shell
> > >  >  > > > > immediately), please do "dmesg > dmesg.log" 
>and send the dmesg.log file
> > >  >  > > > > to me.
> > >  >  > > > 
> > >  >  > > > The system didn't power off, it returned to the 
>shell. I attached dmesg.
> > >  >  > > 
> > >  >  > > Pavel, it looks like we have a problem with the 
>CPU suspend on this box:
> > >  >  > > 
> > >  >  > > acpi acpi: freeze
> > >  >  > > PM: snapshotting memory.
> > >  >  > > Class driver suspend failed for cpu0
> > >  >  > > Could not power down device &q->lock: error -22
> > >  >  > > Some devices failed to power down, aborting suspend
> > >  >  > > acpi acpi: resuming
> > >  >  > 
> > >  >  > That looks like cpufreq/acpi, no?
> > >  > 
> > >  > Looking at drivers/cpufreq/cpufreq.c:cpufreq_suspend(),
> > >  > There's only two ways we can fail that function. In one way,
> > >  > we'll see a printk, and the other we silently -EINVAL.
> > >  > Given the log doesn't show the printk, we must be 
>failing here..
> > >  > 
> > >  >     cpu_policy = cpufreq_cpu_get(cpu);
> > >  >     if (!cpu_policy)
> > >  >         return -EINVAL;
> > >  > 
> > >  > cpufreq_cpu_get has a number of potential ways it 
>could fail however,
> > >  > and isn't very chatty about failing, so we've no real idea
> > >  > what's falling apart there.
> > > 
> > > This patch might give us some more clues.
> > >  
> > > --- 1/drivers/cpufreq/cpufreq.c	2006-09-24 
>00:26:42.000000000 -0400
> > > +++ 2/drivers/cpufreq/cpufreq.c	2006-09-26 
>22:48:49.000000000 -0400
> > > @@ -63,27 +63,36 @@ struct cpufreq_policy *cpufreq_cpu_get(u
> > >  	struct cpufreq_policy *data;
> > >  	unsigned long flags;
> > >  
> > > -	if (cpu >= NR_CPUS)
> > > +	if (cpu >= NR_CPUS) {
> > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed 
>(!>=NR_CPUS)\n");
> > >  		goto err_out;
> > > +	}
> > >  
> > >  	/* get the cpufreq driver */
> > >  	spin_lock_irqsave(&cpufreq_driver_lock, flags);
> > >  
> > > -	if (!cpufreq_driver)
> > > +	if (!cpufreq_driver) {
> > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!driver)\n");
> > >  		goto err_out_unlock;
> > > +	}
> > >  
> > > -	if (!try_module_get(cpufreq_driver->owner))
> > > +	if (!try_module_get(cpufreq_driver->owner)) {
> > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed 
>(!try_module_get)\n");
> > >  		goto err_out_unlock;
> > > -
> > > +	}
> > >  
> > >  	/* get the CPU */
> > >  	data = cpufreq_cpu_data[cpu];
> > >  
> > > -	if (!data)
> > > +	if (!data) {
> > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed (!data)\n");
> > >  		goto err_out_put_module;
> > > +	}
> > >  
> > > -	if (!kobject_get(&data->kobj))
> > > +	if (!kobject_get(&data->kobj)) {
> > > +		printk(KERN_DEBUG "cpufreq_cpu_get failed 
>(!kobject_get)\n");
> > >  		goto err_out_put_module;
> > > +	}
> > >  
> > >  	spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
> > >  	return data;
> > >
> > ... 
> > PM: snapshotting memory.
> > cpufreq_cpu_get failed (!data)
> > Class driver suspend failed for cpu0
> > Could not power down device &q->lock: error -22
> > Some devices failed to power down, aborting suspend
>
>Ok, I'm not quite sure how we got into this state.  Venkatesh, 
>any ideas ?
>acpi-cpufreq got quite a few changes between .17 and .18, including the
>two large 'P-state coordination' change.
>
>Louis, I'm attaching two smaller changes that went into .18.
>Can you apply those with -R, and see if either of those makes 
>a difference?
>
>	Dave
>

cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init
fails;
Looks like acpi_cpufreq driver init is failing at some point in this
case and the driver is staying loaded after that failure. That in turn
seems similar to one other bug I saw recently.

Louis, Can you check whether cpufreq is really working In you case. Boot
normally and before you try suspending, just see whether
/sys/devices/system/cpu/cpu0/cpufreq exists and if it does, cat
everything in that directory.

Thanks,
Venki 

Re: suspending to disk on FC6 not working

[Pavel Machek]

Hi!

> > > Could not power down device &q->lock: error -22
> > > Some devices failed to power down, aborting suspend
> >
> >Ok, I'm not quite sure how we got into this state.  Venkatesh, 
> >any ideas ?
> >acpi-cpufreq got quite a few changes between .17 and .18, including the
> >two large 'P-state coordination' change.
> >
> >Louis, I'm attaching two smaller changes that went into .18.
> >Can you apply those with -R, and see if either of those makes 
> >a difference?
> 
> cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init
> fails;
> Looks like acpi_cpufreq driver init is failing at some point in this
> case and the driver is staying loaded after that failure. That in turn
> seems similar to one other bug I saw recently.

Uh, if acpi_cpufreq is built-in... you can't unload it when init
fails, so you need to handle that somehow...?

							Pavel
-- 
Thanks for all the (sleeping) penguins.

Re: suspending to disk on FC6 not working

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Pavel Machek [mailto:pavel@ucw.cz] 
>Sent: Friday, September 29, 2006 3:15 PM
>To: Pallipadi, Venkatesh
>Cc: Dave Jones; Louis Garcia; linux-pm@lists.osdl.org
>Subject: Re: [linux-pm] suspending to disk on FC6 not working
>
>Hi!
>
>> > > Could not power down device &q->lock: error -22
>> > > Some devices failed to power down, aborting suspend
>> >
>> >Ok, I'm not quite sure how we got into this state.  Venkatesh, 
>> >any ideas ?
>> >acpi-cpufreq got quite a few changes between .17 and .18, 
>including the
>> >two large 'P-state coordination' change.
>> >
>> >Louis, I'm attaching two smaller changes that went into .18.
>> >Can you apply those with -R, and see if either of those makes 
>> >a difference?
>> 
>> cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init
>> fails;
>> Looks like acpi_cpufreq driver init is failing at some point in this
>> case and the driver is staying loaded after that failure. 
>That in turn
>> seems similar to one other bug I saw recently.
>
>Uh, if acpi_cpufreq is built-in... you can't unload it when init
>fails, so you need to handle that somehow...?
>

Sorry. I meant unregistering with cpufreq. When acpi-cpufreq fails, it
should be unregistered from cpufreq and either cpufreq should look for
some other driver that may work or cpufreq should mark that there is no
driver registered. I am looking at the acpi-cpufreq changes that might
have resulted in this and havent found anything yet...

Thanks,
Venki

Re: suspending to disk on FC6 not working

[Dave Jones]

On Fri, Sep 29, 2006 at 02:35:43PM -0700, Pallipadi, Venkatesh wrote:
 
 > cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init
 > fails;
 > Looks like acpi_cpufreq driver init is failing at some point in this
 > case and the driver is staying loaded after that failure. That in turn
 > seems similar to one other bug I saw recently.

Ah, that was because it was marked CPUFREQ_STICKY in 2.6.18.
That was added to work around another problem : If it was built modular,
a modprobe acpi-cpufreq would be really noisy when it get an -ENODEV

	Dave

Re: suspending to disk on FC6 not working

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Dave Jones [mailto:davej@redhat.com] 
>Sent: Friday, September 29, 2006 3:26 PM
>To: Pallipadi, Venkatesh
>Cc: Louis Garcia; Pavel Machek; linux-pm@lists.osdl.org
>Subject: Re: [linux-pm] suspending to disk on FC6 not working
>
>On Fri, Sep 29, 2006 at 02:35:43PM -0700, Pallipadi, Venkatesh wrote:
> 
> > cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq 
>driver init
> > fails;
> > Looks like acpi_cpufreq driver init is failing at some point in this
> > case and the driver is staying loaded after that failure. 
>That in turn
> > seems similar to one other bug I saw recently.
>
>Ah, that was because it was marked CPUFREQ_STICKY in 2.6.18.
>That was added to work around another problem : If it was 
>built modular,
>a modprobe acpi-cpufreq would be really noisy when it get an -ENODEV
>

That's it.. This issue seems to be a side effect of that patch...

Louis: After normal boot of 2.6.18, if you are not seeing the directory
/sys/devices/system/cpu/cpu0/cpufreq

Then try reverting this patch
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3

and then check whether the suspend resume issue goes away. 

Thanks,
Venki

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
>  
> >-----Original Message-----
> >From: Dave Jones [mailto:davej@redhat.com] 
> >Sent: Friday, September 29, 2006 3:26 PM
> >To: Pallipadi, Venkatesh
> >Cc: Louis Garcia; Pavel Machek; linux-pm@lists.osdl.org
> >Subject: Re: [linux-pm] suspending to disk on FC6 not working
> >
> >On Fri, Sep 29, 2006 at 02:35:43PM -0700, Pallipadi, Venkatesh wrote:
> > 
> > > cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq 
> >driver init
> > > fails;
> > > Looks like acpi_cpufreq driver init is failing at some point in this
> > > case and the driver is staying loaded after that failure. 
> >That in turn
> > > seems similar to one other bug I saw recently.
> >
> >Ah, that was because it was marked CPUFREQ_STICKY in 2.6.18.
> >That was added to work around another problem : If it was 
> >built modular,
> >a modprobe acpi-cpufreq would be really noisy when it get an -ENODEV
> >
> 
> That's it.. This issue seems to be a side effect of that patch...
> 
> Louis: After normal boot of 2.6.18, if you are not seeing the directory
> /sys/devices/system/cpu/cpu0/cpufreq
> 
> Then try reverting this patch
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
> ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
> 
> and then check whether the suspend resume issue goes away. 
> 
> Thanks,
> Venki

I reverted this patch and my suspend issue is gone. Though the
directory /sys/devices/system/cpu/cpu0/cpufreq is non existent, with or
without this patch.

-Louis

Re: suspending to disk on FC6 not working

[Dave Jones]

On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
 > On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
 > > That's it.. This issue seems to be a side effect of that patch...
 > > 
 > > Louis: After normal boot of 2.6.18, if you are not seeing the directory
 > > /sys/devices/system/cpu/cpu0/cpufreq
 > > 
 > > Then try reverting this patch
 > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
 > > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
 > > 
 > > and then check whether the suspend resume issue goes away. 
 > > 
 > > Thanks,
 > > Venki
 > 
 > I reverted this patch and my suspend issue is gone. Though the
 > directory /sys/devices/system/cpu/cpu0/cpufreq is non existent, with or
 > without this patch.

Ok, I've backed that out in cpufreq.git, it'll go along to Linus soon.
If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
does it fail silently ? Or does it revert us back to the behaviour
where it's noisy again?

	Dave

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Sat, 2006-09-30 at 23:21 -0400, Dave Jones wrote:
> On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
>  > On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
>  > > That's it.. This issue seems to be a side effect of that patch...
>  > > 
>  > > Louis: After normal boot of 2.6.18, if you are not seeing the directory
>  > > /sys/devices/system/cpu/cpu0/cpufreq
>  > > 
>  > > Then try reverting this patch
>  > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
>  > > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
>  > > 
>  > > and then check whether the suspend resume issue goes away. 
>  > > 
>  > > Thanks,
>  > > Venki
>  > 
>  > I reverted this patch and my suspend issue is gone. Though the
>  > directory /sys/devices/system/cpu/cpu0/cpufreq is non existent, with or
>  > without this patch.
> 
> Ok, I've backed that out in cpufreq.git, it'll go along to Linus soon.
> If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
> does it fail silently ? Or does it revert us back to the behaviour
> where it's noisy again?
> 
> 	Dave

I had not noticed it was not loaded. This maybe a bigger problem. With
the latest FC6 kernel this module gets loaded and thus suspend fails. I
rebuilt the same kernel but plopped this patch in. The module does not
want to load:

# /sbin/modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device

This is why suspend works. But now this module won't load.

-Louis

Re: suspending to disk on FC6 not working

[Dave Jones]

On Sun, Oct 01, 2006 at 01:00:00AM -0400, Louis Garcia wrote:
 > On Sat, 2006-09-30 at 23:21 -0400, Dave Jones wrote:
 > > On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
 > >  > On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
 > >  > > That's it.. This issue seems to be a side effect of that patch...
 > >  > > 
 > >  > > Louis: After normal boot of 2.6.18, if you are not seeing the directory
 > >  > > /sys/devices/system/cpu/cpu0/cpufreq
 > >  > > 
 > >  > > Then try reverting this patch
 > >  > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
 > >  > > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
 > >  > > 
 > >  > > and then check whether the suspend resume issue goes away. 
 > >  > 
 > >  > I reverted this patch and my suspend issue is gone. Though the
 > >  > directory /sys/devices/system/cpu/cpu0/cpufreq is non existent, with or
 > >  > without this patch.
 > > 
 > > Ok, I've backed that out in cpufreq.git, it'll go along to Linus soon.
 > > If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
 > > does it fail silently ? Or does it revert us back to the behaviour
 > > where it's noisy again?
 > > 
 > > 	Dave
 > 
 > I had not noticed it was not loaded. This maybe a bigger problem. With
 > the latest FC6 kernel this module gets loaded and thus suspend fails. I
 > rebuilt the same kernel but plopped this patch in. The module does not
 > want to load:
 > 
 > # /sbin/modprobe acpi-cpufreq
 > FATAL: Error inserting acpi_cpufreq
 > (/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
 > 
 > This is why suspend works. But now this module won't load.

Right, what the STICKY patch that you reverted does is it silences the
failure, by not unloading the module when it fails to init.

What we want is the best of both worlds: Silence when its loaded and
init fails, and no module around.  Hmm.

	Dave

Re: suspending to disk on FC6 not working

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Louis Garcia [mailto:louisg00@bellsouth.net] 
>Sent: Saturday, September 30, 2006 10:00 PM
>To: Dave Jones
>Cc: Pallipadi, Venkatesh; Pavel Machek; linux-pm@lists.osdl.org
>Subject: Re: [linux-pm] suspending to disk on FC6 not working
>
>On Sat, 2006-09-30 at 23:21 -0400, Dave Jones wrote:
>> On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
>>  > On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
>>  > > That's it.. This issue seems to be a side effect of 
>that patch...
>>  > > 
>>  > > Louis: After normal boot of 2.6.18, if you are not 
>seeing the directory
>>  > > /sys/devices/system/cpu/cpu0/cpufreq
>>  > > 
>>  > > Then try reverting this patch
>>  > > 
>http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.
>6.git;a=c
>>  > > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
>>  > > 
>>  > > and then check whether the suspend resume issue goes away. 
>>  > > 
>>  > > Thanks,
>>  > > Venki
>>  > 
>>  > I reverted this patch and my suspend issue is gone. Though the
>>  > directory /sys/devices/system/cpu/cpu0/cpufreq is non 
>existent, with or
>>  > without this patch.
>> 
>> Ok, I've backed that out in cpufreq.git, it'll go along to 
>Linus soon.
>> If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
>> does it fail silently ? Or does it revert us back to the behaviour
>> where it's noisy again?
>> 
>> 	Dave
>
>I had not noticed it was not loaded. This maybe a bigger problem. With
>the latest FC6 kernel this module gets loaded and thus suspend fails. I
>rebuilt the same kernel but plopped this patch in. The module does not
>want to load:
>
># /sbin/modprobe acpi-cpufreq
>FATAL: Error inserting acpi_cpufreq
>(/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu
>/cpufreq/acpi-cpufreq.ko): No such device
>
>This is why suspend works. But now this module won't load.
>

The module was not working on your laptop even when suspend was failing.
That is what the absence of /sys.../cpufreq says. If this module was
working for you earlier and stopped working recently or even otherwise
both this and speedstep-centrino does not work on your platform, that is
a separate issue. Was this module working and cpufreq supported on your
system with any earlier kernels?

Thanks,
Venki

Re: suspending to disk on FC6 not working

[Dave Jones]

On Sat, Sep 30, 2006 at 10:07:16PM -0700, Pallipadi, Venkatesh wrote:

 > >I had not noticed it was not loaded. This maybe a bigger problem. With
 > >the latest FC6 kernel this module gets loaded and thus suspend fails. I
 > >rebuilt the same kernel but plopped this patch in. The module does not
 > >want to load:
 > >
 > ># /sbin/modprobe acpi-cpufreq
 > >FATAL: Error inserting acpi_cpufreq
 > >(/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu
 > >/cpufreq/acpi-cpufreq.ko): No such device
 > >
 > >This is why suspend works. But now this module won't load.
 > >
 > 
 > The module was not working on your laptop even when suspend was failing.
 > That is what the absence of /sys.../cpufreq says. If this module was
 > working for you earlier and stopped working recently or even otherwise
 > both this and speedstep-centrino does not work on your platform, that is
 > a separate issue. Was this module working and cpufreq supported on your
 > system with any earlier kernels?

One problem acpi-cpufreq faces when built modular compared to the
other cpufreq drivers is that there's no way of knowing before modprobe'ing
whether or not it's going to do anything or not, so userspace never knows
if it's really 'safe' to load this module.

In Fedora, we modprobe the acpi-cpufreq module if all other scaling
drivers have failed their init routines. Ie, it's treated as a fallback
"Well, nothing else worked, lets try this, and if this don't work out, bail..."
When we added this userspace 'fallback', we started getting a bunch of
reports like the above, from users who had CPUs that couldn't do any scaling
at all. The STICKY tag was added to the driver so that it would stop
making noise for those users.

Looking at the problem differently, we *could* add back the sticky tag,
and add some explicit checks for !data in the suspend/resume paths
to abort cleanly. It's a bit of a hack though.

hmm?

	Dave

Re: suspending to disk on FC6 not working

[Louis Garcia]

On Sat, 2006-09-30 at 22:07 -0700, Pallipadi, Venkatesh wrote:
>  
> >-----Original Message-----
> >From: Louis Garcia [mailto:louisg00@bellsouth.net] 
> >Sent: Saturday, September 30, 2006 10:00 PM
> >To: Dave Jones
> >Cc: Pallipadi, Venkatesh; Pavel Machek; linux-pm@lists.osdl.org
> >Subject: Re: [linux-pm] suspending to disk on FC6 not working
> >
> >On Sat, 2006-09-30 at 23:21 -0400, Dave Jones wrote:
> >> On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
> >>  > On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
> >>  > > That's it.. This issue seems to be a side effect of 
> >that patch...
> >>  > > 
> >>  > > Louis: After normal boot of 2.6.18, if you are not 
> >seeing the directory
> >>  > > /sys/devices/system/cpu/cpu0/cpufreq
> >>  > > 
> >>  > > Then try reverting this patch
> >>  > > 
> >http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.
> >6.git;a=c
> >>  > > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
> >>  > > 
> >>  > > and then check whether the suspend resume issue goes away. 
> >>  > > 
> >>  > > Thanks,
> >>  > > Venki
> >>  > 
> >>  > I reverted this patch and my suspend issue is gone. Though the
> >>  > directory /sys/devices/system/cpu/cpu0/cpufreq is non 
> >existent, with or
> >>  > without this patch.
> >> 
> >> Ok, I've backed that out in cpufreq.git, it'll go along to 
> >Linus soon.
> >> If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
> >> does it fail silently ? Or does it revert us back to the behaviour
> >> where it's noisy again?
> >> 
> >> 	Dave
> >
> >I had not noticed it was not loaded. This maybe a bigger problem. With
> >the latest FC6 kernel this module gets loaded and thus suspend fails. I
> >rebuilt the same kernel but plopped this patch in. The module does not
> >want to load:
> >
> ># /sbin/modprobe acpi-cpufreq
> >FATAL: Error inserting acpi_cpufreq
> >(/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu
> >/cpufreq/acpi-cpufreq.ko): No such device
> >
> >This is why suspend works. But now this module won't load.
> >
> 
> The module was not working on your laptop even when suspend was failing.
> That is what the absence of /sys.../cpufreq says. If this module was
> working for you earlier and stopped working recently or even otherwise
> both this and speedstep-centrino does not work on your platform, that is
> a separate issue. Was this module working and cpufreq supported on your
> system with any earlier kernels?
> 
> Thanks,
> Venki

I have no clue. All I noticed is suspend stopped working. I'm on a P4
desktop, I don't use or need cpufreq.

On the kernels that fail to suspend. This module is apparently loaded
because rmmod acpi-cpufreq succeeds and I can suspend to my harts
content.

-Louis

Re: suspending to disk on FC6 not working

[Pavel Machek]

Hi!

>  > I had not noticed it was not loaded. This maybe a bigger problem. With
>  > the latest FC6 kernel this module gets loaded and thus suspend fails. I
>  > rebuilt the same kernel but plopped this patch in. The module does not
>  > want to load:
>  > 
>  > # /sbin/modprobe acpi-cpufreq
>  > FATAL: Error inserting acpi_cpufreq
>  > (/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
>  > 
>  > This is why suspend works. But now this module won't load.
> 
> Right, what the STICKY patch that you reverted does is it silences the
> failure, by not unloading the module when it fails to init.
> 
> What we want is the best of both worlds: Silence when its loaded and
> init fails, and no module around.  Hmm.

? Using more kernel memory when hardware can't do acpi_cpufreq just to
get a rid of message... seems like very bad tradeoff. ACPI tables are
not hotpluggable, so it _should_ be impossible to load that module...

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Rafael J. Wysocki]

On Sunday, 1 October 2006 07:22, Dave Jones wrote:
> On Sat, Sep 30, 2006 at 10:07:16PM -0700, Pallipadi, Venkatesh wrote:
> 
>  > >I had not noticed it was not loaded. This maybe a bigger problem. With
>  > >the latest FC6 kernel this module gets loaded and thus suspend fails. I
>  > >rebuilt the same kernel but plopped this patch in. The module does not
>  > >want to load:
>  > >
>  > ># /sbin/modprobe acpi-cpufreq
>  > >FATAL: Error inserting acpi_cpufreq
>  > >(/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu
>  > >/cpufreq/acpi-cpufreq.ko): No such device
>  > >
>  > >This is why suspend works. But now this module won't load.
>  > >
>  > 
>  > The module was not working on your laptop even when suspend was failing.
>  > That is what the absence of /sys.../cpufreq says. If this module was
>  > working for you earlier and stopped working recently or even otherwise
>  > both this and speedstep-centrino does not work on your platform, that is
>  > a separate issue. Was this module working and cpufreq supported on your
>  > system with any earlier kernels?
> 
> One problem acpi-cpufreq faces when built modular compared to the
> other cpufreq drivers is that there's no way of knowing before modprobe'ing
> whether or not it's going to do anything or not, so userspace never knows
> if it's really 'safe' to load this module.
> 
> In Fedora, we modprobe the acpi-cpufreq module if all other scaling
> drivers have failed their init routines. Ie, it's treated as a fallback
> "Well, nothing else worked, lets try this, and if this don't work out, bail..."
> When we added this userspace 'fallback', we started getting a bunch of
> reports like the above, from users who had CPUs that couldn't do any scaling
> at all. The STICKY tag was added to the driver so that it would stop
> making noise for those users.
> 
> Looking at the problem differently, we *could* add back the sticky tag,
> and add some explicit checks for !data in the suspend/resume paths
> to abort cleanly. It's a bit of a hack though.
> 
> hmm?

Well, IMHO, making the module load when we know it won't work is a hack
in the first place. :-)

If you want the sticky tag, the suspend/resume thing should be added too.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

Re: suspending to disk on FC6 not working

[Dave Jones]

On Sun, Oct 01, 2006 at 02:28:19PM +0200, Rafael J. Wysocki wrote:

 > Well, IMHO, making the module load when we know it won't work is a hack
 > in the first place. :-)

That's just it, we *don't* know if it'll work or not until we load it.

	Dave

Re: suspending to disk on FC6 not working

[Pavel Machek]

On Sun 2006-10-01 14:36:07, Dave Jones wrote:
> On Sun, Oct 01, 2006 at 02:28:19PM +0200, Rafael J. Wysocki wrote:
> 
>  > Well, IMHO, making the module load when we know it won't work is a hack
>  > in the first place. :-)
> 
> That's just it, we *don't* know if it'll work or not until we load it.

Okay... but keeping it loaded (when it is unused) to silence some
warnings is stupid / hack. Can we teach userland to ignore the fact
that module failed to load, for example?
							Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: suspending to disk on FC6 not working

[Dave Jones]

On Sun, Oct 01, 2006 at 08:38:52PM +0200, Pavel Machek wrote:
 > On Sun 2006-10-01 14:36:07, Dave Jones wrote:
 > > On Sun, Oct 01, 2006 at 02:28:19PM +0200, Rafael J. Wysocki wrote:
 > > 
 > >  > Well, IMHO, making the module load when we know it won't work is a hack
 > >  > in the first place. :-)
 > > 
 > > That's just it, we *don't* know if it'll work or not until we load it.
 > 
 > Okay... but keeping it loaded (when it is unused) to silence some
 > warnings is stupid / hack. Can we teach userland to ignore the fact
 > that module failed to load, for example?

Sounds like a good idea.

	Dave