On 8/27/07, Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-08-23 at 12:36 -0500, Florin Iucha wrote:
> > On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
> > > this sounds alot like the post i did yesterday titled 'nfs4 hang
> > > regression'
> > > i tracked it down to commit
On Thu, 2007-08-23 at 12:36 -0500, Florin Iucha wrote:
> On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
> > this sounds alot like the post i did yesterday titled 'nfs4 hang regression'
> > i tracked it down to commit 3d39c691ff486142dd9aaeac12f553f4476b7a6
>
> Yes, it certainly does --
On Thu, Aug 23, 2007 at 10:14:38AM -0700, Bret Towe wrote:
> this sounds alot like the post i did yesterday titled 'nfs4 hang regression'
> i tracked it down to commit 3d39c691ff486142dd9aaeac12f553f4476b7a6
Yes, it certainly does -- all the symptoms match!
I'm not [alone in] seeing dead keyboard
On 8/23/07, Florin Iucha <[EMAIL PROTECTED]> wrote:
> Trond,
>
> Fess up... I'm closing in:
>
>http://iucha.net/2.6.23-rc3/2.6.23-rc-bisect.png
>
> [Dropping Jiri and linux-usb-devel from future postings. You are
> included now just for communicating the conclusion of this thread.]
>
> On Wed,
Trond,
Fess up... I'm closing in:
http://iucha.net/2.6.23-rc3/2.6.23-rc-bisect.png
[Dropping Jiri and linux-usb-devel from future postings. You are
included now just for communicating the conclusion of this thread.]
On Wed, Aug 22, 2007 at 08:22:00AM -0500, Florin Iucha wrote:
> On Tue, Aug
On Tue, Aug 21, 2007 at 03:42:26PM +0200, Jiri Kosina wrote:
> On Tue, 21 Aug 2007, Florin Iucha wrote:
>
> > There is another interesting angle to this: in the past, every time I
> > had keyboard problems, it used to be caused by the VFS and/or NFS...
> > after much wrangling, a bunch of bugs w
On Tue, 21 Aug 2007, Jiri Kosina wrote:
> On Tue, 21 Aug 2007, Florin Iucha wrote:
>
> > I have enabled USB debugging and I see a bunch (=46) of these messages:
>
> >[ $timestamp] usb 1-9: usb auto-suspend
> >[ $timestamp] usb 1-9: usb auto-resume
> >[ $timestamp] ehci_hcd :00
On Tue, 21 Aug 2007, Florin Iucha wrote:
> There is another interesting angle to this: in the past, every time I
> had keyboard problems, it used to be caused by the VFS and/or NFS...
> after much wrangling, a bunch of bugs were fixed (Hi Trond, Peter,
> Alan!). Now, after the keyboard "locked
On Tue, Aug 21, 2007 at 08:17:59AM -0500, Florin Iucha wrote:
> On Tue, Aug 21, 2007 at 03:05:25PM +0200, Jiri Kosina wrote:
> > > I have rebuilt 2.6.23-rc3 with 'CONFIG_USB_EHCI_HCD=m' and
> > > 'CONFIG_USB_SUSPEND is not set' and will use it for a while, to see if
> > > the keyboard/usb behaves
On Tue, Aug 21, 2007 at 03:05:25PM +0200, Jiri Kosina wrote:
> > I have rebuilt 2.6.23-rc3 with 'CONFIG_USB_EHCI_HCD=m' and
> > 'CONFIG_USB_SUSPEND is not set' and will use it for a while, to see if
> > the keyboard/usb behaves or not.
>
> Thanks. If this doesn't give us any hint, it would be us
On Tue, 21 Aug 2007, Florin Iucha wrote:
> I have rebuilt 2.6.23-rc3 with 'CONFIG_USB_EHCI_HCD=m' and
> 'CONFIG_USB_SUSPEND is not set' and will use it for a while, to see if
> the keyboard/usb behaves or not.
Thanks. If this doesn't give us any hint, it would be useful if you could
do git-bis
On Tue, Aug 21, 2007 at 06:51:15AM -0500, Florin Iucha wrote:
> On Wed, Aug 15, 2007 at 04:58:33PM +0200, Jiri Kosina wrote:
> > On Wed, 15 Aug 2007, Florin Iucha wrote:
> >
> > > [See my message to Alan]: It happened twice, within 15 minutes of
> > > boot+login, with 2.6.23-rc3-$whatever . I do
On Tue, Aug 21, 2007 at 02:04:26PM +0200, Jiri Kosina wrote:
> > I have enabled USB debugging and I see a bunch (=46) of these messages:
>
> >[ $timestamp] usb 1-9: usb auto-suspend
> >[ $timestamp] usb 1-9: usb auto-resume
> >[ $timestamp] ehci_hcd :00:02.1: GetStatus port 9 st
Am Dienstag 21 August 2007 schrieb Oliver Neukum:
> [ 60.756730] usb 1-9: usb auto-resume
> Did you hit a key at that time?
>
>
> It looks like your keyboard gets autosuspended. But how can that happen?
> Keyboards should never autosuspend, as they are always open.
> The patch for minimum autos
On Tue, 21 Aug 2007, Oliver Neukum wrote:
> It looks like your keyboard gets autosuspended. But how can that happen?
> Keyboards should never autosuspend, as they are always open. The patch
> for minimum autosuspend support in HID did get in earlier, didn't it?
Hi Oliver,
it actually even is n
Am Dienstag 21 August 2007 schrieb Florin Iucha:
> On Wed, Aug 15, 2007 at 04:58:33PM +0200, Jiri Kosina wrote:
> > On Wed, 15 Aug 2007, Florin Iucha wrote:
> >
> > > [See my message to Alan]: It happened twice, within 15 minutes of
> > > boot+login, with 2.6.23-rc3-$whatever . I does not happen
On Tue, 21 Aug 2007, Florin Iucha wrote:
> I have enabled USB debugging and I see a bunch (=46) of these messages:
>[ $timestamp] usb 1-9: usb auto-suspend
>[ $timestamp] usb 1-9: usb auto-resume
>[ $timestamp] ehci_hcd :00:02.1: GetStatus port 9 status 001005 POWER
> sig=se0
On Wed, Aug 15, 2007 at 04:58:33PM +0200, Jiri Kosina wrote:
> On Wed, 15 Aug 2007, Florin Iucha wrote:
>
> > [See my message to Alan]: It happened twice, within 15 minutes of
> > boot+login, with 2.6.23-rc3-$whatever . I does not happen with
> > 2.6.2[123](-rc*)? After the two incidents, I re
On Wed, 15 Aug 2007, Tejun Heo wrote:
> Alan Stern wrote:
> > I think we can simply remove the error message. There's no obvious
> > reason why sysfs_remove_bin_file() should complain about attempts to
> > remove a nonexistent file; sysfs_remove_file() doesn't.
> >
> > This patch will get rid
Cornelia Huck wrote:
> On Wed, 15 Aug 2007 23:54:43 +0900,
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> Alan Stern wrote:
>>> I think we can simply remove the error message. There's no obvious
>>> reason why sysfs_remove_bin_file() should complain about attempts to
>>> remove a nonexistent file;
On Wed, 15 Aug 2007, Florin Iucha wrote:
> On Wed, Aug 15, 2007 at 10:38:54AM -0400, Alan Stern wrote:
> > This patch will get rid of the annoying error messages. It won't do
> > anything about your keyboard's tendency to spontaneously stop working,
> > alas.
>
> My keyboard works fine for day
On Wed, 15 Aug 2007 23:54:43 +0900,
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Alan Stern wrote:
> > I think we can simply remove the error message. There's no obvious
> > reason why sysfs_remove_bin_file() should complain about attempts to
> > remove a nonexistent file; sysfs_remove_file() doesn't
On Wed, 15 Aug 2007, Florin Iucha wrote:
> [See my message to Alan]: It happened twice, within 15 minutes of
> boot+login, with 2.6.23-rc3-$whatever . I does not happen with
> 2.6.2[123](-rc*)? After the two incidents, I rebooted in 2.6.23-rc2 and
> it is working for an hour now.
It is not i
On Wed, Aug 15, 2007 at 04:49:02PM +0200, Jiri Kosina wrote:
> On Wed, 15 Aug 2007, Florin Iucha wrote:
>
> > Today my USB keyboard stopped working in the middle of composing and
> > e-mail. I unplugged it and plugged it back, with no success. I
> > logged in remotely and found this lovely messa
Alan Stern wrote:
> I think we can simply remove the error message. There's no obvious
> reason why sysfs_remove_bin_file() should complain about attempts to
> remove a nonexistent file; sysfs_remove_file() doesn't.
>
> This patch will get rid of the annoying error messages. It won't do
> any
On Wed, Aug 15, 2007 at 10:38:54AM -0400, Alan Stern wrote:
> This patch will get rid of the annoying error messages. It won't do
> anything about your keyboard's tendency to spontaneously stop working,
> alas.
My keyboard works fine for days, with kernels up to and including
2.6.23-rc2 . I hav
On Wed, 15 Aug 2007, Florin Iucha wrote:
> Today my USB keyboard stopped working in the middle of composing and
> e-mail. I unplugged it and plugged it back, with no success. I
> logged in remotely and found this lovely message:
The error message seems unrelated to your keyboard becoming dead.
On Wed, 15 Aug 2007, Florin Iucha wrote:
> Today my USB keyboard stopped working in the middle of composing and
> e-mail. I unplugged it and plugged it back, with no success. I
> logged in remotely and found this lovely message:
>
> [ 1301.567351] usb 1-4: USB disconnect, address 3
> [ 1301.567
Today my USB keyboard stopped working in the middle of composing and
e-mail. I unplugged it and plugged it back, with no success. I
logged in remotely and found this lovely message:
[ 1301.567351] usb 1-4: USB disconnect, address 3
[ 1301.567356] usb 1-4.2: USB disconnect, address 5
[ 1301.56759
29 matches
Mail list logo
