linux-kernel - Re: [BUG, bisected] atmel_spi: hard lockups in transfer

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: <ac67d9130804061724v74856a30ta8b128cc5b69cf80@mail.gmail.com>
Date:	Mon, 7 Apr 2008 02:24:04 +0200
From:	"Szilveszter Ordog" <slipszi@...il.com>
To:	"Ben Nizette" <bn@...sdigital.com>
Cc:	kernel <kernel@...32linux.org>,
	"Haavard Skinnemoen" <hskinnemoen@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG, bisected] atmel_spi: hard lockups in transfer

>  For some weeks now there have been reports flying across the main AVR32
>  support forum, avrfreaks [1], that atmel_spi now hard-hangs on most
>  transfers.  The behaviour is not apparent in .23 and is in .24+.  One
>  tester was good enough to bisect the problem and turned up
>
>  154443c72f47169ebcb3a7befbff0e934c49bff3
>  atmel_spi: chain DMA transfers
>
>  as the culprit.

Thanks for reporting this. Unfortunately it is difficult to test for
me, since I do not have the hardware and there are no error messages.
However, if you add the following line

#define DEBUG

to the top of drivers/spi/atmel_spi.c (before the #include directives)
and recompile the kernel, then you would get lots of debug output
which could help us pinpoint the problem.

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