From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-users@lists.sourceforge.net
Subject: [2.5] EHCI HID keyboard not unloaded at reboot time ?
Date: 15 Feb 2003 17:03:00 +0100 [thread overview]
Message-ID: <1045324980.1767.28.camel@rousalka> (raw)
[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]
[ Please CC me any replies, I don't follow the list closely ]
Hi,
This is a question related to :
http://bugzilla.kernel.org/show_bug.cgi?id=9
Basically I have a usb keyboard plugged on an external USB2 hub. Using
a monolithic ehci/hid kernel I can get it to work in 2.5. It's also used
in usb1 mode by the bios and the bootloader.
However when I shut down or reboot from 2.5, I loose keyboard support
in the bios/bootloader/linux 2.4 (used to loose it in linux 2.5 also but
recent ehci enhancements enable 2.5 to recover it). Nothing short of a
PSU stop (neither reset nor stop button works) will recover it.
What happens is the usb subsystem is somehow not unloaded at
shutdown/reboot time. The bios and linux 2.4 then find a usb subsystem
already setup in usb2 mode, and since they only know usb1 handling, they
are unable to recover usb devices. This is a pain when you have like me
an usb-only input setup. It means crawling under the desk every shutdown
time to reach the PSU power button, and feel the hardware aging
prematurely (and I'm lucky to *have* a PSU power button, I imagine some
other poor souls may have to unplug it to get the same effect).
I say the usb subsystem is somehow not unloaded because
1. when I request a shutdown the keyboard is still active after the «
Power Down » message (this mobo wants acpi to shutdown properly so this
is easy to check with a acpi-less kernel)
2. I sprinkled the ehci unloading function whith printks some time ago
and it was never called.
3. the usb2 hub has a led to show if it's in usb1 or usb2 mode, and it
stays on after the reboot (when cold-booting in uhci 2.4 it stays of)
Now I'm wondering if someone didn't decided at some time that
shutdown=suspend and input devices should stay on in suspend mode so
people can resume their system, ie maybe it's a design mistake instead
of a simple bug.
Can anyone shed some light/advice on this problem ? It's driving me
nuts.
Regards,
--
Nicolas Mailhot
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-02-15 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 16:03 Nicolas Mailhot [this message]
2003-02-16 21:28 ` [2.5] EHCI HID keyboard not unloaded at reboot time ? Pavel Machek
2003-02-18 21:11 ` Nicolas Mailhot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1045324980.1767.28.camel@rousalka \
--to=nicolas.mailhot@laposte.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.