i have a laptop(dell inspiron 2500) it has a touchpad so after standby the touchpad doesn't work
i will post info later
Created attachment 97734 [details] dmesg:2.6.18-gentoo kernel
kernel:2.6-18-gentoo
Created attachment 97766 [details] dmesg:2.6.17-gentoo kernel
changeds title
kenrel modules present: rt2500
Created attachment 97767 [details] .config:linux-2.6.18-gentoo
Created attachment 97768 [details] .config:linux-2.6.17-gentoo
Created attachment 97775 [details] dmesg:2.6.16-gentoo-r13
Created attachment 97780 [details] .config:2.6.16
*** Bug 148678 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > *** Bug 148678 has been marked as a duplicate of this bug. *** > yes but this bug is more clear and has more kernel dmesg and .config
(In reply to comment #12) > (In reply to comment #11) > > *** Bug 148678 has been marked as a duplicate of this bug. *** > > > > yes but this bug is more clear and has more kernel dmesg and .config > oops i didn't read the bug i thoat it was another bug
(In reply to comment #11) > *** Bug 148678 has been marked as a duplicate of this bug. *** > why...the simptoms aren't the same one is a laptop that has a mouse problem the other is a desktop that doesn't want to standby and that crash the second try to standby
Is this reproducible on the latest development kernel, currently 2.6.19-rc6?
(In reply to comment #15) > Is this reproducible on the latest development kernel, currently 2.6.19-rc6? > partialy i can standby and resume without problem but the mouse problem: i have a pointer that can't moove
(In reply to comment #16) > (In reply to comment #15) > > Is this reproducible on the latest development kernel, currently 2.6.19-rc6? > > > > partialy > i can standby and resume without problem but the mouse problem: > i have a pointer that can't moove > Stopping tasks: =======================================================| Suspending console(s) Back to C! agpgart: detected 4MB dedicated video ram. ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 PCI: Setting latency timer of device 0000:00:02.0 to 64 PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was 22802020, writing 2802020) PCI: Setting latency timer of device 0000:00:1e.0 to 64 ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1f.2 to 64 ACPI: PCI Interrupt 0000:00:1f.4[C] -> Link [LNKH] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1f.4 to 64 usb usb2: root hub lost power or was reset ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 PCI: Setting latency timer of device 0000:00:1f.5 to 64 PM: Writing back config space on device 0000:01:03.0 at offset 1 (was 4100083, writing 4100087) ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 Yenta O2: res at 0x94/0xD4: ca/00 Yenta O2: enabling read prefetch/write burst PM: Writing back config space on device 0000:01:03.1 at offset 1 (was 4100083, writing 4100087) ACPI: PCI Interrupt 0000:01:03.1[B] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 PM: Writing back config space on device 0000:02:04.0 at offset f (was 38080100, writing 38080105) PM: Writing back config space on device 0000:02:04.0 at offset 6 (was 0, writing f4100000) PM: Writing back config space on device 0000:02:04.0 at offset 5 (was 1, writing 2401) PM: Writing back config space on device 0000:02:04.0 at offset 4 (was 0, writing f4200000) PM: Writing back config space on device 0000:02:04.0 at offset 3 (was 0, writing 4208) PM: Writing back config space on device 0000:02:04.0 at offset 1 (was 2900000, writing 2900117) PM: Writing back config space on device 0000:07:00.0 at offset f (was 100, writing 105) PM: Writing back config space on device 0000:07:00.0 at offset 4 (was ffffe000, writing 28000000) Restarting tasks... done psmouse.c: Failed to enable mouse on isa0060/serio1
Please file a bug for this upstream at http://bugzilla.kernel.org and post the new URL here File the bug against 2.6.19-rc6 but mention that the bug exists on all kernels you have tested.