linux-kernel - Re: Endless loop with "detected XactErr"

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] [day] [month] [year] [list]

Date:	Fri, 8 Apr 2011 12:32:12 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Zdenek Kabelac <zdenek.kabelac@...il.com>
cc:	USB list <linux-usb@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Endless loop with "detected XactErr"

On Fri, 8 Apr 2011, Zdenek Kabelac wrote:

> > You might want to track down the original source of the
> > underlying error.  Since the machine was docked the entire time, the
> > line saying:
> >
> > [ �473.873802] ACPI: \_SB_.GDCK - undocking
> >
> > definitely looks suspicious.  I bet if you can fix that then the USB
> > problems will go away.
> 
> Hmm looking now into more logs - it might have been used this:
> 
> "echo 1 >/sys/devices/platform/dock.0/undock"
> 
> for this particular testcase  - I might have been checking several
> combination and making modification of some pm script for this.
> So yes - in this case the machine could have been undocked by the above command.
> 
> Is that a major problem for USB ?

Not normally, but maybe the software undock didn't work correctly.

Or maybe it did work.  What happens if you disable CONFIG_USB_DEBUG?

Alan Stern

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