linux-kernel - Re: USB OOPS 2.6.25-rc2-git1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200802201324.37519.david-b@pacbell.net>
Date:	Wed, 20 Feb 2008 13:24:36 -0800
From:	David Brownell <david-b@...bell.net>
To:	Andre Tomt <andre@...t.net>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: USB OOPS 2.6.25-rc2-git1

On Wednesday 20 February 2008, Andre Tomt wrote:
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8028 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8028 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8028 cmd 10021
> ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021

... etc.

OK, the relevant bits are:

   status  0001 == some transaction completed normally (ignored here)
   status  0020 == IAA set, which should have triggered an IRQ
   command 0040 == IAAD clear, meaning IAA should have triggered

Meaning the hardware is misbehaving in a "traditional" way, one
that the watchdog is supposed to catch:  IAA set, but no IRQ.

If you see any "IAA" messages *other* than those, please report
them ASAP.  They'll indicate "nontraditional" misbehavior.

> 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, or that your
oops re-appears, I'll submit some version of this patch for RC3.

And if you're up for it, I may have another patch for you
to try on top of this one ... I had an idea about IRQ trigger
modes that might be causing this problem.

- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/