Re: PS/2 Keyboard is dead after resume.
On 7/16/05, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, > do you? Nope :). > > serio: i8042 AUX port at 0x60,0x64 irq 12 > > serio: i8042 KBD port at 0x60,0x64 irq 1 > > You did not select PNP support (but as far as keyboard controller settings > go we don't trust it anyway on i386). I've never ever found it to work, so I usually disable it. > And here you have a bunch of hardware gets assigned to IRQ 12... > Hmm, I tought ACPI would try not use 12 unless it is absolutely > necessary. What appens if you use "pci=routeirq" boot option? The keyboard was still dead after resume. > You can try working around this with "i8042.noaux" kernel boot option, > but we should probably teach i8042 driver to not touch AUX port on resume > if it was disabled. This worked. Strangely enough, after googling for i8042 and suspend last night, I found the 2.6.12 kernel boot options file. I tried i8042.nomux, i8042.direct, and some others, but nothing worked. Just for fun, I tried booting without any kernel boot options (just the suspend2 option) and with a PS/2 mouse plugged in. On suspend, the keyboard worked. Maybe this could/should be added to the suspend2 code as well? Whatever. It works for now. If you'd like any more information, just let me know. Thanks! -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
[Suspend2 was removed from CC as it appears to be subscribers-only list.] On Friday 15 July 2005 06:43, Andrew Haninger wrote: > On 7/15/05, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > > Could you try doing: > > > > echo 1 > /sys/modules/i8042/parameters/debug > > > > before suspending and the post your dmesg, please? Maybe we see something > > there. > Here you go: > > 12) *0, disabled. Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, do you? ... > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 You did not select PNP support (but as far as keyboard controller settings go we don't trust it anyway on i386). ... > ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 > PCI: setting IRQ 12 as level-triggered > ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKA] -> GSI 12 (level, > low) -> IRQ 12 > PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 > VP_IDE: chipset revision 6 ... > USB Universal Host Controller Interface driver v2.2 > ACPI: PCI Interrupt :00:10.0[A] -> Link [LNKA] -> GSI 12 (level, > low) -> IRQ 12 > uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 > Controller > uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 > uhci_hcd :00:10.0: irq 12, io base 0xd000 > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 2 ports detected > ACPI: PCI Interrupt :00:10.1[A] -> Link [LNKA] -> GSI 12 (level, > low) -> IRQ 12 > uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 > Controller (#2) > uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 > uhci_hcd :00:10.1: irq 12, io base 0xd400 And here you have a bunch of hardware gets assigned to IRQ 12... Hmm, I tought ACPI would try not use 12 unless it is absolutely necessary. What appens if you use "pci=routeirq" boot option? > drivers/input/serio/i8042.c: 60 -> i8042 (command) [154857] > drivers/input/serio/i8042.c: 65 -> i8042 (parameter) [154857] > drivers/input/serio/i8042.c: 60 -> i8042 (command) [154857] > drivers/input/serio/i8042.c: 65 -> i8042 (parameter) [154857] > drivers/input/serio/i8042.c: 60 -> i8042 (command) [154857] > drivers/input/serio/i8042.c: 47 -> i8042 (parameter) [154857] > drivers/input/serio/i8042.c: f2 -> i8042 (kbd-data) [154857] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154860] > drivers/input/serio/i8042.c: ab <- i8042 (interrupt, KBD, 1) [154861] > drivers/input/serio/i8042.c: 41 <- i8042 (interrupt, KBD, 1) [154862] > drivers/input/serio/i8042.c: ed -> i8042 (kbd-data) [154862] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154865] > drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [154865] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154867] > drivers/input/serio/i8042.c: f3 -> i8042 (kbd-data) [154867] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154870] > drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [154870] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154873] > drivers/input/serio/i8042.c: f4 -> i8042 (kbd-data) [154873] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154876] > drivers/input/serio/i8042.c: ed -> i8042 (kbd-data) [154876] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154879] > drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [154879] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [154881] Keyboard seems to be resumed just fine... > 20%...40%...60%...80%...100%...done. > drivers/input/serio/i8042.c: 60 -> i8042 (command) [155414] > drivers/input/serio/i8042.c: 47 -> i8042 (parameter) [155414] > drivers/input/serio/i8042.c: d4 -> i8042 (command) [155414] > drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [155414] > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, KBD, 1) [155417] > atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, > might be trying access hardware directly. > drivers/input/serio/i8042.c: ab <- i8042 (interrupt, KBD, 1) [155418] But when we try to talk to mouse port we ket response from the keyboard and something gets confused. You can try working around this with "i8042.noaux" kernel boot option, but we should probably teach i8042 driver to not touch AUX port on resume if it was disabled. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
[Suspend2 was removed from CC as it appears to be subscribers-only list.] On Friday 15 July 2005 06:43, Andrew Haninger wrote: On 7/15/05, Dmitry Torokhov [EMAIL PROTECTED] wrote: Could you try doing: echo 1 /sys/modules/i8042/parameters/debug before suspending and the post your dmesg, please? Maybe we see something there. Here you go: 12) *0, disabled. Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, do you? ... serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 You did not select PNP support (but as far as keyboard controller settings go we don't trust it anyway on i386). ... ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 PCI: setting IRQ 12 as level-triggered ACPI: PCI Interrupt :00:0f.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 VP_IDE: chipset revision 6 ... USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 12, io base 0xd000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 12, io base 0xd400 And here you have a bunch of hardware gets assigned to IRQ 12... Hmm, I tought ACPI would try not use 12 unless it is absolutely necessary. What appens if you use pci=routeirq boot option? drivers/input/serio/i8042.c: 60 - i8042 (command) [154857] drivers/input/serio/i8042.c: 65 - i8042 (parameter) [154857] drivers/input/serio/i8042.c: 60 - i8042 (command) [154857] drivers/input/serio/i8042.c: 65 - i8042 (parameter) [154857] drivers/input/serio/i8042.c: 60 - i8042 (command) [154857] drivers/input/serio/i8042.c: 47 - i8042 (parameter) [154857] drivers/input/serio/i8042.c: f2 - i8042 (kbd-data) [154857] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154860] drivers/input/serio/i8042.c: ab - i8042 (interrupt, KBD, 1) [154861] drivers/input/serio/i8042.c: 41 - i8042 (interrupt, KBD, 1) [154862] drivers/input/serio/i8042.c: ed - i8042 (kbd-data) [154862] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154865] drivers/input/serio/i8042.c: 00 - i8042 (kbd-data) [154865] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154867] drivers/input/serio/i8042.c: f3 - i8042 (kbd-data) [154867] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154870] drivers/input/serio/i8042.c: 00 - i8042 (kbd-data) [154870] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154873] drivers/input/serio/i8042.c: f4 - i8042 (kbd-data) [154873] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154876] drivers/input/serio/i8042.c: ed - i8042 (kbd-data) [154876] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154879] drivers/input/serio/i8042.c: 00 - i8042 (kbd-data) [154879] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [154881] Keyboard seems to be resumed just fine... 20%...40%...60%...80%...100%...done. drivers/input/serio/i8042.c: 60 - i8042 (command) [155414] drivers/input/serio/i8042.c: 47 - i8042 (parameter) [155414] drivers/input/serio/i8042.c: d4 - i8042 (command) [155414] drivers/input/serio/i8042.c: f2 - i8042 (parameter) [155414] drivers/input/serio/i8042.c: fa - i8042 (interrupt, KBD, 1) [155417] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. drivers/input/serio/i8042.c: ab - i8042 (interrupt, KBD, 1) [155418] But when we try to talk to mouse port we ket response from the keyboard and something gets confused. You can try working around this with i8042.noaux kernel boot option, but we should probably teach i8042 driver to not touch AUX port on resume if it was disabled. -- Dmitry - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On 7/16/05, Dmitry Torokhov [EMAIL PROTECTED] wrote: Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, do you? Nope :). serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 You did not select PNP support (but as far as keyboard controller settings go we don't trust it anyway on i386). I've never ever found it to work, so I usually disable it. And here you have a bunch of hardware gets assigned to IRQ 12... Hmm, I tought ACPI would try not use 12 unless it is absolutely necessary. What appens if you use pci=routeirq boot option? The keyboard was still dead after resume. You can try working around this with i8042.noaux kernel boot option, but we should probably teach i8042 driver to not touch AUX port on resume if it was disabled. This worked. Strangely enough, after googling for i8042 and suspend last night, I found the 2.6.12 kernel boot options file. I tried i8042.nomux, i8042.direct, and some others, but nothing worked. Just for fun, I tried booting without any kernel boot options (just the suspend2 option) and with a PS/2 mouse plugged in. On suspend, the keyboard worked. Maybe this could/should be added to the suspend2 code as well? Whatever. It works for now. If you'd like any more information, just let me know. Thanks! -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On 7/15/05, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > Could you try doing: > > echo 1 > /sys/modules/i8042/parameters/debug > > before suspending and the post your dmesg, please? Maybe we see something > there. Here you go: 12) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *15, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs *21) ACPI: PCI Interrupt Link [ALKC] (IRQs *22) ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Machine check exception polling timer started. audit: initializing netlink socket (disabled) audit(1121412889.356:0): initialized Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Thermal Zone [THRM] (29 C) lp: driver loaded but no devices found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A parport0: PC-style at 0x378 [PCSPP(,...)] lp0: using parport0 (polling). io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 eth0: RealTek RTL8139 at 0xc400, 00:30:1b:3d:91:ee, IRQ 10 eth0: Identified 8139 chip type 'RTL-8100B/8139D' Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 eth1: Lite-On PNIC-II rev 37 at 0001c000, 00:C0:F0:70:43:C6, IRQ 11. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot :00:0f.0 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 PCI: setting IRQ 12 as level-triggered ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci:00:0f.0 ide0: BM-DMA at 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: IBM-DTLA-307015, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: WDC WD102BA, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 29336832 sectors (15020 MB) w/1916KiB Cache, CHS=29104/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hdc: max request size: 128KiB hdc: 20028960 sectors (10254 MB) w/2048KiB Cache, CHS=19870/16/63, UDMA(66) hdc: cache flushes not supported hdc: hdc1 ACPI: PCI Interrupt :00:10.4[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 ehci_hcd :00:10.4: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.4: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.4: irq 10, io mem 0xee043000 ehci_hcd :00:10.4: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 12, io base 0xd000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 12, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 11, io base 0xd800 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports
Re: PS/2 Keyboard is dead after resume.
On 7/15/05, Dmitry Torokhov [EMAIL PROTECTED] wrote: Could you try doing: echo 1 /sys/modules/i8042/parameters/debug before suspending and the post your dmesg, please? Maybe we see something there. Here you go: 12) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *15, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs *21) ACPI: PCI Interrupt Link [ALKC] (IRQs *22) ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report Machine check exception polling timer started. audit: initializing netlink socket (disabled) audit(1121412889.356:0): initialized Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Thermal Zone [THRM] (29 C) lp: driver loaded but no devices found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A parport0: PC-style at 0x378 [PCSPP(,...)] lp0: using parport0 (polling). io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:0b.0[A] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 eth0: RealTek RTL8139 at 0xc400, 00:30:1b:3d:91:ee, IRQ 10 eth0: Identified 8139 chip type 'RTL-8100B/8139D' Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :00:0a.0[A] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 eth1: Lite-On PNIC-II rev 37 at 0001c000, 00:C0:F0:70:43:C6, IRQ 11. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot :00:0f.0 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 PCI: setting IRQ 12 as level-triggered ACPI: PCI Interrupt :00:0f.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci:00:0f.0 ide0: BM-DMA at 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: IBM-DTLA-307015, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: WDC WD102BA, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 29336832 sectors (15020 MB) w/1916KiB Cache, CHS=29104/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hdc: max request size: 128KiB hdc: 20028960 sectors (10254 MB) w/2048KiB Cache, CHS=19870/16/63, UDMA(66) hdc: cache flushes not supported hdc: hdc1 ACPI: PCI Interrupt :00:10.4[C] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 ehci_hcd :00:10.4: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.4: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.4: irq 10, io mem 0xee043000 ehci_hcd :00:10.4: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 12, io base 0xd000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 12, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[B] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 11, io base 0xd800 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ACPI: PCI Interrupt
Re: PS/2 Keyboard is dead after resume.
On Thursday 14 July 2005 21:35, Andrew Haninger wrote: > Hello. > > I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 > with the hibernate-1.10 script. My machine is a Shuttle SK43G which > has a VIA KM400 chipset with an Athlon XP CPU. > > Suspension seems to work well. However, when I resume, the keyboard is > dead and there is a warning in dmesg before and after suspension: > > atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, > might be trying access hardware directly. Could you try doing: echo 1 > /sys/modules/i8042/parameters/debug before suspending and the post your dmesg, please? Maybe we see something there. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PS/2 Keyboard is dead after resume.
Hello. I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 with the hibernate-1.10 script. My machine is a Shuttle SK43G which has a VIA KM400 chipset with an Athlon XP CPU. Suspension seems to work well. However, when I resume, the keyboard is dead and there is a warning in dmesg before and after suspension: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Please include the following information in bug reports: - SUSPEND core : 2.1.9.9 - Kernel Version : 2.6.12.2 - Compiler vers. : 3.3 - Attempt number : 1 - Pageset sizes : 5821 (5821 low) and 118350 (118350 low). - Parameters : 0 32 0 1 0 5 - Calculations : Image size: 124376. Ram to suspend: 2240. - Limits : 126960 pages RAM. Initial boot: 123894. - Overall expected compression percentage: 0. - Compressor lzf enabled. Compressed 508604416 bytes into 23739845 (95 percent compression). - Swapwriter active. Swap available for image: 487964 pages. - Filewriter inactive. - Preemptive kernel. - Max extents used: 4 - I/O speed: Write 251 MB/s, Read 198 MB/s. Resume block device is defe0860. Real Time Clock Driver v1.12 atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. This machine doesn't have XFree86 on it. I am presuming that this is a bug since I've used the exact same kernel+patches (with hibernate 1.09 script) on another machine without issues. I'm not sure if it's a suspension bug or if it's a kernel bug that is brought to light by the suspend2 patches. If I'm wrong and I've made a mistake, I'd love to hear it. Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PS/2 Keyboard is dead after resume.
Hello. I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 with the hibernate-1.10 script. My machine is a Shuttle SK43G which has a VIA KM400 chipset with an Athlon XP CPU. Suspension seems to work well. However, when I resume, the keyboard is dead and there is a warning in dmesg before and after suspension: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Please include the following information in bug reports: - SUSPEND core : 2.1.9.9 - Kernel Version : 2.6.12.2 - Compiler vers. : 3.3 - Attempt number : 1 - Pageset sizes : 5821 (5821 low) and 118350 (118350 low). - Parameters : 0 32 0 1 0 5 - Calculations : Image size: 124376. Ram to suspend: 2240. - Limits : 126960 pages RAM. Initial boot: 123894. - Overall expected compression percentage: 0. - Compressor lzf enabled. Compressed 508604416 bytes into 23739845 (95 percent compression). - Swapwriter active. Swap available for image: 487964 pages. - Filewriter inactive. - Preemptive kernel. - Max extents used: 4 - I/O speed: Write 251 MB/s, Read 198 MB/s. Resume block device is defe0860. Real Time Clock Driver v1.12 atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. This machine doesn't have XFree86 on it. I am presuming that this is a bug since I've used the exact same kernel+patches (with hibernate 1.09 script) on another machine without issues. I'm not sure if it's a suspension bug or if it's a kernel bug that is brought to light by the suspend2 patches. If I'm wrong and I've made a mistake, I'd love to hear it. Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On Thursday 14 July 2005 21:35, Andrew Haninger wrote: Hello. I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 with the hibernate-1.10 script. My machine is a Shuttle SK43G which has a VIA KM400 chipset with an Athlon XP CPU. Suspension seems to work well. However, when I resume, the keyboard is dead and there is a warning in dmesg before and after suspension: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Could you try doing: echo 1 /sys/modules/i8042/parameters/debug before suspending and the post your dmesg, please? Maybe we see something there. -- Dmitry - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
