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]

Date:	Thu, 21 Feb 2008 01:25:33 +0100
From:	Andre Tomt <andre@...t.net>
To:	David Brownell <david-b@...bell.net>
CC:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: USB OOPS 2.6.25-rc2-git1

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

OOPS'ed again after some hours. The OOPS looks identical to me besides 
all kind of other crap mixed in the trace due to a lot of unrelated 
activity going on.

Quite a lot of the same IAA messages (status 8029 and 8028, cmd 10021) 
in /var/log/debug prior to the crash, over the entire uptime time span.

This was with the first patch posted only. Not any of the other ones.

> 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.

It'll have to be tomorrow. Should I throw in the anti-oops patch too?
--
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/