On Thu, 4 Aug 2005 23:07:33 -0500
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> It requests BIOS to hand off control of USB which disables USB legacy
> emulation
> and all troubles associated with it. We could start with -mm...
This also fixes an issue I encountered while doing power
On Fri, Aug 05, 2005 at 12:07:55AM -0400, Michael Krufky wrote:
> >Sounds like a fun thing for post-2.6.13.
> >
> >What does usb-handoff do, precisely?
> >
> I just did a series tests. This is necessary, because the problem was
> intermittent for me. usb-handoff fixes all of my problems!!!
>
On Fri, Aug 05, 2005 at 12:07:55AM -0400, Michael Krufky wrote:
Sounds like a fun thing for post-2.6.13.
What does usb-handoff do, precisely?
I just did a series tests. This is necessary, because the problem was
intermittent for me. usb-handoff fixes all of my problems!!!
without
On Thu, 4 Aug 2005 23:07:33 -0500
Dmitry Torokhov [EMAIL PROTECTED] wrote:
It requests BIOS to hand off control of USB which disables USB legacy
emulation
and all troubles associated with it. We could start with -mm...
This also fixes an issue I encountered while doing power measurements:
Andrew Morton wrote:
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
On Thursday 04 August 2005 22:09, Frank Peters wrote:
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
On Thursday 04 August 2005 22:54, Andrew Morton wrote:
> Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> >
> > On Thursday 04 August 2005 22:09, Frank Peters wrote:
> > > I'll use bugzilla to report any problems with 2.6.13-rc6.
> > >
> > > But since I've included the "usb-handoff" option at boot
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
>
> On Thursday 04 August 2005 22:09, Frank Peters wrote:
> > 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)
On Thursday 04 August 2005 22:09, Frank Peters wrote:
> 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
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
Michael Krufky <[EMAIL PROTECTED]> wrote:
>
> I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel
> maintainer.
>
> Vojtech, I figured these should be sent to you. If I am wrong, please
> redirect them to the correct person / list and let us know.
>
(Pleasee don't top-post.
Michael Krufky [EMAIL PROTECTED] wrote:
I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel
maintainer.
Vojtech, I figured these should be sent to you. If I am wrong, please
redirect them to the correct person / list and let us know.
(Pleasee don't top-post. See what
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
On Thursday 04 August 2005 22:09, Frank Peters wrote:
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
Dmitry Torokhov [EMAIL PROTECTED] wrote:
On Thursday 04 August 2005 22:09, Frank Peters wrote:
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.
On Thursday 04 August 2005 22:54, Andrew Morton wrote:
Dmitry Torokhov [EMAIL PROTECTED] wrote:
On Thursday 04 August 2005 22:09, Frank Peters wrote:
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
Andrew Morton wrote:
Dmitry Torokhov [EMAIL PROTECTED] wrote:
On Thursday 04 August 2005 22:09, Frank Peters wrote:
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
On Sun, 31 Jul 2005 13:42:45 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > Booting linux-2.6.13-rc4 with the "usb-handoff" option gives me
> > a working keyboard everytime now.
>
> But 2.6.12 did not require this workaround, yes?
>
I still have linux-2.6.12.3 on my machine and the
Frank Peters <[EMAIL PROTECTED]> wrote:
>
> On Sun, 31 Jul 2005 20:45:32 +0200
> Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
>
> > >
> > > During a failed boot, when the keyboard was unresponsive, I managed
> > > to capture a kernel log of this failure. Here are the lines that caught
> > > my
On Sun, 31 Jul 2005 20:45:32 +0200
Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> >
> > During a failed boot, when the keyboard was unresponsive, I managed
> > to capture a kernel log of this failure. Here are the lines that caught
> > my attention:
> >
> > kernel: i8042.c: Can't read CTR while
On Sat, Jul 30, 2005 at 02:34:53AM -0400, Frank Peters wrote:
> On Fri, 29 Jul 2005 21:37:24 -0700
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > So I dunno, sorry. Brute-force it with a git bisection search, perhaps?
>
> I compiled 2.6.13-rc4 with ACPI debugging enabled.
>
> During a
On Sat, Jul 30, 2005 at 02:34:53AM -0400, Frank Peters wrote:
On Fri, 29 Jul 2005 21:37:24 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
So I dunno, sorry. Brute-force it with a git bisection search, perhaps?
I compiled 2.6.13-rc4 with ACPI debugging enabled.
During a failed boot,
On Sun, 31 Jul 2005 20:45:32 +0200
Vojtech Pavlik [EMAIL PROTECTED] wrote:
During a failed boot, when the keyboard was unresponsive, I managed
to capture a kernel log of this failure. Here are the lines that caught
my attention:
kernel: i8042.c: Can't read CTR while initializing
Frank Peters [EMAIL PROTECTED] wrote:
On Sun, 31 Jul 2005 20:45:32 +0200
Vojtech Pavlik [EMAIL PROTECTED] wrote:
During a failed boot, when the keyboard was unresponsive, I managed
to capture a kernel log of this failure. Here are the lines that caught
my attention:
On Sun, 31 Jul 2005 13:42:45 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Booting linux-2.6.13-rc4 with the usb-handoff option gives me
a working keyboard everytime now.
But 2.6.12 did not require this workaround, yes?
I still have linux-2.6.12.3 on my machine and the usb-handoff
> >After downloading and compiling the latest version 2.6.12, my
> >keyboard becomes unresponsive and dead following the boot process.
>
FWIW I have similar problem with Toshiba Portege 4000. Every second reboot
keyboard is not there. It is really not there - i.e. I cannot even enter BIOS
On Fri, 29 Jul 2005 21:37:24 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> So I dunno, sorry. Brute-force it with a git bisection search, perhaps?
I compiled 2.6.13-rc4 with ACPI debugging enabled.
During a failed boot, when the keyboard was unresponsive, I managed
to capture a kernel
After downloading and compiling the latest version 2.6.12, my
keyboard becomes unresponsive and dead following the boot process.
FWIW I have similar problem with Toshiba Portege 4000. Every second reboot
keyboard is not there. It is really not there - i.e. I cannot even enter BIOS
setup or
On Friday 29 July 2005 23:37, Andrew Morton wrote:
>
> The diff between 2.6.12-rc4-mm2 and 2.6.12-rc5-mm1 is enormous, but there
> aren't any significant input driver changes there:
> http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc4-mm2-2.6.12-rc5-mm1
>
>From the original
Michael Krufky <[EMAIL PROTECTED]> wrote:
>
> Andrew Morton wrote:
>
> >Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> >
> >> Sadly, I must report that yes, the problem still intermittently occurs
> >> in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
> >> Motherboard. Never
Michael Krufky wrote:
Oops... I'm sorry, that was the OLD dmesg... I am still having the
same symptoms, but the log shows up different error message in newer
kernels... I'll have to reproduce that and send it an another email.
... soon to follow ...
In newer kernels (including 2.6.13-rc4),
Oops... I'm sorry, that was the OLD dmesg... I am still having the same
symptoms, but the log shows up different error message in newer
kernels... I'll have to reproduce that and send it an another email. ...
soon to follow ...
Michael Krufky wrote:
I dug up the original email that I sent
Andrew Morton wrote:
Michael Krufky <[EMAIL PROTECTED]> wrote:
Sadly, I must report that yes, the problem still intermittently occurs
in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
Motherboard. Never has a problem in windows and never in 2.6.11 and
earlier.
I first
On Thu, 28 Jul 2005, Andrew Morton wrote:
> Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> > Sadly, I must report that yes, the problem still intermittently occurs
> > in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
> > Motherboard. Never has a problem in windows and never
On Thu, 28 Jul 2005 22:28:38 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> Guys, are these problems fixed in 2.6.13-rc4?
>
> If not, please cc linux-kernel on the reply, thanks.
>
Unfortunately, with 2.6.13-rc4 the problems are still here.
It takes, on average, about 5-6 reboots before I
On Thu, 28 Jul 2005 22:28:38 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Guys, are these problems fixed in 2.6.13-rc4?
If not, please cc linux-kernel on the reply, thanks.
Unfortunately, with 2.6.13-rc4 the problems are still here.
It takes, on average, about 5-6 reboots before I get a
On Thu, 28 Jul 2005, Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
Sadly, I must report that yes, the problem still intermittently occurs
in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
Motherboard. Never has a problem in windows and never in 2.6.11
Oops... I'm sorry, that was the OLD dmesg... I am still having the same
symptoms, but the log shows up different error message in newer
kernels... I'll have to reproduce that and send it an another email. ...
soon to follow ...
Michael Krufky wrote:
I dug up the original email that I sent
Michael Krufky [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
Sadly, I must report that yes, the problem still intermittently occurs
in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
Motherboard. Never has a problem in windows
On Friday 29 July 2005 23:37, Andrew Morton wrote:
The diff between 2.6.12-rc4-mm2 and 2.6.12-rc5-mm1 is enormous, but there
aren't any significant input driver changes there:
http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc4-mm2-2.6.12-rc5-mm1
From the original thread it
Michael Krufky <[EMAIL PROTECTED]> wrote:
>
> Sadly, I must report that yes, the problem still intermittently occurs
> in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
> Motherboard. Never has a problem in windows and never in 2.6.11 and
> earlier.
>
> I first noticed this
Andrew Morton wrote:
Michael Krufky <[EMAIL PROTECTED]> wrote:
I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel
maintainer.
Vojtech, I figured these should be sent to you. If I am wrong, please
redirect them to the correct person / list and let us know.
Thank you.
Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel
maintainer.
Vojtech, I figured these should be sent to you. If I am wrong, please
redirect them to the correct person / list and let us know.
Thank you.
Michael Krufky [EMAIL PROTECTED] wrote:
Sadly, I must report that yes, the problem still intermittently occurs
in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
Motherboard. Never has a problem in windows and never in 2.6.11 and
earlier.
I first noticed this problem
43 matches
Mail list logo
