linux-kernel - Re: [Bug #25402] kernel (2.6.37-8-generic_amd64) panic on boot (with message "map_single: bounce buffer is not DMA'ble)

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: <201012302351.48156.rjw@sisk.pl>
Date:	Thu, 30 Dec 2010 23:51:48 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	carlos palma <carlos.palma@....com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Florian Mickler <florian@...kler.org>
Subject: Re: [Bug #25402] kernel (2.6.37-8-generic_amd64) panic on boot (with message "map_single: bounce buffer is not DMA'ble) - possible regression !!!

On Thursday, December 30, 2010, carlos palma wrote:
> I can confirm that this "regression" still exists with the kernel 
> 2.6.37-rc8.
> The Call Trace is basically the same:
> 
> ...
> Kernel panic - not syncing: map_single ...
> Pid 935, comm: NetworkManager Tainted
> call trace
> panic+oxbf/0x200
> ? default_spin_lock_flags+0x9/0x10
> ?swiotlb_tlb_map_single+0x1ce/0x250
> ?map_single+0x46/0x60
> swiotlb_map_page+0xa6/0xf
> ... and then the FREEZE ... only a hard reset brings to live (with 
> 2.6.36-2) Linux.

Thanks for the info.

Why did you put "regression" into double quotes?

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