Keyboard and touchpad doesn't work after suspend-to-ram on a Fujitsu-Siemens Amilo M1420

[Federico Sassi]

Hello,
keyboard and touchpad doesn't work after resuming from suspend-to-ram on a
Fujitsu-Siemens Amilo M1420 (notebook).
Keyboard and touchpad are ps2 devices (internal).

I've tried on Warty, Hoary and now Breezy (gnome - Ubuntu), always with the same
results.
Hibernation (suspend-to-disk) works flawlessy (even if it is slow), but suspend
don't! When I suspend the notebook goes down fine, when i wake it up it restore
X, and almost everything (network, usb,services) but NO PS2 devices like my
integrated keyboard e touchpad! Though my usb mouse works perfetcly after suspend.

I've tried lots of things but I haven't found any way to get the keyboard (or
the touchpad) working after suspend (though after hibernation it works perfectly!):
-I've tried to recompile the kernel with ps2 devices modularized (module atkbd
or similar) and forcing the module down (and the up) when suspending. But it
didnt' worked.
-I've tried the swsusp2 patch to the kernel, too, without improvements.
-I've tried to add the s3_bios (or similar) boot parameter to the kernel without
results.

The notebook is Mitac 8050 re-branded by Fujitsu-Siemens (my BIOS is up-to-date).
Can it be a problem with my DSDT table? If it is needed i can upload it.
Now I'm with Ubuntu Breezy, ubuntu kernel 2.6.12-9-686. I launch the suspend
script from the logout menu.

I think that the keyboard is quite buggy, because when I run xev and I press the
volume up key combination Fn+F3 (or the volume down Fn+F4) i get an endless
sequence of the same char 176 (or 174) so I have to link that function to
another combination of keys.

Thank you very much for your attention and your support.
If you need something just ask!

Federico Sassi

[Federico Sassi (fsassi)]

Created an attachment (id=4924)
output of 'lscpi -vv'

[Matt Zimmerman (mdz)]

Can you test on current Dapper please?

[Federico Sassi (fsassi)]

I've just tested over my 2.6.15-19-686 kernel in dapper.
With fglrx driver running the hibernation work flawlessy, but the system doesn't even go into suspend.

With open-source driver (ati) the hibernation works great. When I suspend to ram the system suspends correctly but when it wakes up I got NO keyboard and NO touchpad....exactly like in breezy!

If you need more info, just tell me!

Thanks really much!

Federico

[Federico Sassi (fsassi)]

Sorry,
I've tested a little bit further.
With fglrx the hibernation works ok just for few minutes... if I leave my system hibernated for a few hours then when I turn it on the screen is full of garbage...
I haven't tested yet with open source driver...

Federico

[Federico Sassi (fsassi)]

9 May 2006
2.6.15-22-686

[Federico Sassi (fsassi)]

9 May 2006
2.6.15-22-686

[Federico Sassi (fsassi)]

9 May 2006
2.6.15-22-686

[Federico Sassi (fsassi)]

Hi,
I've just tested suspend to ram and hibernation (suspend to disk) with the later dapper updates installed (at 9 May 2006 13.00 CET) and the latest dapper kernel 2.6.15-22-686

