On Thursday 21 February 2008, Alan Stern wrote:
> > = CUT HERE
> > Modify EHCI irq handling on the theory that at least some of the
> > "lost" IRQs are caused by goofage between multiple lowlevel IRQ
> > acking mechanisms: try rescanning before we exit the handler, in
> > case the EHCI-int
On Wed, 20 Feb 2008, David Brownell wrote:
> > CPU 0 CPU 1
> > - -
> > Watchdog timer expires
> > Timer routine acquires spinlock
> > IAA IRQ arrives
> >
On Wed, 20 Feb 2008, David Brownell wrote:
> = CUT HERE
> Modify EHCI irq handling on the theory that at least some of the
> "lost" IRQs are caused by goofage between multiple lowlevel IRQ
> acking mechanisms: try rescanning before we exit the handler, in
> case the EHCI-internal ack (by
On Wednesday 20 February 2008, Andre Tomt wrote:
> David Brownell wrote:
> > On Wednesday 20 February 2008, Andre Tomt wrote:
> >> It has not crashed yet with the patch though.
> >
> > It seems that one of the tweks in this patch made the watchdog
> > act better than before. So unless I hear from
David Brownell wrote:
On Wednesday 20 February 2008, Andre Tomt wrote:
It has not crashed yet with the patch though.
It seems that one of the tweks in this patch made the watchdog
act better than before. So unless I hear from you (before the
start of next week) that some other message appears
On Wednesday 20 February 2008, Alan Stern wrote:
> On Wed, 20 Feb 2008, David Brownell wrote:
>
> > On Wednesday 20 February 2008, Alan Stern wrote:
> > > > ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> > >
> > > lines in the log brings up some ideas that have been percol
On Wed, 20 Feb 2008, David Brownell wrote:
> On Wednesday 20 February 2008, Alan Stern wrote:
> > > ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> >
> > lines in the log brings up some ideas that have been percolating in my
> > mind for a while. They have to do with the
On Wednesday 20 February 2008, Alan Stern wrote:
> > ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
>
> lines in the log brings up some ideas that have been percolating in my
> mind for a while. They have to do with the possibility of a race
> between the watchdog routine
On Wednesday 20 February 2008, Andre Tomt wrote:
> ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd :00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd :00:1d.7: IAA watchdog
On Wed, 20 Feb 2008, Andre Tomt wrote:
> David Brownell wrote:
> > On Tuesday 19 February 2008, Andre Tomt wrote:
> >>> Can you try this diagnostic patch, to see if it reports any messages
> >>> about IAA and/or IAAD oddities? There's surely a quick workaround
> >>> for this, but I'd rather under
David Brownell wrote:
On Tuesday 19 February 2008, Andre Tomt wrote:
Can you try this diagnostic patch, to see if it reports any messages
about IAA and/or IAAD oddities? There's surely a quick workaround
for this, but I'd rather understand the root cause before patching.
Doesn't seem to have tr
On Tue, 19 Feb 2008, David Brownell wrote:
> Please try that diagnostic patch I sent ... with CONFIG_USB_DEBUG.
>
> Near as I can tell this is caused by some hardware oddity that needs
> to be worked around. We seem to be at stage where we've fixed some
> problems, nudging code paths around so a
From: David Brownell <[EMAIL PROTECTED]>
Date: Tue, 19 Feb 2008 16:19:54 -0800
> On Tuesday 19 February 2008, David Miller wrote:
> > From: Andre Tomt <[EMAIL PROTECTED]>
> > Date: Tue, 19 Feb 2008 16:19:08 +0100
> >
> > > Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
>
On Tuesday 19 February 2008, Andre Tomt wrote:
>
> > Can you try this diagnostic patch, to see if it reports any messages
> > about IAA and/or IAAD oddities? There's surely a quick workaround
> > for this, but I'd rather understand the root cause before patching.
>
> Doesn't seem to have trigger
On Tuesday 19 February 2008, David Miller wrote:
> From: Andre Tomt <[EMAIL PROTECTED]>
> Date: Tue, 19 Feb 2008 16:19:08 +0100
>
> > Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
> > not doing anything interesting at the time, but has its / and kernel on
> > a usb-stora
David Brownell wrote:
On Tuesday 19 February 2008, Andre Tomt wrote:
Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
not doing anything interesting at the time, but has its / and kernel on
a usb-storage device (usb pen drive).
Can you try this diagnostic patch, to see i
From: Andre Tomt <[EMAIL PROTECTED]>
Date: Tue, 19 Feb 2008 16:19:08 +0100
> Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
> not doing anything interesting at the time, but has its / and kernel on
> a usb-storage device (usb pen drive).
>
> Intel ICH8R chipset (and USB
Alan Stern wrote:
On Tue, 19 Feb 2008, Andre Tomt wrote:
Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
not doing anything interesting at the time, but has its / and kernel on
a usb-storage device (usb pen drive).
Intel ICH8R chipset (and USB controller), running x86_
On Tue, 19 Feb 2008, Andre Tomt wrote:
> Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
> not doing anything interesting at the time, but has its / and kernel on
> a usb-storage device (usb pen drive).
>
> Intel ICH8R chipset (and USB controller), running x86_64 kernel.
On Tuesday 19 February 2008, Andre Tomt wrote:
> Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
> not doing anything interesting at the time, but has its / and kernel on
> a usb-storage device (usb pen drive).
Can you try this diagnostic patch, to see if it reports any me
Got this on a serial console today, using 2.6.25-rc2-git1. Machine was
not doing anything interesting at the time, but has its / and kernel on
a usb-storage device (usb pen drive).
Intel ICH8R chipset (and USB controller), running x86_64 kernel. I'll
post .config and some additional info when
21 matches
Mail list logo