* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) [not found] <20070925065109.GA3080@localhost.localdomain> @ 2007-09-25 7:33 ` Andrew Morton 2007-09-25 8:36 ` Alexey Starikovskiy 2007-09-25 15:40 ` Linus Torvalds 0 siblings, 2 replies; 32+ messages in thread From: Andrew Morton @ 2007-09-25 7:33 UTC (permalink / raw) To: Damien Wyart Cc: LKML, Len Brown, Frans Pop, Alexey Starikovskiy, Rafael J. Wysocki, linux-acpi On Tue, 25 Sep 2007 08:51:09 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > Hello, > > After testing rc8, I noticed that I couldn't power off the computer > directly, it only got halted and I had to press the power button > manually. Just before displaying "System halted", the following message > is displayed: > > ACPI : PCI interrupt for device 0000:02:08.0 disabled > > I had to first revert 5a50fe709d527f31169263e36601dd83446d5744 then > f216cc3748a3a22c2b99390fddcdafa0583791a2 (handling of Sx states) to > recover previous behaviour. Let's add some cc's. > Attached are the dmesg for rc7, rc8 and rc8 with the two patches > reverted. "diff -u dmesg.rc8_revert dmesg.rc8" says: --- dmesg.rc8_revert 2007-09-25 00:31:33.000000000 -0700 +++ dmesg.rc8 2007-09-25 00:31:30.000000000 -0700 @@ -1,4 +1,4 @@ -Linux version 2.6.23-rc8-25092007dw (root@brouette) (gcc version 4.2.1 (Debian 4.2.1-5)) #2 SMP Tue Sep 25 08:31:09 CEST 2007 +Linux version 2.6.23-rc8-25092007dw (root@brouette) (gcc version 4.2.1 (Debian 4.2.1-5)) #1 SMP Tue Sep 25 07:27:10 CEST 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) @@ -72,18 +72,18 @@ console [tty0] enabled Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 2074780k/2096592k available (2175k kernel code, 20712k reserved, 815k data, 192k init, 1179088k highmem) +Memory: 2074780k/2096592k available (2175k kernel code, 20712k reserved, 816k data, 192k init, 1179088k highmem) virtual kernel memory layout: fixmap : 0xfff9b000 - 0xfffff000 ( 400 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) .init : 0xc03f0000 - 0xc0420000 ( 192 kB) - .data : 0xc031fd5c - 0xc03ebd04 ( 815 kB) - .text : 0xc0100000 - 0xc031fd5c (2175 kB) + .data : 0xc031fcd4 - 0xc03ebd04 ( 816 kB) + .text : 0xc0100000 - 0xc031fcd4 (2175 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1 -Calibrating delay using timer specific routine.. 5987.66 BogoMIPS (lpj=2993833) +Calibrating delay using timer specific routine.. 5987.60 BogoMIPS (lpj=2993802) Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000041d 00000000 00000000 00000000 monitor/mwait feature present. @@ -104,7 +104,7 @@ Booting processor 1/1 eip 2000 CPU 1 irqstacks, hard=c0426000 soft=c0424000 Initializing CPU#1 -Calibrating delay using timer specific routine.. 5984.18 BogoMIPS (lpj=2992093) +Calibrating delay using timer specific routine.. 5984.16 BogoMIPS (lpj=2992084) CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000041d 00000000 00000000 00000000 monitor/mwait feature present. CPU: Trace cache: 12K uops, L1 D cache: 16K @@ -116,7 +116,7 @@ CPU1: Intel P4/Xeon Extended MCE MSRs (12) available CPU1: Thermal monitoring enabled CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03 -Total of 2 processors activated (11971.85 BogoMIPS). +Total of 2 processors activated (11971.77 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 checking TSC synchronization [CPU#0 -> CPU#1]: passed. @@ -279,6 +279,7 @@ EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 192k freed +input: PC Speaker as /devices/platform/pcspkr/input/input4 sr0: scsi3-mmc drive: 1x/48x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 @@ -287,7 +288,6 @@ usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb -input: PC Speaker as /devices/platform/pcspkr/input/input4 parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,ECP] USB Universal Host Controller Interface driver v3.0 @@ -299,46 +299,42 @@ usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected -ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20 -PCI: Setting latency timer of device 0000:00:1d.1 to 64 -uhci_hcd 0000:00:1d.1: UHCI Host Controller -uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 -uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60 +ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 20 +PCI: Setting latency timer of device 0000:00:1d.7 to 64 +ehci_hcd 0000:00:1d.7: EHCI Host Controller +ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 +ehci_hcd 0000:00:1d.7: debug port 1 +PCI: cache line size of 128 is not supported by device 0000:00:1d.7 +ehci_hcd 0000:00:1d.7: irq 20, io mem 0xffa80800 +ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found -hub 2-0:1.0: 2 ports detected +hub 2-0:1.0: 8 ports detected +ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 21 +PCI: Setting latency timer of device 0000:00:1d.1 to 64 +uhci_hcd 0000:00:1d.1: UHCI Host Controller +uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 +uhci_hcd 0000:00:1d.1: irq 21, io base 0x0000ff60 +usb usb3: configuration #1 chosen from 1 choice +hub 3-0:1.0: USB hub found +hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17 PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller -uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 +uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000ff40 -usb usb3: configuration #1 chosen from 1 choice -hub 3-0:1.0: USB hub found -hub 3-0:1.0: 2 ports detected -usb 1-1: new full speed USB device using uhci_hcd and address 2 +usb usb4: configuration #1 chosen from 1 choice +hub 4-0:1.0: USB hub found +hub 4-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:00:1d.3 to 64 uhci_hcd 0000:00:1d.3: UHCI Host Controller -uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 +uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1d.3: irq 19, io base 0x0000ff20 -usb usb4: configuration #1 chosen from 1 choice -hub 4-0:1.0: USB hub found -hub 4-0:1.0: 2 ports detected -ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 21 -PCI: Setting latency timer of device 0000:00:1d.7 to 64 -ehci_hcd 0000:00:1d.7: EHCI Host Controller -ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5 -ehci_hcd 0000:00:1d.7: debug port 1 -PCI: cache line size of 128 is not supported by device 0000:00:1d.7 -ehci_hcd 0000:00:1d.7: irq 21, io mem 0xffa80800 -ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 -usb 1-1: configuration #1 chosen from 1 choice -usb 1-1: can't set config #1, error -71 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found -hub 5-0:1.0: 8 ports detected -usb 1-1: USB disconnect, address 2 -usb 1-1: new full speed USB device using uhci_hcd and address 3 +hub 5-0:1.0: 2 ports detected +usb 1-1: new full speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice Adding 1212896k swap on /dev/sdb7. Priority:-1 extents:1 across:1212896k EXT3 FS on sdb2, internal journal ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 7:33 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Andrew Morton @ 2007-09-25 8:36 ` Alexey Starikovskiy 2007-09-25 9:08 ` Torsten Kaiser 2007-09-25 15:40 ` Linus Torvalds 1 sibling, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 8:36 UTC (permalink / raw) To: Damien Wyart Cc: Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi Do you have CONFIG_ACPI_SLEEP enabled in your .config? Andrew Morton wrote: > On Tue, 25 Sep 2007 08:51:09 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > >> Hello, >> >> After testing rc8, I noticed that I couldn't power off the computer >> directly, it only got halted and I had to press the power button >> manually. Just before displaying "System halted", the following message >> is displayed: >> >> ACPI : PCI interrupt for device 0000:02:08.0 disabled >> >> I had to first revert 5a50fe709d527f31169263e36601dd83446d5744 then >> f216cc3748a3a22c2b99390fddcdafa0583791a2 (handling of Sx states) to >> recover previous behaviour. > > Let's add some cc's. > >> Attached are the dmesg for rc7, rc8 and rc8 with the two patches >> reverted. > > "diff -u dmesg.rc8_revert dmesg.rc8" says: > > --- dmesg.rc8_revert 2007-09-25 00:31:33.000000000 -0700 > +++ dmesg.rc8 2007-09-25 00:31:30.000000000 -0700 > @@ -1,4 +1,4 @@ > -Linux version 2.6.23-rc8-25092007dw (root@brouette) (gcc version 4.2.1 (Debian 4.2.1-5)) #2 SMP Tue Sep 25 08:31:09 CEST 2007 > +Linux version 2.6.23-rc8-25092007dw (root@brouette) (gcc version 4.2.1 (Debian 4.2.1-5)) #1 SMP Tue Sep 25 07:27:10 CEST 2007 > BIOS-provided physical RAM map: > BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) > BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > @@ -72,18 +72,18 @@ > console [tty0] enabled > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > -Memory: 2074780k/2096592k available (2175k kernel code, 20712k reserved, 815k data, 192k init, 1179088k highmem) > +Memory: 2074780k/2096592k available (2175k kernel code, 20712k reserved, 816k data, 192k init, 1179088k highmem) > virtual kernel memory layout: > fixmap : 0xfff9b000 - 0xfffff000 ( 400 kB) > pkmap : 0xff800000 - 0xffc00000 (4096 kB) > vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) > lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) > .init : 0xc03f0000 - 0xc0420000 ( 192 kB) > - .data : 0xc031fd5c - 0xc03ebd04 ( 815 kB) > - .text : 0xc0100000 - 0xc031fd5c (2175 kB) > + .data : 0xc031fcd4 - 0xc03ebd04 ( 816 kB) > + .text : 0xc0100000 - 0xc031fcd4 (2175 kB) > Checking if this processor honours the WP bit even in supervisor mode... Ok. > SLUB: Genslabs=22, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1 > -Calibrating delay using timer specific routine.. 5987.66 BogoMIPS (lpj=2993833) > +Calibrating delay using timer specific routine.. 5987.60 BogoMIPS (lpj=2993802) > Mount-cache hash table entries: 512 > CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000041d 00000000 00000000 00000000 > monitor/mwait feature present. > @@ -104,7 +104,7 @@ > Booting processor 1/1 eip 2000 > CPU 1 irqstacks, hard=c0426000 soft=c0424000 > Initializing CPU#1 > -Calibrating delay using timer specific routine.. 5984.18 BogoMIPS (lpj=2992093) > +Calibrating delay using timer specific routine.. 5984.16 BogoMIPS (lpj=2992084) > CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000041d 00000000 00000000 00000000 > monitor/mwait feature present. > CPU: Trace cache: 12K uops, L1 D cache: 16K > @@ -116,7 +116,7 @@ > CPU1: Intel P4/Xeon Extended MCE MSRs (12) available > CPU1: Thermal monitoring enabled > CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03 > -Total of 2 processors activated (11971.85 BogoMIPS). > +Total of 2 processors activated (11971.77 BogoMIPS). > ENABLING IO-APIC IRQs > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 > checking TSC synchronization [CPU#0 -> CPU#1]: passed. > @@ -279,6 +279,7 @@ > EXT3-fs: mounted filesystem with ordered data mode. > VFS: Mounted root (ext3 filesystem) readonly. > Freeing unused kernel memory: 192k freed > +input: PC Speaker as /devices/platform/pcspkr/input/input4 > sr0: scsi3-mmc drive: 1x/48x cd/rw xa/form2 cdda tray > Uniform CD-ROM driver Revision: 3.20 > sr 1:0:0:0: Attached scsi CD-ROM sr0 > @@ -287,7 +288,6 @@ > usbcore: registered new interface driver usbfs > usbcore: registered new interface driver hub > usbcore: registered new device driver usb > -input: PC Speaker as /devices/platform/pcspkr/input/input4 > parport_pc 00:0a: reported by Plug and Play ACPI > parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,ECP] > USB Universal Host Controller Interface driver v3.0 > @@ -299,46 +299,42 @@ > usb usb1: configuration #1 chosen from 1 choice > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 2 ports detected > -ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20 > -PCI: Setting latency timer of device 0000:00:1d.1 to 64 > -uhci_hcd 0000:00:1d.1: UHCI Host Controller > -uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 > -uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ff60 > +ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 20 > +PCI: Setting latency timer of device 0000:00:1d.7 to 64 > +ehci_hcd 0000:00:1d.7: EHCI Host Controller > +ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 > +ehci_hcd 0000:00:1d.7: debug port 1 > +PCI: cache line size of 128 is not supported by device 0000:00:1d.7 > +ehci_hcd 0000:00:1d.7: irq 20, io mem 0xffa80800 > +ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > usb usb2: configuration #1 chosen from 1 choice > hub 2-0:1.0: USB hub found > -hub 2-0:1.0: 2 ports detected > +hub 2-0:1.0: 8 ports detected > +ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 21 > +PCI: Setting latency timer of device 0000:00:1d.1 to 64 > +uhci_hcd 0000:00:1d.1: UHCI Host Controller > +uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 > +uhci_hcd 0000:00:1d.1: irq 21, io base 0x0000ff60 > +usb usb3: configuration #1 chosen from 1 choice > +hub 3-0:1.0: USB hub found > +hub 3-0:1.0: 2 ports detected > ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:00:1d.2 to 64 > uhci_hcd 0000:00:1d.2: UHCI Host Controller > -uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3 > +uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 > uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000ff40 > -usb usb3: configuration #1 chosen from 1 choice > -hub 3-0:1.0: USB hub found > -hub 3-0:1.0: 2 ports detected > -usb 1-1: new full speed USB device using uhci_hcd and address 2 > +usb usb4: configuration #1 chosen from 1 choice > +hub 4-0:1.0: USB hub found > +hub 4-0:1.0: 2 ports detected > ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 19 > PCI: Setting latency timer of device 0000:00:1d.3 to 64 > uhci_hcd 0000:00:1d.3: UHCI Host Controller > -uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4 > +uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 > uhci_hcd 0000:00:1d.3: irq 19, io base 0x0000ff20 > -usb usb4: configuration #1 chosen from 1 choice > -hub 4-0:1.0: USB hub found > -hub 4-0:1.0: 2 ports detected > -ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 21 > -PCI: Setting latency timer of device 0000:00:1d.7 to 64 > -ehci_hcd 0000:00:1d.7: EHCI Host Controller > -ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5 > -ehci_hcd 0000:00:1d.7: debug port 1 > -PCI: cache line size of 128 is not supported by device 0000:00:1d.7 > -ehci_hcd 0000:00:1d.7: irq 21, io mem 0xffa80800 > -ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > -usb 1-1: configuration #1 chosen from 1 choice > -usb 1-1: can't set config #1, error -71 > usb usb5: configuration #1 chosen from 1 choice > hub 5-0:1.0: USB hub found > -hub 5-0:1.0: 8 ports detected > -usb 1-1: USB disconnect, address 2 > -usb 1-1: new full speed USB device using uhci_hcd and address 3 > +hub 5-0:1.0: 2 ports detected > +usb 1-1: new full speed USB device using uhci_hcd and address 2 > usb 1-1: configuration #1 chosen from 1 choice > Adding 1212896k swap on /dev/sdb7. Priority:-1 extents:1 across:1212896k > EXT3 FS on sdb2, internal journal > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 8:36 ` Alexey Starikovskiy @ 2007-09-25 9:08 ` Torsten Kaiser 2007-09-25 9:27 ` Damien Wyart 2007-09-25 11:25 ` Alexey Starikovskiy 0 siblings, 2 replies; 32+ messages in thread From: Torsten Kaiser @ 2007-09-25 9:08 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Damien Wyart, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi [-- Attachment #1: Type: text/plain, Size: 423 bytes --] On 9/25/07, Alexey Starikovskiy <astarikovskiy@suse.de> wrote: > Do you have CONFIG_ACPI_SLEEP enabled in your .config? I'm answering that too, because I suspect that my "2.6.23-rc7-mm1 does not power off"-error might have the same cause. No, I do not have CONFIG_ACPI_SLEEP set, because I do not have CONFIG_PM_SLEEP set, because I do not want SUSPEND and/or HIBERNATION. .config from 2.6.23-rc7-mm1 attached. Torsten [-- Attachment #2: config.txt --] [-- Type: text/plain, Size: 48358 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc7-mm1 # Mon Sep 24 19:59:05 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=18 # CONFIG_CGROUPS is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_PROC_KPAGEMAP=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_IO_TRACE=y CONFIG_BLK_DEV_BSG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y CONFIG_NUMA=y # CONFIG_K8_NUMA is not set CONFIG_NODES_SHIFT=6 CONFIG_X86_64_ACPI_NUMA=y # CONFIG_NUMA_EMU is not set CONFIG_ARCH_DISCONTIGMEM_ENABLE=y CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set # CONFIG_DISCONTIGMEM_MANUAL is not set CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y # CONFIG_MEMORY_HOTPLUG is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MIGRATION=y CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y CONFIG_NR_CPUS=4 CONFIG_PHYSICAL_ALIGN=0x200000 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_START=0x200000 # CONFIG_SECCOMP is not set # CONFIG_CC_STACKPROTECTOR is not set CONFIG_HZ_100=y # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=100 CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y # CONFIG_PM_LEGACY is not set # CONFIG_PM_DEBUG is not set CONFIG_SUSPEND_SMP_POSSIBLE=y # CONFIG_SUSPEND is not set CONFIG_HIBERNATION_SMP_POSSIBLE=y # CONFIG_HIBERNATION is not set CONFIG_ACPI=y # CONFIG_ACPI_PROCFS is not set # CONFIG_ACPI_PROC_EVENT is not set # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y CONFIG_ACPI_FAN=y # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y # CONFIG_ACPI_SBS is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set CONFIG_X86_ACPI_CPUFREQ=y # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCI_DOMAINS is not set # CONFIG_DMAR is not set CONFIG_PCIEPORTBUS=y CONFIG_PCIEAER=y CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y # CONFIG_PCI_DEBUG is not set CONFIG_HT_IRQ=y # CONFIG_PCCARD is not set # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=y CONFIG_XFRM_SUB_POLICY=y # CONFIG_XFRM_MIGRATE is not set CONFIG_NET_KEY=y # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m CONFIG_NET_IPGRE_BROADCAST=y # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set CONFIG_INET_AH=y CONFIG_INET_ESP=y CONFIG_INET_IPCOMP=y CONFIG_INET_XFRM_TUNNEL=y CONFIG_INET_TUNNEL=y CONFIG_INET_XFRM_MODE_TRANSPORT=y CONFIG_INET_XFRM_MODE_TUNNEL=y CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=m CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=m CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m # CONFIG_DEFAULT_BIC is not set # CONFIG_DEFAULT_CUBIC is not set # CONFIG_DEFAULT_HTCP is not set # CONFIG_DEFAULT_VEGAS is not set # CONFIG_DEFAULT_WESTWOOD is not set CONFIG_DEFAULT_RENO=y CONFIG_DEFAULT_TCP_CONG="reno" CONFIG_TCP_MD5SIG=y # CONFIG_IP_VS is not set CONFIG_IPV6=m # CONFIG_IPV6_PRIVACY is not set # CONFIG_IPV6_ROUTER_PREF is not set CONFIG_IPV6_OPTIMISTIC_DAD=y CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m # CONFIG_IPV6_MIP6 is not set CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_SIT=m CONFIG_IPV6_TUNNEL=m # CONFIG_IPV6_MULTIPLE_TABLES is not set CONFIG_NETLABEL=y # CONFIG_NETWORK_SECMARK is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK_ENABLED=m CONFIG_NF_CONNTRACK=m CONFIG_NF_CT_ACCT=y CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NETFILTER_XTABLES=m CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m # CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set # CONFIG_NETFILTER_XT_TARGET_DSCP is not set CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m # CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m # # IP: Netfilter Configuration # CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NF_CONNTRACK_PROC_COMPAT=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_IPRANGE=m CONFIG_IP_NF_MATCH_TOS=m CONFIG_IP_NF_MATCH_RECENT=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_OWNER=m CONFIG_IP_NF_MATCH_ADDRTYPE=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_SAME=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_TOS=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration (EXPERIMENTAL) # CONFIG_NF_CONNTRACK_IPV6=m # CONFIG_IP6_NF_QUEUE is not set CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_OWNER=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_RAW=m # CONFIG_IP_DCCP is not set CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_HMAC_NONE is not set CONFIG_SCTP_HMAC_SHA1=y # CONFIG_SCTP_HMAC_MD5 is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set CONFIG_NET_SCH_FIFO=y CONFIG_NET_CLS_ROUTE=y # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set # # Wireless # CONFIG_CFG80211=m CONFIG_NL80211=y CONFIG_WIRELESS_EXT=y CONFIG_MAC80211=m CONFIG_MAC80211_LEDS=y # CONFIG_MAC80211_DEBUGFS is not set # CONFIG_MAC80211_DEBUG is not set CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set CONFIG_IEEE80211_CRYPT_WEP=m CONFIG_IEEE80211_CRYPT_CCMP=m CONFIG_IEEE80211_CRYPT_TKIP=m CONFIG_IEEE80211_SOFTMAC=m # CONFIG_IEEE80211_SOFTMAC_DEBUG is not set CONFIG_RFKILL=m CONFIG_RFKILL_INPUT=m CONFIG_NET_9P=m # CONFIG_NET_9P_DEBUG is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set # CONFIG_BLK_DEV_RAM is not set CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_MISC_DEVICES=y # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not set CONFIG_EEPROM_93CX6=m # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_SONY_LAPTOP is not set # CONFIG_THINKPAD_ACPI is not set # CONFIG_IDE is not set # # SCSI device support # CONFIG_RAID_ATTRS=y CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=m # CONFIG_SCSI_NETLINK is not set # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=m CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_CHR_DEV_SG=m # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set CONFIG_SCSI_ISCSI_ATTRS=m # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set CONFIG_SCSI_LOWLEVEL=y # CONFIG_ISCSI_TCP is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_HPTIOP is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_SRP is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y CONFIG_SATA_AHCI=y # CONFIG_SATA_SVW is not set # CONFIG_ATA_PIIX is not set # CONFIG_SATA_MV is not set CONFIG_SATA_NV=y # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set CONFIG_SATA_SIL=y CONFIG_SATA_SIL24=y # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ALI is not set CONFIG_PATA_AMD=m # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set CONFIG_MD=y CONFIG_BLK_DEV_MD=y # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set CONFIG_MD_RAID1=y # CONFIG_MD_RAID10 is not set CONFIG_MD_RAID456=y CONFIG_MD_RAID5_RESHAPE=y # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # CONFIG_DM_DELAY is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # CONFIG_FIREWIRE is not set CONFIG_IEEE1394=y # # Subsystem Options # # CONFIG_IEEE1394_VERBOSEDEBUG is not set # # Controllers # # CONFIG_IEEE1394_PCILYNX is not set CONFIG_IEEE1394_OHCI1394=y # # Protocols # CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y CONFIG_IEEE1394_ETH1394=y CONFIG_IEEE1394_DV1394=m CONFIG_IEEE1394_RAWIO=m CONFIG_I2O=y CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m # CONFIG_I2O_CONFIG_OLD_IOCTL is not set CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y # CONFIG_NETDEVICES_MULTIQUEUE is not set # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set CONFIG_VETH=m # CONFIG_NET_SB1000 is not set # CONFIG_IP1000 is not set # CONFIG_ARCNET is not set # CONFIG_NET_ETHERNET is not set CONFIG_MII=m CONFIG_NETDEV_1000=y # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_E1000E is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SIS190 is not set # CONFIG_SKGE is not set # CONFIG_SKY2 is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=y # CONFIG_BNX2 is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # # Wireless LAN # CONFIG_WLAN_PRE80211=y CONFIG_STRIP=m CONFIG_WLAN_80211=y CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW2100_DEBUG is not set CONFIG_IPW2200=m CONFIG_IPW2200_MONITOR=y CONFIG_IPW2200_RADIOTAP=y CONFIG_IPW2200_PROMISCUOUS=y CONFIG_IPW2200_QOS=y # CONFIG_IPW2200_DEBUG is not set CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m # CONFIG_LIBERTAS_DEBUG is not set CONFIG_AIRO=m CONFIG_HERMES=m CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_NORTEL_HERMES=m CONFIG_PCI_HERMES=m CONFIG_USB_ATMEL=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m CONFIG_PRISM54=m CONFIG_USB_ZD1201=m CONFIG_RTL8187=m CONFIG_ADM8211=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m CONFIG_ATH5K=m CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m CONFIG_BCM43XX=m CONFIG_BCM43XX_DEBUG=y CONFIG_BCM43XX_DMA=y CONFIG_BCM43XX_PIO=y CONFIG_BCM43XX_DMA_AND_PIO_MODE=y # CONFIG_BCM43XX_DMA_MODE is not set # CONFIG_BCM43XX_PIO_MODE is not set CONFIG_B43=m CONFIG_B43_PCI_AUTOSELECT=y CONFIG_B43_PCICORE_AUTOSELECT=y # CONFIG_B43_DEBUG is not set CONFIG_B43_DMA=y CONFIG_B43_PIO=y CONFIG_B43_DMA_AND_PIO_MODE=y # CONFIG_B43_DMA_MODE is not set # CONFIG_B43_PIO_MODE is not set CONFIG_B43LEGACY=m CONFIG_B43LEGACY_PCI_AUTOSELECT=y CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y # CONFIG_B43LEGACY_DEBUG is not set CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_PIO=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set # CONFIG_B43LEGACY_PIO_MODE is not set CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set CONFIG_RT2X00=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB_FIRMWARE=y # CONFIG_RT2400PCI is not set # CONFIG_RT2500PCI is not set # CONFIG_RT61PCI is not set CONFIG_RT2500USB=m CONFIG_RT73USB=m # CONFIG_RT2X00_DEBUG is not set CONFIG_Z1211=m # CONFIG_Z1211_DEBUG is not set # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET_MII=m CONFIG_USB_USBNET=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set CONFIG_PPP=m # CONFIG_PPP_MULTILINK is not set CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOL2TP=m # CONFIG_SLIP is not set CONFIG_SLHC=m # CONFIG_NET_FC is not set CONFIG_SHAPER=m # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set CONFIG_INPUT_POLLDEV=m # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=y # CONFIG_INPUT_ATLAS_BTNS is not set # CONFIG_INPUT_ATI_REMOTE is not set # CONFIG_INPUT_ATI_REMOTE2 is not set # CONFIG_INPUT_KEYSPAN_REMOTE is not set # CONFIG_INPUT_POWERMATE is not set # CONFIG_INPUT_YEALINK is not set # CONFIG_INPUT_UINPUT is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y # CONFIG_VT_UNICODE is not set CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=1 CONFIG_SERIAL_8250_RUNTIME_UARTS=1 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # CONFIG_IPMI_HANDLER is not set CONFIG_HW_RANDOM=m CONFIG_HW_RANDOM_INTEL=m # CONFIG_HW_RANDOM_AMD is not set # CONFIG_NVRAM is not set CONFIG_RTC=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set CONFIG_AGP=y CONFIG_AGP_AMD64=y # CONFIG_AGP_INTEL is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_DRM=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=m # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_RAW_DRIVER is not set CONFIG_HPET=y # CONFIG_HPET_RTC_IRQ is not set CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=y # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y # # I2C Algorithms # CONFIG_I2C_ALGOBIT=y CONFIG_I2C_ALGOPCF=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set CONFIG_I2C_AMD756=m # CONFIG_I2C_AMD756_S4882 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_I810 is not set # CONFIG_I2C_PIIX4 is not set CONFIG_I2C_NFORCE2=m # CONFIG_I2C_OCORES is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_PROSAVAGE is not set # CONFIG_I2C_SAVAGE4 is not set # CONFIG_I2C_SIMTEC is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_STUB is not set # CONFIG_I2C_TINY_USB is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # CONFIG_I2C_VOODOO3 is not set # # Miscellaneous I2C Chip support # CONFIG_SENSORS_DS1337=m CONFIG_SENSORS_DS1374=m # CONFIG_DS1682 is not set CONFIG_SENSORS_EEPROM=m CONFIG_SENSORS_PCF8574=m CONFIG_SENSORS_PCA9539=m CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_MAX6875=m # CONFIG_SENSORS_TSL2550 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # SPI support # CONFIG_SPI=y # CONFIG_SPI_DEBUG is not set CONFIG_SPI_MASTER=y # # SPI Master Controller Drivers # CONFIG_SPI_BITBANG=m # # SPI Protocol Masters # CONFIG_SPI_AT25=m # CONFIG_SPI_SPIDEV is not set # CONFIG_SPI_TLE62X0 is not set # CONFIG_W1 is not set # CONFIG_POWER_SUPPLY is not set CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7470 is not set CONFIG_SENSORS_K8TEMP=y # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set # CONFIG_SENSORS_IT87 is not set CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM70=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Sonics Silicon Backplane # CONFIG_SSB_POSSIBLE=y CONFIG_SSB=m CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y # CONFIG_SSB_DEBUG is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y # CONFIG_WATCHDOG is not set # # Multifunction device drivers # # CONFIG_MFD_SM501 is not set # # Multimedia devices # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L1=y CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_TDA9875=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_TVP5150=m CONFIG_VIDEO_CX25840=m CONFIG_VIDEO_CX2341X=m # CONFIG_VIDEO_VIVI is not set CONFIG_VIDEO_BT848=m # CONFIG_VIDEO_SAA6588 is not set # CONFIG_VIDEO_CPIA is not set # CONFIG_VIDEO_CPIA2 is not set # CONFIG_VIDEO_SAA5246A is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_TUNER_3036 is not set # CONFIG_VIDEO_STRADIS is not set # CONFIG_VIDEO_ZORAN is not set # CONFIG_VIDEO_SAA7134 is not set # CONFIG_VIDEO_MXB is not set # CONFIG_VIDEO_DPC is not set # CONFIG_VIDEO_HEXIUM_ORION is not set # CONFIG_VIDEO_HEXIUM_GEMINI is not set # CONFIG_VIDEO_CX88 is not set # CONFIG_VIDEO_IVTV is not set # CONFIG_VIDEO_CAFE_CCIC is not set CONFIG_V4L_USB_DRIVERS=y CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_29XXX=y CONFIG_VIDEO_PVRUSB2_24XXX=y CONFIG_VIDEO_PVRUSB2_SYSFS=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_EM28XX=m CONFIG_VIDEO_USBVISION=m CONFIG_VIDEO_USBVIDEO=m CONFIG_USB_VICAM=m CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m CONFIG_USB_QUICKCAM_MESSENGER=m CONFIG_USB_ET61X251=m CONFIG_VIDEO_OVCAMCHIP=m CONFIG_USB_W9968CF=m CONFIG_USB_OV511=m CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m CONFIG_USB_ZC0301=m CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_ZR364XX=m CONFIG_USB_STK11XX=m # CONFIG_RADIO_ADAPTERS is not set # CONFIG_DVB_CORE is not set CONFIG_VIDEO_TUNER=m # CONFIG_VIDEO_TUNER_CUSTOMIZE is not set CONFIG_TUNER_MT20XX=m CONFIG_TUNER_TDA8290=m CONFIG_TUNER_TEA5761=m CONFIG_TUNER_TEA5767=m CONFIG_TUNER_SIMPLE=m CONFIG_VIDEO_BUF=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m # CONFIG_DAB is not set # # Graphics support # # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set # CONFIG_FB is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_VIDEO_SELECT=y CONFIG_DUMMY_CONSOLE=y CONFIG_FONT_8x16=y # # Sound # CONFIG_SOUND=y # # Advanced Linux Sound Architecture # CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_HWDEP=y CONFIG_SND_RAWMIDI=m # CONFIG_SND_SEQUENCER is not set # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set # CONFIG_SND_RTCTIMER is not set # CONFIG_SND_DYNAMIC_MINORS is not set # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # # CONFIG_SND_DUMMY is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # PCI devices # # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set CONFIG_SND_BT87X=y # CONFIG_SND_BT87X_OVERCLOCK is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_FM801 is not set CONFIG_SND_HDA_INTEL=y CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y # CONFIG_SND_HDA_CODEC_ATIHDMI is not set CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0 # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set # CONFIG_SND_INTEL8X0 is not set # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set # # SPI devices # # # USB devices # # CONFIG_SND_USB_AUDIO is not set # CONFIG_SND_USB_USX2Y is not set CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y # # System on Chip audio support # # CONFIG_SND_SOC is not set # # SoC Audio support for SuperH # # # Open Sound System # # CONFIG_SOUND_PRIME is not set CONFIG_HID_SUPPORT=y CONFIG_HID=m # CONFIG_HID_DEBUG is not set CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=m # CONFIG_USB_HIDINPUT_POWERBOOK is not set # CONFIG_HID_FF is not set CONFIG_USB_HIDDEV=y # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set CONFIG_USB_DYNAMIC_MINORS=y CONFIG_USB_SUSPEND=y # CONFIG_USB_PERSIST is not set # CONFIG_USB_OTG is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_SPLIT_ISO=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_ISP116X_HCD is not set CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_DATAFAB=y CONFIG_USB_STORAGE_FREECOM=y CONFIG_USB_STORAGE_DPCM=y CONFIG_USB_STORAGE_USBAT=y CONFIG_USB_STORAGE_SDDR09=y CONFIG_USB_STORAGE_SDDR55=y CONFIG_USB_STORAGE_JUMPSHOT=y CONFIG_USB_STORAGE_ALAUDA=y CONFIG_USB_STORAGE_KARMA=y CONFIG_USB_LIBUSUAL=y # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m # CONFIG_USB_MON is not set # # USB port drivers # # # USB Serial Converter support # CONFIG_USB_SERIAL=m CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_AIRPRIME=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP2101=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m # CONFIG_USB_SERIAL_FUNSOFT is not set CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m # CONFIG_USB_SERIAL_KEYSPAN is not set CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m CONFIG_USB_SERIAL_SAFE_PADDED=y CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m # CONFIG_USB_SERIAL_DEBUG is not set CONFIG_USB_EZUSB=y # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_AUERSWALD=m CONFIG_USB_RIO500=m CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m CONFIG_USB_BERRY_CHARGE=m CONFIG_USB_LED=m CONFIG_USB_CYPRESS_CY7C63=m CONFIG_USB_CYTHERM=m CONFIG_USB_PHIDGET=m CONFIG_USB_PHIDGETKIT=m CONFIG_USB_PHIDGETMOTORCONTROL=m CONFIG_USB_PHIDGETSERVO=m CONFIG_USB_IDMOUSE=m # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y CONFIG_USB_LD=m CONFIG_USB_TRANCEVIBRATOR=m CONFIG_USB_IOWARRIOR=m # CONFIG_USB_TEST is not set CONFIG_USB_GOTEMP=m # # USB DSL modem support # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # CONFIG_MMC is not set CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=m # # LED drivers # # # LED Triggers # CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_HEARTBEAT=m # CONFIG_INFINIBAND is not set CONFIG_EDAC=y # # Reporting subsystems # # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_MM_EDAC=y # CONFIG_EDAC_E752X is not set # CONFIG_EDAC_I82975X is not set # CONFIG_EDAC_I5000 is not set # CONFIG_RTC_CLASS is not set CONFIG_DMADEVICES=y # # DMA Devices # # CONFIG_INTEL_IOATDMA is not set CONFIG_VIRTUALIZATION=y CONFIG_KVM=m # CONFIG_KVM_INTEL is not set CONFIG_KVM_AMD=m # # Userspace I/O # # CONFIG_UIO is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_DMIID=y # # File systems # CONFIG_EXT2_FS=m CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y # CONFIG_EXT4DEV_FS is not set CONFIG_JBD=m # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=m # CONFIG_REISER4_FS is not set # CONFIG_REISERFS_FS is not set CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y CONFIG_JFS_SECURITY=y # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set CONFIG_FS_POSIX_ACL=y CONFIG_XFS_FS=y CONFIG_XFS_QUOTA=y CONFIG_XFS_SECURITY=y CONFIG_XFS_POSIX_ACL=y # CONFIG_XFS_RT is not set CONFIG_GFS2_FS=m CONFIG_GFS2_FS_LOCKING_NOLOCK=m CONFIG_GFS2_FS_LOCKING_DLM=m CONFIG_OCFS2_FS=m # CONFIG_OCFS2_DEBUG_MASKLOG is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_QUOTA=y # CONFIG_QUOTA_NETLINK_INTERFACE is not set # CONFIG_PRINT_QUOTA_WARNING is not set # CONFIG_QFMT_V1 is not set CONFIG_QFMT_V2=y CONFIG_QUOTACTL=y CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set CONFIG_NTFS_RW=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=m # # Layered filesystems # # CONFIG_UNION_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set CONFIG_CRAMFS=m # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set CONFIG_UFS_FS=m CONFIG_UFS_FS_WRITE=y # CONFIG_UFS_DEBUG is not set # # Network File Systems # CONFIG_NFS_FS=y # CONFIG_NFS_V3 is not set CONFIG_NFS_V4=y CONFIG_NFS_DIRECTIO=y CONFIG_NFSD=m CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set CONFIG_NFSD_V4=y CONFIG_NFSD_TCP=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_SUNRPC_BIND34=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set CONFIG_CIFS=m CONFIG_CIFS_STATS=y CONFIG_CIFS_STATS2=y CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_EXPERIMENTAL=y CONFIG_CIFS_UPCALL=y # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set CONFIG_9P_FS=m # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y # CONFIG_MINIX_SUBPARTITION is not set CONFIG_SOLARIS_X86_PARTITION=y # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_PARTITION is not set # CONFIG_EFI_PARTITION is not set # CONFIG_SYSV68_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="cp850" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=y # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set CONFIG_NLS_CODEPAGE_1250=m # CONFIG_NLS_CODEPAGE_1251 is not set CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=m # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=m # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set CONFIG_NLS_UTF8=m # # Distributed Lock Manager # CONFIG_DLM=m # CONFIG_DLM_DEBUG is not set # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_PRINTK_TIME=y # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_PAGE_OWNER is not set CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_SCHED_DEBUG is not set # CONFIG_SCHEDSTATS is not set CONFIG_TIMER_STATS=y # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set # CONFIG_FRAME_POINTER is not set # CONFIG_UNWIND_INFO is not set # CONFIG_PROFILE_LIKELY is not set # CONFIG_FORCED_INLINING is not set # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_DEBUG_SYNCHRO_TEST is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_WANT_EXTRA_DEBUG_INFORMATION is not set # CONFIG_KGDB is not set # CONFIG_KGDB_ATTACH_WAIT is not set # CONFIG_DEBUG_RODATA is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # # Security options # # CONFIG_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITY_NETWORK is not set CONFIG_SECURITY_CAPABILITIES=y # CONFIG_SECURITY_FILE_CAPABILITIES is not set # CONFIG_SECURITY_ROOTPLUG is not set # CONFIG_SECURITY_SELINUX is not set CONFIG_XOR_BLOCKS=y CONFIG_ASYNC_CORE=y CONFIG_ASYNC_MEMCPY=y CONFIG_ASYNC_XOR=y CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ABLKCIPHER=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_ECB=m CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_CRYPTD=y CONFIG_CRYPTO_DES=y CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=y CONFIG_CRYPTO_TWOFISH_X86_64=y CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_DEFLATE=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_CAMELLIA=m # CONFIG_CRYPTO_TEST is not set CONFIG_CRYPTO_AUTHENC=m # CONFIG_CRYPTO_HW is not set # # Library routines # CONFIG_BITREVERSE=m CONFIG_CRC_CCITT=m CONFIG_CRC16=m CONFIG_CRC_ITU_T=m CONFIG_CRC32=m CONFIG_CRC7=m CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 9:08 ` Torsten Kaiser @ 2007-09-25 9:27 ` Damien Wyart 2007-09-25 9:58 ` Damien Wyart 2007-09-25 11:25 ` Alexey Starikovskiy 1 sibling, 1 reply; 32+ messages in thread From: Damien Wyart @ 2007-09-25 9:27 UTC (permalink / raw) To: Torsten Kaiser Cc: Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi Hello, > On 9/25/07, Alexey Starikovskiy <astarikovskiy@suse.de> wrote: > > Do you have CONFIG_ACPI_SLEEP enabled in your .config? * Torsten Kaiser <just.for.lkml@googlemail.com> [2007-09-25 11:08]: > I'm answering that too, because I suspect that my "2.6.23-rc7-mm1 does > not power off"-error might have the same cause. > No, I do not have CONFIG_ACPI_SLEEP set, > because I do not have CONFIG_PM_SLEEP set, > because I do not want SUSPEND and/or HIBERNATION. Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same reason (and this worked fine without them in rc7). I do not think these settings should have changed between rc7 and rc8. -- Damien Wyart ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 9:27 ` Damien Wyart @ 2007-09-25 9:58 ` Damien Wyart 2007-09-25 11:45 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Damien Wyart @ 2007-09-25 9:58 UTC (permalink / raw) To: Torsten Kaiser Cc: Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi > > No, I do not have CONFIG_ACPI_SLEEP set, > > because I do not have CONFIG_PM_SLEEP set, > > because I do not want SUSPEND and/or HIBERNATION. > Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > reason (and this worked fine without them in rc7). I do not think > these settings should have changed between rc7 and rc8. Also, another test I just did: on another computer, rc8 is fine regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can provide config if needed. Best, -- Damien Wyart ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 9:58 ` Damien Wyart @ 2007-09-25 11:45 ` Rafael J. Wysocki 2007-09-25 12:02 ` Damien Wyart 2007-09-25 12:05 ` Rafael J. Wysocki 0 siblings, 2 replies; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 11:45 UTC (permalink / raw) To: Damien Wyart Cc: Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > > > No, I do not have CONFIG_ACPI_SLEEP set, > > > because I do not have CONFIG_PM_SLEEP set, > > > because I do not want SUSPEND and/or HIBERNATION. > > > Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > > reason (and this worked fine without them in rc7). I do not think > > these settings should have changed between rc7 and rc8. Well, we haven't changed much. > Also, another test I just did: on another computer, rc8 is fine > regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > provide config if needed. On the box that fails to power off, can you please test -rc8 with these two commits reverted: commit 5a50fe709d527f31169263e36601dd83446d5744 ACPI: suspend: consolidate handling of Sx states addendum commit f216cc3748a3a22c2b99390fddcdafa0583791a2 ACPI: suspend: consolidate handling of Sx states. and see if it works? Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 11:45 ` Rafael J. Wysocki @ 2007-09-25 12:02 ` Damien Wyart 2007-09-25 15:05 ` Damien Wyart 2007-09-25 12:05 ` Rafael J. Wysocki 1 sibling, 1 reply; 32+ messages in thread From: Damien Wyart @ 2007-09-25 12:02 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi > On the box that fails to power off, can you please test -rc8 with these two > commits reverted: > commit 5a50fe709d527f31169263e36601dd83446d5744 > ACPI: suspend: consolidate handling of Sx states addendum > commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > ACPI: suspend: consolidate handling of Sx states. > and see if it works? I had done these tests in the first place (see my first mail), so yes, reverting makes the box power off fine. Will test this evening the patch you pointed in your next message. -- Damien Wyart ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 12:02 ` Damien Wyart @ 2007-09-25 15:05 ` Damien Wyart 2007-09-26 1:39 ` Mike Houston 0 siblings, 1 reply; 32+ messages in thread From: Damien Wyart @ 2007-09-25 15:05 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi > Will test this evening the patch you pointed in your next message. Ok, with both patches (including the very latest one from Alexey --- tried the "stylistically correct" one), machine halts fine again. Thanks to all for having looked at this! -- Damien Wyart ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 15:05 ` Damien Wyart @ 2007-09-26 1:39 ` Mike Houston 0 siblings, 0 replies; 32+ messages in thread From: Mike Houston @ 2007-09-26 1:39 UTC (permalink / raw) To: Damien Wyart Cc: Rafael J. Wysocki, Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tue, 25 Sep 2007 17:05:00 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > > Will test this evening the patch you pointed in your next message. > > Ok, with both patches (including the very latest one from Alexey --- > tried the "stylistically correct" one), machine halts fine again. > Thanks to all for having looked at this! Same here, applying the two patches in this thread fixed the problem for me, on my Intel 965P based system. It now does the acpi power off correctly once again, and I have noticed no other problems with 2.6.23-rc8. "move acpi_sleep_prepare outside of CONFIG_SUSPEND" and the last "ACPI: suspend: fix ACPI_SLEEP states" Thanks Alexey and Rafael. Mike Houston ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 11:45 ` Rafael J. Wysocki 2007-09-25 12:02 ` Damien Wyart @ 2007-09-25 12:05 ` Rafael J. Wysocki 2007-09-25 12:05 ` Alexey Starikovskiy 1 sibling, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 12:05 UTC (permalink / raw) To: Damien Wyart Cc: Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > > > > No, I do not have CONFIG_ACPI_SLEEP set, > > > > because I do not have CONFIG_PM_SLEEP set, > > > > because I do not want SUSPEND and/or HIBERNATION. > > > > > Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > > > reason (and this worked fine without them in rc7). I do not think > > > these settings should have changed between rc7 and rc8. > > Well, we haven't changed much. > > > Also, another test I just did: on another computer, rc8 is fine > > regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > > provide config if needed. > > On the box that fails to power off, can you please test -rc8 with these two > commits reverted: > > commit 5a50fe709d527f31169263e36601dd83446d5744 > ACPI: suspend: consolidate handling of Sx states addendum > > commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > ACPI: suspend: consolidate handling of Sx states. > > and see if it works? If it does, please test the patch from this message http://marc.info/?l=linux-kernel&m=119052978117735&w=4 on top of vanilla 2.6.23-rc8. Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 12:05 ` Rafael J. Wysocki @ 2007-09-25 12:05 ` Alexey Starikovskiy 2007-09-25 12:39 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 12:05 UTC (permalink / raw) To: Damien Wyart, Torsten Kaiser Cc: Rafael J. Wysocki, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi [-- Attachment #1: Type: text/plain, Size: 1524 bytes --] Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: >> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: >>>>> No, I do not have CONFIG_ACPI_SLEEP set, >>>>> because I do not have CONFIG_PM_SLEEP set, >>>>> because I do not want SUSPEND and/or HIBERNATION. >>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same >>>> reason (and this worked fine without them in rc7). I do not think >>>> these settings should have changed between rc7 and rc8. >> Well, we haven't changed much. >> >>> Also, another test I just did: on another computer, rc8 is fine >>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can >>> provide config if needed. >> On the box that fails to power off, can you please test -rc8 with these two >> commits reverted: >> >> commit 5a50fe709d527f31169263e36601dd83446d5744 >> ACPI: suspend: consolidate handling of Sx states addendum >> >> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 >> ACPI: suspend: consolidate handling of Sx states. >> >> and see if it works? > > If it does, please test the patch from this message > > http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > > on top of vanilla 2.6.23-rc8. You will need one more patch on top of just mentioned one. Regards, Alex. > > Greetings, > Rafael > - > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > [-- Attachment #2: fix-ACPI_SLEEP_states.patch --] [-- Type: text/x-patch, Size: 2299 bytes --] ACPI: suspend: fix ACPI_SLEEP states From: Alexey Starikovskiy <astarikovskiy@suse.de> Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de> --- drivers/acpi/sleep/Makefile | 2 +- drivers/acpi/sleep/main.c | 7 +++++-- include/acpi/acpi_drivers.h | 4 ---- 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/acpi/sleep/Makefile b/drivers/acpi/sleep/Makefile index ba9bd40..f1fb888 100644 --- a/drivers/acpi/sleep/Makefile +++ b/drivers/acpi/sleep/Makefile @@ -1,5 +1,5 @@ obj-y := wakeup.o -obj-$(CONFIG_ACPI_SLEEP) += main.o +obj-y += main.o obj-$(CONFIG_ACPI_SLEEP) += proc.o EXTRA_CFLAGS += $(ACPI_CFLAGS) diff --git a/drivers/acpi/sleep/main.c b/drivers/acpi/sleep/main.c index c79edcb..86415f1 100644 --- a/drivers/acpi/sleep/main.c +++ b/drivers/acpi/sleep/main.c @@ -24,8 +24,6 @@ u8 sleep_states[ACPI_S_STATE_COUNT]; -static u32 acpi_target_sleep_state = ACPI_STATE_S0; - int acpi_sleep_prepare(u32 acpi_state) { #ifdef CONFIG_ACPI_SLEEP @@ -48,6 +46,9 @@ int acpi_sleep_prepare(u32 acpi_state) } #ifdef CONFIG_SUSPEND + +static u32 acpi_target_sleep_state = ACPI_STATE_S0; + static struct pm_ops acpi_pm_ops; extern void do_suspend_lowlevel(void); @@ -299,6 +300,7 @@ int acpi_suspend(u32 acpi_state) return -EINVAL; } +#ifdef CONFIG_PM_SLEEP /** * acpi_pm_device_sleep_state - return preferred power state of ACPI device * in the system sleep state given by %acpi_target_sleep_state @@ -373,6 +375,7 @@ int acpi_pm_device_sleep_state(struct device *dev, int wake, int *d_min_p) *d_min_p = d_min; return d_max; } +#endif static void acpi_power_off_prepare(void) { diff --git a/include/acpi/acpi_drivers.h b/include/acpi/acpi_drivers.h index 202acb9..f85f77a 100644 --- a/include/acpi/acpi_drivers.h +++ b/include/acpi/acpi_drivers.h @@ -147,10 +147,6 @@ static inline void unregister_hotplug_dock_device(acpi_handle handle) /*-------------------------------------------------------------------------- Suspend/Resume -------------------------------------------------------------------------- */ -#ifdef CONFIG_ACPI_SLEEP extern int acpi_sleep_init(void); -#else -static inline int acpi_sleep_init(void) { return 0; } -#endif #endif /*__ACPI_DRIVERS_H__*/ ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 12:05 ` Alexey Starikovskiy @ 2007-09-25 12:39 ` Rafael J. Wysocki 2007-09-25 12:53 ` Alexey Starikovskiy 0 siblings, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 12:39 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Damien Wyart, Torsten Kaiser, Alexey Starikovskiy, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > >> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > >>>>> No, I do not have CONFIG_ACPI_SLEEP set, > >>>>> because I do not have CONFIG_PM_SLEEP set, > >>>>> because I do not want SUSPEND and/or HIBERNATION. > >>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > >>>> reason (and this worked fine without them in rc7). I do not think > >>>> these settings should have changed between rc7 and rc8. > >> Well, we haven't changed much. > >> > >>> Also, another test I just did: on another computer, rc8 is fine > >>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > >>> provide config if needed. > >> On the box that fails to power off, can you please test -rc8 with these two > >> commits reverted: > >> > >> commit 5a50fe709d527f31169263e36601dd83446d5744 > >> ACPI: suspend: consolidate handling of Sx states addendum > >> > >> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > >> ACPI: suspend: consolidate handling of Sx states. > >> > >> and see if it works? > > > > If it does, please test the patch from this message > > > > http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > > > > on top of vanilla 2.6.23-rc8. > You will need one more patch on top of just mentioned one. Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? CONFIG_HIBERNATION needs acpi_target_sleep_state too. Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 12:39 ` Rafael J. Wysocki @ 2007-09-25 12:53 ` Alexey Starikovskiy 2007-09-25 13:25 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 12:53 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi [-- Attachment #1: Type: text/plain, Size: 1604 bytes --] Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: >> Rafael J. Wysocki wrote: >>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: >>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: >>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, >>>>>>> because I do not have CONFIG_PM_SLEEP set, >>>>>>> because I do not want SUSPEND and/or HIBERNATION. >>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same >>>>>> reason (and this worked fine without them in rc7). I do not think >>>>>> these settings should have changed between rc7 and rc8. >>>> Well, we haven't changed much. >>>> >>>>> Also, another test I just did: on another computer, rc8 is fine >>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can >>>>> provide config if needed. >>>> On the box that fails to power off, can you please test -rc8 with these two >>>> commits reverted: >>>> >>>> commit 5a50fe709d527f31169263e36601dd83446d5744 >>>> ACPI: suspend: consolidate handling of Sx states addendum >>>> >>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 >>>> ACPI: suspend: consolidate handling of Sx states. >>>> >>>> and see if it works? >>> If it does, please test the patch from this message >>> >>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 >>> >>> on top of vanilla 2.6.23-rc8. >> You will need one more patch on top of just mentioned one. > > Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? > > CONFIG_HIBERNATION needs acpi_target_sleep_state too. Agree, attaching updated patch. Thanks, Alex. [-- Attachment #2: fix-ACPI_SLEEP_states.patch --] [-- Type: text/x-patch, Size: 2282 bytes --] ACPI: suspend: fix ACPI_SLEEP states From: Alexey Starikovskiy <astarikovskiy@suse.de> Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de> --- drivers/acpi/sleep/Makefile | 2 +- drivers/acpi/sleep/main.c | 5 +++++ include/acpi/acpi_drivers.h | 4 ---- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/drivers/acpi/sleep/Makefile b/drivers/acpi/sleep/Makefile index ba9bd40..f1fb888 100644 --- a/drivers/acpi/sleep/Makefile +++ b/drivers/acpi/sleep/Makefile @@ -1,5 +1,5 @@ obj-y := wakeup.o -obj-$(CONFIG_ACPI_SLEEP) += main.o +obj-y += main.o obj-$(CONFIG_ACPI_SLEEP) += proc.o EXTRA_CFLAGS += $(ACPI_CFLAGS) diff --git a/drivers/acpi/sleep/main.c b/drivers/acpi/sleep/main.c index c79edcb..6ea0628 100644 --- a/drivers/acpi/sleep/main.c +++ b/drivers/acpi/sleep/main.c @@ -24,7 +24,9 @@ u8 sleep_states[ACPI_S_STATE_COUNT]; +#if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION) static u32 acpi_target_sleep_state = ACPI_STATE_S0; +#endif int acpi_sleep_prepare(u32 acpi_state) { @@ -48,6 +50,7 @@ int acpi_sleep_prepare(u32 acpi_state) } #ifdef CONFIG_SUSPEND + static struct pm_ops acpi_pm_ops; extern void do_suspend_lowlevel(void); @@ -299,6 +302,7 @@ int acpi_suspend(u32 acpi_state) return -EINVAL; } +#ifdef CONFIG_PM_SLEEP /** * acpi_pm_device_sleep_state - return preferred power state of ACPI device * in the system sleep state given by %acpi_target_sleep_state @@ -373,6 +377,7 @@ int acpi_pm_device_sleep_state(struct device *dev, int wake, int *d_min_p) *d_min_p = d_min; return d_max; } +#endif static void acpi_power_off_prepare(void) { diff --git a/include/acpi/acpi_drivers.h b/include/acpi/acpi_drivers.h index 202acb9..f85f77a 100644 --- a/include/acpi/acpi_drivers.h +++ b/include/acpi/acpi_drivers.h @@ -147,10 +147,6 @@ static inline void unregister_hotplug_dock_device(acpi_handle handle) /*-------------------------------------------------------------------------- Suspend/Resume -------------------------------------------------------------------------- */ -#ifdef CONFIG_ACPI_SLEEP extern int acpi_sleep_init(void); -#else -static inline int acpi_sleep_init(void) { return 0; } -#endif #endif /*__ACPI_DRIVERS_H__*/ ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 12:53 ` Alexey Starikovskiy @ 2007-09-25 13:25 ` Rafael J. Wysocki 2007-09-25 13:15 ` Alexey Starikovskiy 0 siblings, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 13:25 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: > >> Rafael J. Wysocki wrote: > >>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > >>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > >>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, > >>>>>>> because I do not have CONFIG_PM_SLEEP set, > >>>>>>> because I do not want SUSPEND and/or HIBERNATION. > >>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > >>>>>> reason (and this worked fine without them in rc7). I do not think > >>>>>> these settings should have changed between rc7 and rc8. > >>>> Well, we haven't changed much. > >>>> > >>>>> Also, another test I just did: on another computer, rc8 is fine > >>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > >>>>> provide config if needed. > >>>> On the box that fails to power off, can you please test -rc8 with these two > >>>> commits reverted: > >>>> > >>>> commit 5a50fe709d527f31169263e36601dd83446d5744 > >>>> ACPI: suspend: consolidate handling of Sx states addendum > >>>> > >>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > >>>> ACPI: suspend: consolidate handling of Sx states. > >>>> > >>>> and see if it works? > >>> If it does, please test the patch from this message > >>> > >>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > >>> > >>> on top of vanilla 2.6.23-rc8. > >> You will need one more patch on top of just mentioned one. > > > > Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? > > > > CONFIG_HIBERNATION needs acpi_target_sleep_state too. > Agree, attaching updated patch. Well, please use "ifdef CONFIG_PM_SLEEP" instead of "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", as you did with the second block. Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 13:25 ` Rafael J. Wysocki @ 2007-09-25 13:15 ` Alexey Starikovskiy 2007-09-25 14:18 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 13:15 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: >> Rafael J. Wysocki wrote: >>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: >>>> Rafael J. Wysocki wrote: >>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: >>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: >>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, >>>>>>>>> because I do not have CONFIG_PM_SLEEP set, >>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. >>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same >>>>>>>> reason (and this worked fine without them in rc7). I do not think >>>>>>>> these settings should have changed between rc7 and rc8. >>>>>> Well, we haven't changed much. >>>>>> >>>>>>> Also, another test I just did: on another computer, rc8 is fine >>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can >>>>>>> provide config if needed. >>>>>> On the box that fails to power off, can you please test -rc8 with these two >>>>>> commits reverted: >>>>>> >>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 >>>>>> ACPI: suspend: consolidate handling of Sx states addendum >>>>>> >>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 >>>>>> ACPI: suspend: consolidate handling of Sx states. >>>>>> >>>>>> and see if it works? >>>>> If it does, please test the patch from this message >>>>> >>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 >>>>> >>>>> on top of vanilla 2.6.23-rc8. >>>> You will need one more patch on top of just mentioned one. >>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? >>> >>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. >> Agree, attaching updated patch. > > Well, please use "ifdef CONFIG_PM_SLEEP" instead of > "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", > as you did with the second block. I was thinking about that, but it seem to be less clear... We need this variable only for suspend or hibernation, nothing else. with pm_sleep it is not visible at all. Thoughts? ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 13:15 ` Alexey Starikovskiy @ 2007-09-25 14:18 ` Rafael J. Wysocki 2007-09-25 14:19 ` Alexey Starikovskiy 0 siblings, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 14:18 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: > >> Rafael J. Wysocki wrote: > >>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: > >>>> Rafael J. Wysocki wrote: > >>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > >>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > >>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, > >>>>>>>>> because I do not have CONFIG_PM_SLEEP set, > >>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. > >>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > >>>>>>>> reason (and this worked fine without them in rc7). I do not think > >>>>>>>> these settings should have changed between rc7 and rc8. > >>>>>> Well, we haven't changed much. > >>>>>> > >>>>>>> Also, another test I just did: on another computer, rc8 is fine > >>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > >>>>>>> provide config if needed. > >>>>>> On the box that fails to power off, can you please test -rc8 with these two > >>>>>> commits reverted: > >>>>>> > >>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 > >>>>>> ACPI: suspend: consolidate handling of Sx states addendum > >>>>>> > >>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > >>>>>> ACPI: suspend: consolidate handling of Sx states. > >>>>>> > >>>>>> and see if it works? > >>>>> If it does, please test the patch from this message > >>>>> > >>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > >>>>> > >>>>> on top of vanilla 2.6.23-rc8. > >>>> You will need one more patch on top of just mentioned one. > >>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? > >>> > >>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. > >> Agree, attaching updated patch. > > > > Well, please use "ifdef CONFIG_PM_SLEEP" instead of > > "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", > > as you did with the second block. > I was thinking about that, but it seem to be less clear... > We need this variable only for suspend or hibernation, nothing else. > with pm_sleep it is not visible at all. > > Thoughts? Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look at kernel/power/Kconfig, and it was introduced exactly for the conditions like this. IOW, if we want something to be used for anything else than suspend or hibernation, it shouldn't be defined under PM_SLEEP. Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 14:18 ` Rafael J. Wysocki @ 2007-09-25 14:19 ` Alexey Starikovskiy 2007-09-25 14:52 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 14:19 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote: >> Rafael J. Wysocki wrote: >>> On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: >>>> Rafael J. Wysocki wrote: >>>>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: >>>>>> Rafael J. Wysocki wrote: >>>>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: >>>>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: >>>>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, >>>>>>>>>>> because I do not have CONFIG_PM_SLEEP set, >>>>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. >>>>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same >>>>>>>>>> reason (and this worked fine without them in rc7). I do not think >>>>>>>>>> these settings should have changed between rc7 and rc8. >>>>>>>> Well, we haven't changed much. >>>>>>>> >>>>>>>>> Also, another test I just did: on another computer, rc8 is fine >>>>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can >>>>>>>>> provide config if needed. >>>>>>>> On the box that fails to power off, can you please test -rc8 with these two >>>>>>>> commits reverted: >>>>>>>> >>>>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 >>>>>>>> ACPI: suspend: consolidate handling of Sx states addendum >>>>>>>> >>>>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 >>>>>>>> ACPI: suspend: consolidate handling of Sx states. >>>>>>>> >>>>>>>> and see if it works? >>>>>>> If it does, please test the patch from this message >>>>>>> >>>>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 >>>>>>> >>>>>>> on top of vanilla 2.6.23-rc8. >>>>>> You will need one more patch on top of just mentioned one. >>>>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? >>>>> >>>>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. >>>> Agree, attaching updated patch. >>> Well, please use "ifdef CONFIG_PM_SLEEP" instead of >>> "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", >>> as you did with the second block. >> I was thinking about that, but it seem to be less clear... >> We need this variable only for suspend or hibernation, nothing else. >> with pm_sleep it is not visible at all. >> >> Thoughts? > > Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look > at kernel/power/Kconfig, and it was introduced exactly for the conditions like > this. I've seen this then I wrote the patch :) See my point, it is not clear, that PM_SLEEP is equivalent to SUSPEND || HIBERNATION, one needs to grep Kconfig files to find that -- it means that code becomes less readable, and I would like to avoid that. > > IOW, if we want something to be used for anything else than suspend or > hibernation, it shouldn't be defined under PM_SLEEP. Agree, but we should distinguish there it is better to use PM_SLEEP, and there it is better to use (SUSPEND || HIBERNATION) just to be more expressive... Regards, Alex. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 14:19 ` Alexey Starikovskiy @ 2007-09-25 14:52 ` Rafael J. Wysocki 2007-09-25 14:45 ` Alexey Starikovskiy 0 siblings, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 14:52 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 16:19, Alexey Starikovskiy wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote: > >> Rafael J. Wysocki wrote: > >>> On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: > >>>> Rafael J. Wysocki wrote: > >>>>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: > >>>>>> Rafael J. Wysocki wrote: > >>>>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > >>>>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > >>>>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, > >>>>>>>>>>> because I do not have CONFIG_PM_SLEEP set, > >>>>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. > >>>>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > >>>>>>>>>> reason (and this worked fine without them in rc7). I do not think > >>>>>>>>>> these settings should have changed between rc7 and rc8. > >>>>>>>> Well, we haven't changed much. > >>>>>>>> > >>>>>>>>> Also, another test I just did: on another computer, rc8 is fine > >>>>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > >>>>>>>>> provide config if needed. > >>>>>>>> On the box that fails to power off, can you please test -rc8 with these two > >>>>>>>> commits reverted: > >>>>>>>> > >>>>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 > >>>>>>>> ACPI: suspend: consolidate handling of Sx states addendum > >>>>>>>> > >>>>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > >>>>>>>> ACPI: suspend: consolidate handling of Sx states. > >>>>>>>> > >>>>>>>> and see if it works? > >>>>>>> If it does, please test the patch from this message > >>>>>>> > >>>>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > >>>>>>> > >>>>>>> on top of vanilla 2.6.23-rc8. > >>>>>> You will need one more patch on top of just mentioned one. > >>>>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? > >>>>> > >>>>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. > >>>> Agree, attaching updated patch. > >>> Well, please use "ifdef CONFIG_PM_SLEEP" instead of > >>> "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", > >>> as you did with the second block. > >> I was thinking about that, but it seem to be less clear... > >> We need this variable only for suspend or hibernation, nothing else. > >> with pm_sleep it is not visible at all. > >> > >> Thoughts? > > > > Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look > > at kernel/power/Kconfig, and it was introduced exactly for the conditions like > > this. > I've seen this then I wrote the patch :) See my point, it is not clear, > that PM_SLEEP is equivalent to SUSPEND || HIBERNATION, one needs to > grep Kconfig files to find that -- it means that code becomes less readable, > and I would like to avoid that. I see your point. Still, you are using PM_SLEEP in the same file, so someone reading the code for the first time will have to find out what it is anyway. OTOH, the only function of PM_SLEEP is to be a replacement for (SUSPEND || HIBERNATION). It has no other meaning whatsoever. [Well, sorry, I couldn't invent a better name.] > > IOW, if we want something to be used for anything else than suspend or > > hibernation, it shouldn't be defined under PM_SLEEP. > Agree, but we should distinguish there it is better to use PM_SLEEP, > and there it is better to use (SUSPEND || HIBERNATION) just to be more expressive... Well, since PM_SLEEP is used as (SUSPEND || HIBERNATION) everywhere else, I think that it would actually be confusing not to use it here. :-) Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 14:52 ` Rafael J. Wysocki @ 2007-09-25 14:45 ` Alexey Starikovskiy 2007-09-25 15:54 ` Rafael J. Wysocki 2007-09-25 16:23 ` Andrew Morton 0 siblings, 2 replies; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 14:45 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi [-- Attachment #1: Type: text/plain, Size: 3802 bytes --] Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 16:19, Alexey Starikovskiy wrote: >> Rafael J. Wysocki wrote: >>> On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote: >>>> Rafael J. Wysocki wrote: >>>>> On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: >>>>>> Rafael J. Wysocki wrote: >>>>>>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: >>>>>>>> Rafael J. Wysocki wrote: >>>>>>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: >>>>>>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: >>>>>>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, >>>>>>>>>>>>> because I do not have CONFIG_PM_SLEEP set, >>>>>>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. >>>>>>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same >>>>>>>>>>>> reason (and this worked fine without them in rc7). I do not think >>>>>>>>>>>> these settings should have changed between rc7 and rc8. >>>>>>>>>> Well, we haven't changed much. >>>>>>>>>> >>>>>>>>>>> Also, another test I just did: on another computer, rc8 is fine >>>>>>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can >>>>>>>>>>> provide config if needed. >>>>>>>>>> On the box that fails to power off, can you please test -rc8 with these two >>>>>>>>>> commits reverted: >>>>>>>>>> >>>>>>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 >>>>>>>>>> ACPI: suspend: consolidate handling of Sx states addendum >>>>>>>>>> >>>>>>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 >>>>>>>>>> ACPI: suspend: consolidate handling of Sx states. >>>>>>>>>> >>>>>>>>>> and see if it works? >>>>>>>>> If it does, please test the patch from this message >>>>>>>>> >>>>>>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 >>>>>>>>> >>>>>>>>> on top of vanilla 2.6.23-rc8. >>>>>>>> You will need one more patch on top of just mentioned one. >>>>>>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? >>>>>>> >>>>>>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. >>>>>> Agree, attaching updated patch. >>>>> Well, please use "ifdef CONFIG_PM_SLEEP" instead of >>>>> "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", >>>>> as you did with the second block. >>>> I was thinking about that, but it seem to be less clear... >>>> We need this variable only for suspend or hibernation, nothing else. >>>> with pm_sleep it is not visible at all. >>>> >>>> Thoughts? >>> Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look >>> at kernel/power/Kconfig, and it was introduced exactly for the conditions like >>> this. >> I've seen this then I wrote the patch :) See my point, it is not clear, >> that PM_SLEEP is equivalent to SUSPEND || HIBERNATION, one needs to >> grep Kconfig files to find that -- it means that code becomes less readable, >> and I would like to avoid that. > > I see your point. Still, you are using PM_SLEEP in the same file, so someone > reading the code for the first time will have to find out what it is anyway. In the second place it depends on header file using PM_SLEEP, so it makes sense. > > OTOH, the only function of PM_SLEEP is to be a replacement for > (SUSPEND || HIBERNATION). It has no other meaning whatsoever. > > [Well, sorry, I couldn't invent a better name.] > >>> IOW, if we want something to be used for anything else than suspend or >>> hibernation, it shouldn't be defined under PM_SLEEP. >> Agree, but we should distinguish there it is better to use PM_SLEEP, >> and there it is better to use (SUSPEND || HIBERNATION) just to be more expressive... > > Well, since PM_SLEEP is used as (SUSPEND || HIBERNATION) everywhere else, > I think that it would actually be confusing not to use it here. :-) Ok, patch is here. Regards, Alex. [-- Attachment #2: fix-ACPI_SLEEP_states.patch --] [-- Type: text/x-patch, Size: 2083 bytes --] ACPI: suspend: fix ACPI_SLEEP states From: Alexey Starikovskiy <astarikovskiy@suse.de> Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de> --- drivers/acpi/sleep/Makefile | 2 +- drivers/acpi/sleep/main.c | 4 ++++ include/acpi/acpi_drivers.h | 4 ---- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/acpi/sleep/Makefile b/drivers/acpi/sleep/Makefile index ba9bd40..f1fb888 100644 --- a/drivers/acpi/sleep/Makefile +++ b/drivers/acpi/sleep/Makefile @@ -1,5 +1,5 @@ obj-y := wakeup.o -obj-$(CONFIG_ACPI_SLEEP) += main.o +obj-y += main.o obj-$(CONFIG_ACPI_SLEEP) += proc.o EXTRA_CFLAGS += $(ACPI_CFLAGS) diff --git a/drivers/acpi/sleep/main.c b/drivers/acpi/sleep/main.c index c79edcb..2cbb9aa 100644 --- a/drivers/acpi/sleep/main.c +++ b/drivers/acpi/sleep/main.c @@ -24,7 +24,9 @@ u8 sleep_states[ACPI_S_STATE_COUNT]; +#ifdef CONFIG_PM_SLEEP static u32 acpi_target_sleep_state = ACPI_STATE_S0; +#endif int acpi_sleep_prepare(u32 acpi_state) { @@ -299,6 +301,7 @@ int acpi_suspend(u32 acpi_state) return -EINVAL; } +#ifdef CONFIG_PM_SLEEP /** * acpi_pm_device_sleep_state - return preferred power state of ACPI device * in the system sleep state given by %acpi_target_sleep_state @@ -373,6 +376,7 @@ int acpi_pm_device_sleep_state(struct device *dev, int wake, int *d_min_p) *d_min_p = d_min; return d_max; } +#endif static void acpi_power_off_prepare(void) { diff --git a/include/acpi/acpi_drivers.h b/include/acpi/acpi_drivers.h index 202acb9..f85f77a 100644 --- a/include/acpi/acpi_drivers.h +++ b/include/acpi/acpi_drivers.h @@ -147,10 +147,6 @@ static inline void unregister_hotplug_dock_device(acpi_handle handle) /*-------------------------------------------------------------------------- Suspend/Resume -------------------------------------------------------------------------- */ -#ifdef CONFIG_ACPI_SLEEP extern int acpi_sleep_init(void); -#else -static inline int acpi_sleep_init(void) { return 0; } -#endif #endif /*__ACPI_DRIVERS_H__*/ ^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 14:45 ` Alexey Starikovskiy @ 2007-09-25 15:54 ` Rafael J. Wysocki 2007-09-25 16:23 ` Andrew Morton 1 sibling, 0 replies; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 15:54 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, Andrew Morton, LKML, Len Brown, Frans Pop, linux-acpi On Tuesday, 25 September 2007 16:45, Alexey Starikovskiy wrote: > Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 16:19, Alexey Starikovskiy wrote: > >> Rafael J. Wysocki wrote: > >>> On Tuesday, 25 September 2007 15:15, Alexey Starikovskiy wrote: > >>>> Rafael J. Wysocki wrote: > >>>>> On Tuesday, 25 September 2007 14:53, Alexey Starikovskiy wrote: > >>>>>> Rafael J. Wysocki wrote: > >>>>>>> On Tuesday, 25 September 2007 14:05, Alexey Starikovskiy wrote: > >>>>>>>> Rafael J. Wysocki wrote: > >>>>>>>>> On Tuesday, 25 September 2007 13:45, Rafael J. Wysocki wrote: > >>>>>>>>>> On Tuesday, 25 September 2007 11:58, Damien Wyart wrote: > >>>>>>>>>>>>> No, I do not have CONFIG_ACPI_SLEEP set, > >>>>>>>>>>>>> because I do not have CONFIG_PM_SLEEP set, > >>>>>>>>>>>>> because I do not want SUSPEND and/or HIBERNATION. > >>>>>>>>>>>> Same answer from my side: I do not have CONFIG_ACPI_SLEEP for the same > >>>>>>>>>>>> reason (and this worked fine without them in rc7). I do not think > >>>>>>>>>>>> these settings should have changed between rc7 and rc8. > >>>>>>>>>> Well, we haven't changed much. > >>>>>>>>>> > >>>>>>>>>>> Also, another test I just did: on another computer, rc8 is fine > >>>>>>>>>>> regarding ACPI power off, even if CONFIG_ACPI_SLEEP is not set. I can > >>>>>>>>>>> provide config if needed. > >>>>>>>>>> On the box that fails to power off, can you please test -rc8 with these two > >>>>>>>>>> commits reverted: > >>>>>>>>>> > >>>>>>>>>> commit 5a50fe709d527f31169263e36601dd83446d5744 > >>>>>>>>>> ACPI: suspend: consolidate handling of Sx states addendum > >>>>>>>>>> > >>>>>>>>>> commit f216cc3748a3a22c2b99390fddcdafa0583791a2 > >>>>>>>>>> ACPI: suspend: consolidate handling of Sx states. > >>>>>>>>>> > >>>>>>>>>> and see if it works? > >>>>>>>>> If it does, please test the patch from this message > >>>>>>>>> > >>>>>>>>> http://marc.info/?l=linux-kernel&m=119052978117735&w=4 > >>>>>>>>> > >>>>>>>>> on top of vanilla 2.6.23-rc8. > >>>>>>>> You will need one more patch on top of just mentioned one. > >>>>>>> Hm, why did you put acpi_target_sleep_state under CONFIG_SUSPEND? > >>>>>>> > >>>>>>> CONFIG_HIBERNATION needs acpi_target_sleep_state too. > >>>>>> Agree, attaching updated patch. > >>>>> Well, please use "ifdef CONFIG_PM_SLEEP" instead of > >>>>> "if defined(CONFIG_SUSPEND)||defined(CONFIG_HIBERNATION)", > >>>>> as you did with the second block. > >>>> I was thinking about that, but it seem to be less clear... > >>>> We need this variable only for suspend or hibernation, nothing else. > >>>> with pm_sleep it is not visible at all. > >>>> > >>>> Thoughts? > >>> Well, PM_SLEEP is defined as (SUSPEND || HIBERNATION), please have a look > >>> at kernel/power/Kconfig, and it was introduced exactly for the conditions like > >>> this. > >> I've seen this then I wrote the patch :) See my point, it is not clear, > >> that PM_SLEEP is equivalent to SUSPEND || HIBERNATION, one needs to > >> grep Kconfig files to find that -- it means that code becomes less readable, > >> and I would like to avoid that. > > > > I see your point. Still, you are using PM_SLEEP in the same file, so someone > > reading the code for the first time will have to find out what it is anyway. > In the second place it depends on header file using PM_SLEEP, so it makes sense. > > > > OTOH, the only function of PM_SLEEP is to be a replacement for > > (SUSPEND || HIBERNATION). It has no other meaning whatsoever. > > > > [Well, sorry, I couldn't invent a better name.] > > > >>> IOW, if we want something to be used for anything else than suspend or > >>> hibernation, it shouldn't be defined under PM_SLEEP. > >> Agree, but we should distinguish there it is better to use PM_SLEEP, > >> and there it is better to use (SUSPEND || HIBERNATION) just to be more expressive... > > > > Well, since PM_SLEEP is used as (SUSPEND || HIBERNATION) everywhere else, > > I think that it would actually be confusing not to use it here. :-) > Ok, patch is here. Acked-by: Rafael J. Wysocki <rjw@sisk.pl> and thanks for fixing this. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 14:45 ` Alexey Starikovskiy 2007-09-25 15:54 ` Rafael J. Wysocki @ 2007-09-25 16:23 ` Andrew Morton 2007-09-25 16:25 ` Alexey Starikovskiy 1 sibling, 1 reply; 32+ messages in thread From: Andrew Morton @ 2007-09-25 16:23 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Rafael J. Wysocki, Alexey Starikovskiy, Damien Wyart, Torsten Kaiser, LKML, Len Brown, Frans Pop, linux-acpi On Tue, 25 Sep 2007 18:45:15 +0400 Alexey Starikovskiy <astarikovskiy@suse.de> wrote: > [fix-ACPI_SLEEP_states.patch text/x-patch (2.0KB)] > ACPI: suspend: fix ACPI_SLEEP states > > From: Alexey Starikovskiy <astarikovskiy@suse.de> > > Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de> > --- > > drivers/acpi/sleep/Makefile | 2 +- > drivers/acpi/sleep/main.c | 4 ++++ > include/acpi/acpi_drivers.h | 4 ---- > 3 files changed, 5 insertions(+), 5 deletions(-) I get a reject applying this to current mainline. Easy enough to fix it, but I worry that the fix might be incorrect when applied to some tree other than that which you were working on. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 16:23 ` Andrew Morton @ 2007-09-25 16:25 ` Alexey Starikovskiy 0 siblings, 0 replies; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 16:25 UTC (permalink / raw) To: Andrew Morton Cc: Alexey Starikovskiy, Rafael J. Wysocki, Damien Wyart, Torsten Kaiser, LKML, Len Brown, Frans Pop, linux-acpi Andrew, There are 2 patches, this is the second. Above, Rafael gave link to first. Here it is again: http://marc.info/?l=linux-kernel&m=119052978117735&w=4 Sorry for confusion, Alex. Andrew Morton wrote: > On Tue, 25 Sep 2007 18:45:15 +0400 Alexey Starikovskiy <astarikovskiy@suse.de> wrote: > >> [fix-ACPI_SLEEP_states.patch text/x-patch (2.0KB)] >> ACPI: suspend: fix ACPI_SLEEP states >> >> From: Alexey Starikovskiy <astarikovskiy@suse.de> >> >> Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de> >> --- >> >> drivers/acpi/sleep/Makefile | 2 +- >> drivers/acpi/sleep/main.c | 4 ++++ >> include/acpi/acpi_drivers.h | 4 ---- >> 3 files changed, 5 insertions(+), 5 deletions(-) > > I get a reject applying this to current mainline. Easy enough to fix it, > but I worry that the fix might be incorrect when applied to some tree other > than that which you were working on. > > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 9:08 ` Torsten Kaiser 2007-09-25 9:27 ` Damien Wyart @ 2007-09-25 11:25 ` Alexey Starikovskiy 2007-09-25 16:30 ` Torsten Kaiser 1 sibling, 1 reply; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 11:25 UTC (permalink / raw) To: Torsten Kaiser Cc: Alexey Starikovskiy, Damien Wyart, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi Torsten Kaiser wrote: > On 9/25/07, Alexey Starikovskiy <astarikovskiy@suse.de> wrote: >> Do you have CONFIG_ACPI_SLEEP enabled in your .config? > > I'm answering that too, because I suspect that my "2.6.23-rc7-mm1 does > not power off"-error might have the same cause. > > No, I do not have CONFIG_ACPI_SLEEP set, > because I do not have CONFIG_PM_SLEEP set, > because I do not want SUSPEND and/or HIBERNATION. This is not the reason. SUSPEND is controlled with CONFIG_SUSPEND and HIBERNATION is controlled with CONFIG_HIBERNATION. But if you want S5 ACPI sleep state you might want to enable ACPI_SLEEP... > > .config from 2.6.23-rc7-mm1 attached. > > Torsten > ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 11:25 ` Alexey Starikovskiy @ 2007-09-25 16:30 ` Torsten Kaiser 2007-09-25 16:31 ` Alexey Starikovskiy 2007-09-25 16:34 ` Alexey Starikovskiy 0 siblings, 2 replies; 32+ messages in thread From: Torsten Kaiser @ 2007-09-25 16:30 UTC (permalink / raw) To: Alexey Starikovskiy Cc: Alexey Starikovskiy, Damien Wyart, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi On 9/25/07, Alexey Starikovskiy <aystarik@gmail.com> wrote: > Torsten Kaiser wrote: > > No, I do not have CONFIG_ACPI_SLEEP set, > > because I do not have CONFIG_PM_SLEEP set, > > because I do not want SUSPEND and/or HIBERNATION. > This is not the reason. SUSPEND is controlled with CONFIG_SUSPEND and > HIBERNATION is controlled with CONFIG_HIBERNATION. > But if you want S5 ACPI sleep state you might want to enable ACPI_SLEEP... What I meant with SUSPEND and/or HIBERNATION was CONFIG_SUSPEND / CONFIG_HIBERNATION. And the relations where from Kconfig: from drivers/acpi/Kconfig: config ACPI_SLEEP bool depends on PM_SLEEP default y -> no PM_SLEEP means no ACPI_SLEEP from kernel/power/Kconfig: config PM_SLEEP bool depends on SUSPEND || HIBERNATION default y -> No SUSPEND and/or HIBERNATION means no PM_SLEEP And if I select SUSPEND and/or HIBERNATION I will not only build this feature into the kernel, but also HOTPLUG_CPU and I want to avoid that. It's exactly as Linus said in his mail: Not everybody wants SUSPEND... I should have formulated that better in my mail, but that was what I wanted to say. Back to debugging this: http://marc.info/?l=linux-acpi&m=119052970904643&w=4 fails to apply against 2.6.23-rc7-mm1, but moving that function by hand was not to difficult. ;) (With only the second patch I got a link error...) http://marc.info/?l=linux-acpi&m=119073173625910&w=4 applied, and a test showed that my system now powers off again. Torsten ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 16:30 ` Torsten Kaiser @ 2007-09-25 16:31 ` Alexey Starikovskiy 2007-09-25 16:34 ` Alexey Starikovskiy 1 sibling, 0 replies; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 16:31 UTC (permalink / raw) To: Torsten Kaiser Cc: Alexey Starikovskiy, Damien Wyart, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi Torsten Kaiser wrote: > On 9/25/07, Alexey Starikovskiy <aystarik@gmail.com> wrote: >> Torsten Kaiser wrote: >>> No, I do not have CONFIG_ACPI_SLEEP set, >>> because I do not have CONFIG_PM_SLEEP set, >>> because I do not want SUSPEND and/or HIBERNATION. >> This is not the reason. SUSPEND is controlled with CONFIG_SUSPEND and >> HIBERNATION is controlled with CONFIG_HIBERNATION. >> But if you want S5 ACPI sleep state you might want to enable ACPI_SLEEP... > > What I meant with SUSPEND and/or HIBERNATION was CONFIG_SUSPEND / > CONFIG_HIBERNATION. > > And the relations where from Kconfig: > from drivers/acpi/Kconfig: > config ACPI_SLEEP > bool > depends on PM_SLEEP > default y > > -> no PM_SLEEP means no ACPI_SLEEP > > from kernel/power/Kconfig: > config PM_SLEEP > bool > depends on SUSPEND || HIBERNATION > default y > > -> No SUSPEND and/or HIBERNATION means no PM_SLEEP > > And if I select SUSPEND and/or HIBERNATION I will not only build this > feature into the kernel, but also HOTPLUG_CPU and I want to avoid > that. > > It's exactly as Linus said in his mail: Not everybody wants SUSPEND... > > I should have formulated that better in my mail, but that was what I > wanted to say. > > > Back to debugging this: > http://marc.info/?l=linux-acpi&m=119052970904643&w=4 > fails to apply against 2.6.23-rc7-mm1, but moving that function by > hand was not to difficult. ;) > (With only the second patch I got a link error...) > > http://marc.info/?l=linux-acpi&m=119073173625910&w=4 > applied, and a test showed that my system now powers off again. > > Torsten Understood, patches are available, please test. Regards, Alex. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 16:30 ` Torsten Kaiser 2007-09-25 16:31 ` Alexey Starikovskiy @ 2007-09-25 16:34 ` Alexey Starikovskiy 1 sibling, 0 replies; 32+ messages in thread From: Alexey Starikovskiy @ 2007-09-25 16:34 UTC (permalink / raw) To: Torsten Kaiser Cc: Alexey Starikovskiy, Damien Wyart, Andrew Morton, LKML, Len Brown, Frans Pop, Rafael J. Wysocki, linux-acpi Torsten Kaiser wrote: > Back to debugging this: > http://marc.info/?l=linux-acpi&m=119052970904643&w=4 > fails to apply against 2.6.23-rc7-mm1, but moving that function by > hand was not to difficult. ;) > (With only the second patch I got a link error...) > > http://marc.info/?l=linux-acpi&m=119073173625910&w=4 > applied, and a test showed that my system now powers off again. Good, thanks, Alex. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 7:33 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Andrew Morton 2007-09-25 8:36 ` Alexey Starikovskiy @ 2007-09-25 15:40 ` Linus Torvalds 2007-09-25 16:00 ` Rafael J. Wysocki 2007-09-26 14:59 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Tim Post 1 sibling, 2 replies; 32+ messages in thread From: Linus Torvalds @ 2007-09-25 15:40 UTC (permalink / raw) To: Andrew Morton Cc: Damien Wyart, LKML, Len Brown, Frans Pop, Alexey Starikovskiy, Rafael J. Wysocki, linux-acpi On Tue, 25 Sep 2007 08:51:09 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > > Hello, > > After testing rc8, I noticed that I couldn't power off the computer > directly, it only got halted and I had to press the power button > manually. Just before displaying "System halted", the following message > is displayed: > > ACPI : PCI interrupt for device 0000:02:08.0 disabled > > I had to first revert 5a50fe709d527f31169263e36601dd83446d5744 then > f216cc3748a3a22c2b99390fddcdafa0583791a2 (handling of Sx states) to > recover previous behaviour. Hmm. Those things *do* seem to be suspicious. For example, those commits seem to move code that used to be inside CONFIG_PM (which pretty much *everybody* has) to be inside CONFIG_ACPI_SLEEP (which is a totally different thing, and depends on whether the user asked for suspend support or not! Damien - does it work if you ask for SUSPEND or HIBERNATION support? Len - why are you guys moving stuff into CONFIG_PM_SLEEP? I know you seem to think that absolutely *everybody* should always support suspend and hibernation, but the fact is, not everybody does. And it's a totally separate thing for normal ACPI CPU runstate support that people have used to manage a *running* CPU (and shutting it down). Linus ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 15:40 ` Linus Torvalds @ 2007-09-25 16:00 ` Rafael J. Wysocki 2007-09-25 21:44 ` ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) Frans Pop 2007-09-26 14:59 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Tim Post 1 sibling, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 16:00 UTC (permalink / raw) To: Linus Torvalds Cc: Andrew Morton, Damien Wyart, LKML, Len Brown, Frans Pop, Alexey Starikovskiy, linux-acpi On Tuesday, 25 September 2007 17:40, Linus Torvalds wrote: > > On Tue, 25 Sep 2007 08:51:09 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > > > > Hello, > > > > After testing rc8, I noticed that I couldn't power off the computer > > directly, it only got halted and I had to press the power button > > manually. Just before displaying "System halted", the following message > > is displayed: > > > > ACPI : PCI interrupt for device 0000:02:08.0 disabled > > > > I had to first revert 5a50fe709d527f31169263e36601dd83446d5744 then > > f216cc3748a3a22c2b99390fddcdafa0583791a2 (handling of Sx states) to > > recover previous behaviour. > > Hmm. Those things *do* seem to be suspicious. > > For example, those commits seem to move code that used to be inside > CONFIG_PM (which pretty much *everybody* has) to be inside > CONFIG_ACPI_SLEEP (which is a totally different thing, and depends on > whether the user asked for suspend support or not! > > Damien - does it work if you ask for SUSPEND or HIBERNATION support? > > Len - why are you guys moving stuff into CONFIG_PM_SLEEP? I know you seem > to think that absolutely *everybody* should always support suspend and > hibernation, but the fact is, not everybody does. And it's a totally > separate thing for normal ACPI CPU runstate support that people have used > to manage a *running* CPU (and shutting it down). This was a mistake and fixes have already been posted: http://marc.info/?l=linux-acpi&m=119052970904643&w=4 http://marc.info/?l=linux-acpi&m=119073173625910&w=4 Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) 2007-09-25 16:00 ` Rafael J. Wysocki @ 2007-09-25 21:44 ` Frans Pop 2007-09-25 22:18 ` Rafael J. Wysocki 0 siblings, 1 reply; 32+ messages in thread From: Frans Pop @ 2007-09-25 21:44 UTC (permalink / raw) To: LKML Cc: Rafael J. Wysocki, Linus Torvalds, Andrew Morton, Damien Wyart, Len Brown, Alexey Starikovskiy, linux-acpi On Tuesday 25 September 2007, Rafael J. Wysocki wrote: > On Tuesday, 25 September 2007 17:40, Linus Torvalds wrote: > > Len - why are you guys moving stuff into CONFIG_PM_SLEEP? I know you > > seem to think that absolutely *everybody* should always support suspend > > and hibernation, but the fact is, not everybody does. And it's a > > totally separate thing for normal ACPI CPU runstate support that people > > have used to manage a *running* CPU (and shutting it down). > > This was a mistake and fixes have already been posted: > > http://marc.info/?l=linux-acpi&m=119052970904643&w=4 > http://marc.info/?l=linux-acpi&m=119073173625910&w=4 As this whole "separate suspend and hibernate" change seems to have been trickier than expected, I have done some additional testing using 2.6.23-rc8 plus both patches referred to above. I compiled kernels (i386) for my laptop (Toshiba Satellite A40) with: A) PM + SUSPEND + HIBERNATION + ACPI B) PM + SUSPEND + ACPI C) PM + HIBERNATION + ACPI D) PM + ACPI E) PM + SUSPEND + HIBERNATION but _without_ ACPI F) without PM In all cases CONFIG_APM was not set; all compiled without errors. With all I have have booted, tried to suspend (close lid, which runs sleep script, which does 'echo mem >/sys/power/state'), tried to hibernate ('echo disk >/sys/power/state') and powered off (all from KDE sessions). RESULTS boot s2ram s2disk off A) OK OK OK OK B) OK OK N/A OK C) OK OK 1) OK OK D) OK 2) OK 1) N/A OK E) OK 3) N/A 4) ??? 5) Only halted 6) F) OK N/A N/A Only halted 6) Comments: 1) sleep script ran, but laptop stayed on 2) dmesg lists S0,S5 supported /proc/acpi/{sleep,wakeup} do not exist (is that correct?) 3) /proc/acpi/{sleep,wakeup} do not exist; /sys/power/state only has 'mem' so SUSPEND seems missing even though compiled in 4) sleep script did not even run (as expected) 5) System did suspend, but power stayed on with on console: Shutdown: hda \ Power down. \ Shutdown: hda \ hda: lost interrupt (2x) \ psmouse.c: Failed to deactivate mouse on isa0060/serio1 System powered off manually and resumed correctly after that 6) System halted correctly, but did not power off automatically The results for E and F are possibly correct as basically the config (without ACPI) was broken for this laptop. In fact, I was somewhat surprised how well it behaved without ACPI. I suspect that whether a system powers off without ACPI or not can depend on the system? I have dmesg after boot and some other info available for all kernels if anybody is interested. If any additional tests are wanted, please ask. Cheers, FJP ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) 2007-09-25 21:44 ` ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) Frans Pop @ 2007-09-25 22:18 ` Rafael J. Wysocki 2007-09-25 22:28 ` Frans Pop 0 siblings, 1 reply; 32+ messages in thread From: Rafael J. Wysocki @ 2007-09-25 22:18 UTC (permalink / raw) To: Frans Pop Cc: LKML, Linus Torvalds, Andrew Morton, Damien Wyart, Len Brown, Alexey Starikovskiy, linux-acpi On Tuesday, 25 September 2007 23:44, Frans Pop wrote: > On Tuesday 25 September 2007, Rafael J. Wysocki wrote: > > On Tuesday, 25 September 2007 17:40, Linus Torvalds wrote: > > > Len - why are you guys moving stuff into CONFIG_PM_SLEEP? I know you > > > seem to think that absolutely *everybody* should always support suspend > > > and hibernation, but the fact is, not everybody does. And it's a > > > totally separate thing for normal ACPI CPU runstate support that people > > > have used to manage a *running* CPU (and shutting it down). > > > > This was a mistake and fixes have already been posted: > > > > http://marc.info/?l=linux-acpi&m=119052970904643&w=4 > > http://marc.info/?l=linux-acpi&m=119073173625910&w=4 > > As this whole "separate suspend and hibernate" change seems to have been > trickier than expected, I have done some additional testing using > 2.6.23-rc8 plus both patches referred to above. > > I compiled kernels (i386) for my laptop (Toshiba Satellite A40) with: > A) PM + SUSPEND + HIBERNATION + ACPI > B) PM + SUSPEND + ACPI > C) PM + HIBERNATION + ACPI > D) PM + ACPI > E) PM + SUSPEND + HIBERNATION but _without_ ACPI > F) without PM Thanks a lot for testing this! > In all cases CONFIG_APM was not set; all compiled without errors. > > With all I have have booted, tried to suspend (close lid, which runs sleep > script, which does 'echo mem >/sys/power/state'), tried to hibernate ('echo > disk >/sys/power/state') and powered off (all from KDE sessions). > > RESULTS > boot s2ram s2disk off > A) OK OK OK OK > B) OK OK N/A OK > C) OK OK 1) OK OK > D) OK 2) OK 1) N/A OK > E) OK 3) N/A 4) ??? 5) Only halted 6) > F) OK N/A N/A Only halted 6) > > Comments: > 1) sleep script ran, but laptop stayed on > 2) dmesg lists S0,S5 supported > /proc/acpi/{sleep,wakeup} do not exist (is that correct?) > 3) /proc/acpi/{sleep,wakeup} do not exist; /sys/power/state only has 'mem' Hm, this should be 'disk' ... > so SUSPEND seems missing even though compiled in ... but it so follows from this comment. Can you clarify, please? > 4) sleep script did not even run (as expected) > 5) System did suspend, but power stayed on with on console: > Shutdown: hda \ Power down. \ Shutdown: hda \ hda: lost interrupt (2x) > \ psmouse.c: Failed to deactivate mouse on isa0060/serio1 > System powered off manually and resumed correctly after that > 6) System halted correctly, but did not power off automatically > > The results for E and F are possibly correct as basically the config > (without ACPI) was broken for this laptop. In fact, I was somewhat > surprised how well it behaved without ACPI. > > I suspect that whether a system powers off without ACPI or not can depend on > the system? > > I have dmesg after boot and some other info available for all kernels if > anybody is interested. If any additional tests are wanted, please ask. I think that your results reflect the code pretty well, ie. no big surprises. On ACPI machines suspend doesn't actually work without ACPI and that's why 'mem' is missing from kernel/power/state with E). Hibernation theoretically works without ACPI, but the box cannot be powered off due to the lack of support for that. For the same reason, the system doesn't power off with E), F). The errors from device drivers in the last phase of hibernation with E) may be related to some confusion cause by the lack of ACPI methods expected to be present. Greetings, Rafael ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) 2007-09-25 22:18 ` Rafael J. Wysocki @ 2007-09-25 22:28 ` Frans Pop 0 siblings, 0 replies; 32+ messages in thread From: Frans Pop @ 2007-09-25 22:28 UTC (permalink / raw) To: LKML Cc: Rafael J. Wysocki, Linus Torvalds, Andrew Morton, Damien Wyart, Len Brown, Alexey Starikovskiy, linux-acpi On Wednesday 26 September 2007, Rafael J. Wysocki wrote: > > I compiled kernels (i386) for my laptop (Toshiba Satellite A40) with: > > A) PM + SUSPEND + HIBERNATION + ACPI > > B) PM + SUSPEND + ACPI > > C) PM + HIBERNATION + ACPI > > D) PM + ACPI > > E) PM + SUSPEND + HIBERNATION but _without_ ACPI > > F) without PM > > Thanks a lot for testing this! You're welcome. Until 2.6.20 or .21 s2ram never worked for me and even then sound did not work after resume. Now it seems to be supported perfectly, so my thanks to all of you! Pity this laptop is slowly nearing end of life (3.5 years old, though still performing fine). > > RESULTS > > boot s2ram s2disk off > > A) OK OK OK OK > > B) OK OK N/A OK > > C) OK OK 1) OK OK > > D) OK 2) OK 1) N/A OK > > E) OK 3) N/A 4) ??? 5) Only halted 6) > > F) OK N/A N/A Only halted 6) > > > > Comments: > > 1) sleep script ran, but laptop stayed on > > 2) dmesg lists S0,S5 supported > > /proc/acpi/{sleep,wakeup} do not exist (is that correct?) > > 3) /proc/acpi/{sleep,wakeup} do not exist; /sys/power/state only has > > 'mem' > > Hm, this should be 'disk' ... > > > so SUSPEND seems missing even though compiled in > > ... but it so follows from this comment. Can you clarify, please? Yes, my mistake. For E) /sys/power/state only has "disk", not "mem". > I think that your results reflect the code pretty well, ie. no big > surprises. Great. That was what I was thinking. Thanks for confirming. ^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: ACPI power off regression in 2.6.23-rc8 (NOT in rc7) 2007-09-25 15:40 ` Linus Torvalds 2007-09-25 16:00 ` Rafael J. Wysocki @ 2007-09-26 14:59 ` Tim Post 1 sibling, 0 replies; 32+ messages in thread From: Tim Post @ 2007-09-26 14:59 UTC (permalink / raw) To: Linus Torvalds Cc: Andrew Morton, Damien Wyart, LKML, Len Brown, Frans Pop, Alexey Starikovskiy, Rafael J. Wysocki, linux-acpi Bah, its too damn stable. Break it and do it again. >From 2.6.20.3 : Boot time cut in half. My PC no longer 'wakes up' angrily. My wife does that, I'm going to start sleeping with the P4, its more agreeable now. P4 HT with generic Intel chipset. What fun is this when nothing breaks? Thank you all :) On Tue, 2007-09-25 at 08:40 -0700, Linus Torvalds wrote: > > On Tue, 25 Sep 2007 08:51:09 +0200 Damien Wyart <damien.wyart@free.fr> wrote: > > > > Hello, > > > > After testing rc8, I noticed that I couldn't power off the computer > > directly, it only got halted and I had to press the power button > > manually. Just before displaying "System halted", the following message > > is displayed: > > > > ACPI : PCI interrupt for device 0000:02:08.0 disabled > > > > I had to first revert 5a50fe709d527f31169263e36601dd83446d5744 then > > f216cc3748a3a22c2b99390fddcdafa0583791a2 (handling of Sx states) to > > recover previous behaviour. > > Hmm. Those things *do* seem to be suspicious. > > For example, those commits seem to move code that used to be inside > CONFIG_PM (which pretty much *everybody* has) to be inside > CONFIG_ACPI_SLEEP (which is a totally different thing, and depends on > whether the user asked for suspend support or not! > > Damien - does it work if you ask for SUSPEND or HIBERNATION support? > > Len - why are you guys moving stuff into CONFIG_PM_SLEEP? I know you seem > to think that absolutely *everybody* should always support suspend and > hibernation, but the fact is, not everybody does. And it's a totally > separate thing for normal ACPI CPU runstate support that people have used > to manage a *running* CPU (and shutting it down). > > Linus > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 32+ messages in thread
end of thread, other threads:[~2007-09-26 15:42 UTC | newest]
Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20070925065109.GA3080@localhost.localdomain>
2007-09-25 7:33 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Andrew Morton
2007-09-25 8:36 ` Alexey Starikovskiy
2007-09-25 9:08 ` Torsten Kaiser
2007-09-25 9:27 ` Damien Wyart
2007-09-25 9:58 ` Damien Wyart
2007-09-25 11:45 ` Rafael J. Wysocki
2007-09-25 12:02 ` Damien Wyart
2007-09-25 15:05 ` Damien Wyart
2007-09-26 1:39 ` Mike Houston
2007-09-25 12:05 ` Rafael J. Wysocki
2007-09-25 12:05 ` Alexey Starikovskiy
2007-09-25 12:39 ` Rafael J. Wysocki
2007-09-25 12:53 ` Alexey Starikovskiy
2007-09-25 13:25 ` Rafael J. Wysocki
2007-09-25 13:15 ` Alexey Starikovskiy
2007-09-25 14:18 ` Rafael J. Wysocki
2007-09-25 14:19 ` Alexey Starikovskiy
2007-09-25 14:52 ` Rafael J. Wysocki
2007-09-25 14:45 ` Alexey Starikovskiy
2007-09-25 15:54 ` Rafael J. Wysocki
2007-09-25 16:23 ` Andrew Morton
2007-09-25 16:25 ` Alexey Starikovskiy
2007-09-25 11:25 ` Alexey Starikovskiy
2007-09-25 16:30 ` Torsten Kaiser
2007-09-25 16:31 ` Alexey Starikovskiy
2007-09-25 16:34 ` Alexey Starikovskiy
2007-09-25 15:40 ` Linus Torvalds
2007-09-25 16:00 ` Rafael J. Wysocki
2007-09-25 21:44 ` ACPI suspend/hibernate tests (was: ACPI power off regression in 2.6.23-rc8) Frans Pop
2007-09-25 22:18 ` Rafael J. Wysocki
2007-09-25 22:28 ` Frans Pop
2007-09-26 14:59 ` ACPI power off regression in 2.6.23-rc8 (NOT in rc7) Tim Post
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox