From: Greg KH <greg@kroah.com>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] Re: 2.6.16-rc1-mm3
Date: Fri, 27 Jan 2006 09:27:20 -0800 [thread overview]
Message-ID: <20060127172720.GB13320@kroah.com> (raw)
In-Reply-To: <43DA161C.1070404@reub.net>
On Sat, Jan 28, 2006 at 01:46:20AM +1300, Reuben Farrelly wrote:
>
>
> On 26/01/2006 6:39 p.m., Greg KH wrote:
> >On Wed, Jan 25, 2006 at 11:44:14PM +1300, Reuben Farrelly wrote:
> >>
> >>On 25/01/2006 8:24 p.m., Andrew Morton wrote:
> >>>http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc1/2.6.16-rc1-mm3/
> >>>
> >>>- Dropped the timekeeping patch series due to a complex timesource
> >>>selection
> >>> bug.
> >>>
> >>>- Various fixes and updates.
> >>Generally quite good again :)
> >>
> >>I'm seeing this USB "handoff" warning message logged when booting up:
> >>
> >>0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?)
> >>
> >>This is not new to this -mm release, looking back over my bootlogs I note
> >>that 2.6-15-rc5-mm1 was OK, but 2.6.15-mm4 was showing this message.
> >>I'll narrow it down if it doesn't appear obvious what the problem is.
> >
> >When this happens, does your usb-ehci driver still work properly
> >(meaning do usb 2.0 devices connect and go at the proper high speeds)?
>
> It seems like every device I can lay my hands on either only supports 1.1
> or doesn't specify what it is. I'll try find something which is known to
> be 2.0. Certainly my 1.1 devices seem to work ok.
>
> >And if you change the USB setting in your bios, does this error message
> >go away?
>
> If I change "USB 2.0 legacy support" from "High Speed 480Mbps" which it was
> originally to "Full Speed 12MBps" then yes it does go away. Although I'm
> not sure that's the best way to have it configured.
How about just disabling USB legacy support in the bios completly?
Unless you have a USB keyboard that you need for a bootloader screen or
BIOS configuration, that's the recommended setting (due to all of the
horrible BIOS USB bugs we have seen over the years.)
If after you find a USB 2.0 device, and have any problems with it,
please let us know.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-27 17:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 7:24 2.6.16-rc1-mm3 Andrew Morton
2006-01-25 8:38 ` [PATCH] convert a for (i = 0 ; i < NR_CPUS ; i++) to for_each_cpu(i) in sched_init() Eric Dumazet
2006-01-25 8:42 ` [PATCH, resent] " Eric Dumazet
2006-01-25 9:14 ` [PATCH] convert a for (i = 0 ; i < NR_CPUS ; i++) to for_each_cpu(i) in files_defer_init() Eric Dumazet
2006-01-25 12:01 ` [PATCH, resent] convert a for (i = 0 ; i < NR_CPUS ; i++) to for_each_cpu(i) in sched_init() Ingo Molnar
2006-01-25 9:01 ` [PATCH] mips: follow the change of split_page() Yoichi Yuasa
2006-01-25 9:16 ` 2.6.16-rc1-mm3: mips, sparc64 split_page breakage Alexey Dobriyan
2006-01-25 9:26 ` [PATCH -mm] Mark ppc_htab_operations as const Alexey Dobriyan
2006-01-25 9:32 ` [PATCH -mm] s390: dasd_eckd: add missing } Alexey Dobriyan
2006-01-25 10:44 ` 2.6.16-rc1-mm3 Reuben Farrelly
2006-01-26 5:39 ` [linux-usb-devel] 2.6.16-rc1-mm3 Greg KH
2006-01-27 12:46 ` Reuben Farrelly
2006-01-27 17:27 ` Greg KH [this message]
2006-01-27 17:49 ` 2.6.16-rc1-mm3 Pete Zaitcev
2006-01-27 19:40 ` 2.6.16-rc1-mm3 Reuben Farrelly
2006-01-27 19:57 ` 2.6.16-rc1-mm3 Pete Zaitcev
2006-01-25 11:40 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-25 15:59 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-26 19:02 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-26 19:47 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-26 19:50 ` 2.6.16-rc1-mm3 Nick Piggin
2006-01-27 10:11 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-01 8:30 ` 2.6.16-rc1-mm3 Nick Piggin
2006-02-01 8:51 ` 2.6.16-rc1-mm3 Andrew Morton
2006-02-02 21:06 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-02 22:20 ` 2.6.16-rc1-mm3 Andrew Morton
2006-02-02 23:48 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-02-03 0:12 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-26 19:58 ` 2.6.16-rc1-mm3 Michal Piotrowski
2006-01-25 14:06 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-25 14:44 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-25 16:46 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-25 18:16 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-25 21:06 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-26 7:03 ` 2.6.16-rc1-mm3 Pekka Enberg
2006-01-27 0:20 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-27 3:23 ` 2.6.16-rc1-mm3 Andrew Morton
2006-01-27 6:03 ` 2.6.16-rc1-mm3 Eric Dumazet
2006-01-27 10:12 ` 2.6.16-rc1-mm3 Andy Whitcroft
2006-01-27 10:37 ` 2.6.16-rc1-mm3 Eric Dumazet
2006-01-25 19:55 ` 2.6.16-rc1-mm3 / netfilter / firehol problems? thunder7
2006-01-25 20:59 ` Jiri Slaby
2006-01-26 8:29 ` Harald Welte
2006-01-26 5:29 ` [BUG] Invalid sleeping function call in 2.6.16-rc1-mm3 Peter Williams
2006-01-26 18:13 ` 2.6.16-rc1-mm3 (soft lockup) Dominik Karall
2006-01-26 19:01 ` 2.6.16-rc1-mm3 (psmouse.c) Dominik Karall
2006-01-26 22:23 ` [RFC: -mm patch] drivers/serial/jsm/: cleanups Adrian Bunk
2006-01-27 11:47 ` 2.6.16-rc1-mm3 Reuben Farrelly
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=20060127172720.GB13320@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=reuben-lkml@reub.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®