mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: Andrew Morton <akpm@osdl.org>
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Thu, 4 Aug 2005 23:09:47 -0400	[thread overview]
Message-ID: <20050804230947.36c24139.frank.peters@comcast.net> (raw)
In-Reply-To: <20050804162812.29a3f2b2.akpm@osdl.org>

I'll use bugzilla to report any problems with 2.6.13-rc6.

But since I've included the "usb-handoff" option at boot time,
all my problems (except the long dhcp/eth0 connect time) are
now gone.  Right now I'm using 2.6.13-rc5.

I understand the need to pinpoint the kernel version, but the
"usb-handoff" option has even corrected some problems that
started in linux-2.4.x.  For example, my PS/2 mouse now functions
normally.  It has not worked with this motherboard since some time
in the 2.4.x series.  Also, my keyboard lights were malfunctioning
under X-Window since early 2.6.x, but with the "usb-handoff" option
they are working normally now.

If I had known about the "usb-handoff" option earlier, this thread 
probalby would not even have come into existence.  As long as "usb-handoff"
keeps working, I would consider the issue closed.

Frank Peters


On Thu, 4 Aug 2005 16:28:12 -0700
Andrew Morton <akpm@osdl.org> wrote:

> 
> Frank, if any problems remain in 2.6.13-rc6 could you please raise new
> bugzilla.kernel.org records for them?  That way poor old me will be able to
> keep tabs on progress more easily.
> 
> (It's especially important to identify the most recent kernel version which
> didn't have a particular bug)
> 
> Thanks.

  parent reply	other threads:[~2005-08-05  3:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 15:34 Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
2005-06-24 16:59   ` Frank Peters
2005-06-24 17:12     ` Michael Krufky
     [not found]       ` <20050728222838.64517cc9.akpm@osdl.org>
2005-07-29  5:44         ` Michael Krufky
2005-07-29  5:54           ` Andrew Morton
2005-07-30  2:44             ` Zwane Mwaikambo
2005-07-30  3:48             ` Michael Krufky
2005-07-30  3:52               ` Michael Krufky
2005-07-30  4:18                 ` Michael Krufky
2005-07-30  4:37               ` Andrew Morton
2005-07-30  5:57                 ` Dmitry Torokhov
2005-07-30  6:34                 ` Frank Peters
2005-07-31 18:45                   ` Vojtech Pavlik
2005-07-31 19:24                     ` Frank Peters
2005-07-31 20:42                       ` Andrew Morton
2005-07-31 23:48                         ` Frank Peters
2005-07-29 18:33         ` Frank Peters
     [not found]           ` <20050804162812.29a3f2b2.akpm@osdl.org>
2005-08-05  3:09             ` Frank Peters [this message]
2005-08-05  3:20               ` Dmitry Torokhov
2005-08-05  3:54                 ` Andrew Morton
2005-08-05  4:07                   ` Dmitry Torokhov
2005-08-05 10:40                     ` Marc Ballarin
2005-08-05  4:07                   ` Michael Krufky
2005-08-05  6:43                     ` Vojtech Pavlik
2005-08-04 20:19       ` Andrew Morton
2005-06-27 11:39   ` Michael Krufky
     [not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07   ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
2005-07-30  8:33 isa0060/serio0 problems -WAS- " Andrey Borzenkov

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=20050804230947.36c24139.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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®