Hibernation works fine, everything came up all right. (The system is still slow for few minutes after suspend and the "Load" indicator in the Gnome System Monitor says that the system is under a 100% load, slowly decreasing.

Suspend to ram is still not working. The system suspends right, it wakes up almost fine (display, network, usb mouse are ok!) but I still get no keyboard (and touchpad, which is ps2) and not full ACPI (I get no battery indicator, but it knows that now I'm using AC power).

In the dmesg output of the system after suspend to ram (file attached) I read a lot of:
SET: Misaligned resource pointer: d580ce42 Type 07 Len 0
(and other acpi-related errors)
and
atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
(line 400 in the attacched file)

Now I don't know what to do to fix this issue... may someone help me, please?
Thanks very much for reading!

If more information are needed just let me know!

Federico Sassi

[Federico Sassi (fsassi)]

Scrive Matt Zimmerman <email address hidden>:

> Can you test on current Dapper please?

Hi, I've just tested and posted my results on launchpad.
Thanks really much for caring!
I'd like really much to get this bug resolved before Dapper, because a really
need suspend to ram!

Federico Sassi

>
> ** Changed in: acpi (Ubuntu)
> Sourcepackagename: acpi => linux-source-2.6.15
> Binarypackagename: acpi => None
> Status: Unconfirmed => Needs Info
> --
> Keyboard and touchpad doesn't work after suspend-to-ram on a Fujitsu-Siemens
> Amilo M1420
> https://launchpad.net/malone/bugs/25673
>
>

[Federico Sassi (fsassi)]

Hi,
I've just tested suspend to ram and hibernation (suspend to disk) with the later dapper updates installed (at 9 May 2006 13.00 CET) and the latest dapper kernel 2.6.15-22-686

Hibernation works fine, everything came up all right. (The system is still slow for few minutes after suspend and the "Load" indicator in the Gnome System Monitor says that the system is under a 100% load, slowly decreasing.

Suspend to ram is still not working. The system suspends right, it wakes up almost fine (display, network, usb mouse are ok!) but I still get no keyboard (and touchpad, which is ps2) and not full ACPI (I get no battery indicator, but it knows that now I'm using AC power).

In the dmesg output of the system after suspend to ram (file attached) I read a lot of:
SET: Misaligned resource pointer: d580ce42 Type 07 Len 0
(and other acpi-related errors)
and
atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
(line 400 in the attacched file)

Now I don't know what to do to fix this issue... may someone help me, please?
Thanks very much for reading!

If more information are needed just let me know!

Federico Sassi

[Kashif Sheikh (kashms)]

I had the same issue on a Medion MD5400 laptop. Although suspend to ram worked both in hoary and breezy, keyboard would freeze in dapper. Searching around I found the suggestion that it had something to do with the ps2 mouse. I solved the keyboard issue by removing the psmouse module before suspend:

$ sudo modprobe -r psmouse

and reloading it after resume:

$ sudo modprobe psmouse

If it works for you then you can put the psmouse module in /etc/default/acpi-support.

[Federico Sassi (fsassi)]

I've just tried to remove the psmouse module just before suspending like you said but I get the same result.... no keyboard and touchpad (a ps2 mouse) after restarting.

Thanks anyway! Do you have any other suggestion?

Federico Sassi

[Kashif Sheikh (kashms)]

You could try to boot with a ps2 mouse instead of a usb mouse. Try to
suspend and resume and if keyboard is still unresponsive unplug the ps2
mouse and test keyboard again.

If that doesn't provide any clues you could try to disable USB legacy
support in BIOS. Finally, try i8042.noaux as a boot option. There are
other i8042 type boot options but i8042.noaux is the only one I tested
(didn't have an affect for me). Try googling around for the other
options.

On Fri, 2006-06-09 at 08:23 +0000, Federico Sassi wrote:
> I've just tried to remove the psmouse module just before suspending like
> you said but I get the same result.... no keyboard and touchpad (a ps2
> mouse) after restarting.
>
> Thanks anyway! Do you have any other suggestion?
>
> Federico Sassi
>

[Federico Sassi (fsassi)]

ops, sorry if I didn't answer you before but I have missed the mail containing your answer!

I'm on a laptop and I don't have a ps2 port!
Moreover my usb mouse doesn't have any problem! It's my (integrated) ps2-keyboard that freeze!

So what can I do?
Should I try edgy knot-2?

Federico

[Simon Law (sfllaw)]

Often the touchpad is controlled by the psmouse module. Could
you please try the workaround documented in bug 22931?

Thanks.

[Federico Sassi (fsassi)]

Hi
I've tried, like said in bug 22931, to rmmod button and psmouse but it's not working neither the touchpad neither the keyboard.

I've noticed that acpi doesn't come up right so I did (thanks to copy&paste&dasher) a
sudo /etc/init.d/acpid restart
and a
sudo /etc/init.d/acpi-support restart
but it didn't changed anything!

Would you like output from dmesg?

Thanks for caring!

    Federico

[Federico Sassi (fsassi)]

Hi,
here there's dmesg output after waking up from suspend.
as you can see there are a lot of

**** SET: Misaligned resource pointer: d72881c2 Type 07 Len 0

and

atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).

and

ACPI: read EC, IB not empty
ACPI-0412: *** Error: Handler for [EmbeddedControl] returned AE_TIME
ACPI-0517: *** Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node c1599560), AE_TIME

Maybe the error is here...

thanks

   Federico

[Federico Sassi (fsassi)]

Hi,
sorry for another entry but I forgot to mention my test about booting with different parameter of i8042 as suggested by Kashif Sheikh in a precedent entry in this bug.
I've tried booting with:
i8042.noaux
i8042.reset
i8042.noacpi

It didn't worked in every case but there are little differences in dmesg outputs

NOACPI
it's exacly like without that booting option, in dmesg there is the same
"i8042: failed to resume active multiplexor, mouse won't work."

NOAUX
there is no line in dmesg after resume telling anything about i8042 and there is only one
"atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
 atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known."

RESET
there is a different statement:
"i8042.c: i8042 controller selftest failed. (0x0 != 0x55)"

Do you know any explanation about this?

Bye

Federico

[reh4c (gene-hoffler)]

After suspending my Fujitsu LOOX subnotebook, the integrated stick-type (nipple) pointing device does not re-initialize. However, after plugging in a USB mouse, it functions again. I've been having this same problem since Breezy. I am using Edgy Knot 3. Any fix anticipated? Thanks.

[emvy (mate-varga)]

Same at my Lenovo T60. Everything works fine, just no keyboard - even the trackpoint is OK.

Nothing helps, just a reboot.

[Federico Sassi (fsassi)]

I've installed Ubuntu 6.10 Edgy Eft .... and EVERYTHING WORKS NOW!
Suspend and hibernate.

WOW!

Thank you very much, Ubuntu!

[Luka Renko (lure)]

Closed based on multiple positive reports on edgy. If you still have this problem with up-to-date Edgy, feel free to re-open and provide details about your HW.

[Peter Whittaker (pwwnow)]

On Mon, 2007-01-08 at 11:45 +0000, Luka Renko wrote:
> Closed based on multiple positive reports on edgy. If you still have
> this problem with up-to-date Edgy, feel free to re-open and provide
> details about your HW.

Since Dapper will be supported until 2011, it may be best to regress
check this against a comparable Dapper system then redirect the bug to
the appropriate kernel version. It may not get fixed, but if it is an
open problem on a supported release, it should be tracked as such.

FWIW, YMMV, IANAM (I am not a MOTU),

pww

[Luka Renko (lure)]

Peter, this would be nice, but in this particular case it is very hard to do as it is hardware related. Even if it would not be hardware related, it would require to have older (supported) versions installed and quite some time to confirm.
Even if this would be confirmed with older release, it may not be feasible to backport the this particular fix as we are talking about kernel bug (2.6 kernels change *a lot* between minor releases).

General policy is to close bug as Fix Released when fixed package is uploaded to Ubuntu repositories (see [1]). This is also true if the fix was uploaded to current development version. If the bug is critical or has severe impact on many users, you may request a backport - select "Nominate for Release" and the bug would be evaluated by the bug/release team if it qualifies for Stable Release Update (SRU - see [2]).

[1] https://wiki.ubuntu.com/Bugs/CommonTasks
[2] https://wiki.ubuntu.com/StableReleaseUpdates

[Peter Whittaker (pwwnow)]

Luka, thanks for the pointers to the guidelines. Since this isn't a regression (it never worked), is not a security vulnerability, and is unlikely to cause data loss, it isn't a candidate for backporting.

Thanks again,

pww

[Victor Noël (victornoel)]

Hi

i am on a lenovo 3000 n100 with feisty (linux-image-2.6.20-6-generic-2.6.20-6.11) and i get this message :
"i8042: failed to resume active multiplexor, mouse won't work."

when i come back from suspend

i think it was working on 2.6.17 on edgy.

[Ben Collins (ben-collins)]

Rejecting 2.6.20 target. Never confirmed to have broken there.

kaouete, please open a new bug for your problem instead of pasting to the end of some other bug report.

[Federico Sassi (fsassi)]

Hi,
I'm really sorry to not have posted it sooner...

on Ubuntu 6.10 Edgy Eft suspend and hibernate WORKS perfectly!!!
so you can close the bug there.

on Ubuntu 7.04 Feisty Fawn till today (25 March 2007 on 2.6.20-12-generic) suspend and hibernate WORKS perfectly .

Thanks to all.

Federico

[Peter Whittaker (pwwnow)]

Marking as rejected in 2.6.15 to stop this report from appearing in "open bug" searches: It is fixed in 2.6.17 and not a candidate for backporting.

[Wesley Stessens (wesley)]

This bug happens to me in Gutsy Gibbon now. Kernel 2.6.22-9-generic.
I have an HP Pavilion dv9058ea laptop.

My keyboard keeps working, though, but maybe it is not PS2?
My touchpad does not work right, it flies to all directions when I try to use it and simulates clicks when it shouldn't.
My USB mouse keeps working fine.
My Caps Lock key keeps blinking on/off/on/off... (although that's only a visual problem)

[TJ (tj)]

Wesley, your problem may not be the issue this bug is reporting. To help determine that please provide the following reports:

$ cat -n /proc/bus/input/devices | egrep -B 6 -A 4 'H:.+mouse.+event'

$ awk 'BEGIN {tp=0;i=0;} !tp && $0 ~ /Section.+InputDevice/ {i=1;x=0;} i == 1 {cfg[x++]=$0;} $0 ~ /Driver.+synaptics/ {tp=1;} $0 ~ /EndSection/ {i=0;} END {for(i=0;i<x;i++) {print cfg[i];}} ' /etc/X11/xorg.conf

Also, please include the following additional information (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Leann Ogasawara (leannogasawara)]

This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!