From: Sebastian Kemper <sebastian_ml@gmx.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [OHCI] BIOS handoff failed (BIOS bug?)
Date: Fri, 1 Dec 2006 19:28:55 +0100 [thread overview]
Message-ID: <20061201182855.GA7867@section_eight> (raw)
In-Reply-To: <20061201130359.GA3999@section_eight>
On Fri, Dec 01, 2006 at 02:03:59PM +0100, Sebastian Kemper wrote:
> Hello all,
>
> I sometimes get this message when I boot kernel 2.6.19. Could this be
> related to the BIOS option "USB keyboard support"? When I turn it off I
> never get the "handoff failed" message afaik. But I need it to access
> lilo. Now I use an USB->PS2 adapter and turn "USB keyboard support" off.
>
> If "handoff failed" and "USB keyboard support" are related wouldn't it
> make sense to change the USB error handling?
>
> Regards
> Sebastian
I digged deeper:
* the same happens with older kernels (I tried 2.6.17.13 for instance)
* the handoff works every time when "USB Keyboard Support" is disabled
in my BIOS
* the handoff doesn't work when I enable "USB Keyboard Support" and use
the keyboard at the lilo prompt (up, down, enter ...). It does work,
though, when I keep my hands afk.
I also increased the wait time from 5 seconds to 20 in
drivers/usb/host/pci-quirks.c but that didn't change anything. I guess
the bios won't release OHCI in order to be able to serve keyboard input
without usb hid drivers once I hit a key when bios is still in charge.
But I looked around and couldn't see any ill effects so I'll stop
bothering you with this ;-)
Regards
Sebastian
Hardware:
* 32bit Sempron
* Shutte AN35N NForce2 mainboard
...
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Machine check exception polling timer started.
io scheduler noop registered
io scheduler cfq registered (default)
0000:00:02.0 OHCI: BIOS handoff failed (BIOS bug ?) 00000784
############################################################
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK4] -> GSI 11 (level,
low) -> IRQ 11
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
...
/usr/src/linux/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux section_eight 2.6.19 #3 Fri Dec 1 19:04:08 CET 2006 i686 AMD
Sempron(tm) 2400+ AuthenticAMD GNU/Linux
Gnu C 4.1.1
Gnu make 3.81
binutils 2.16.1
util-linux 2.12r
mount 2.12r
module-init-tools 3.2.2
e2fsprogs 1.39
Linux C Library > libc.2.4
Dynamic linker (ldd) 2.4
Procps 3.2.6
Net-tools 1.60
Kbd 1.12
Sh-utils 6.4
udev 103
Modules Loaded rt61 lirc_serial lirc_dev
next prev parent reply other threads:[~2006-12-01 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 13:03 [OHCI] BIOS handoff failed (BIOS bug?) Sebastian Kemper
2006-12-01 18:28 ` Sebastian Kemper [this message]
2006-12-01 23:02 ` Pete Zaitcev
2006-12-01 23:23 ` thockin
2006-12-01 23:29 ` Pete Zaitcev
2006-12-01 23:32 ` thockin
2006-12-02 7:15 ` Sebastian Kemper
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=20061201182855.GA7867@section_eight \
--to=sebastian_ml@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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.