linux-kernel - swiotlb_alloc_coherent: allocated memory is out of range for device

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

Message-ID: <87d4hwuc9v.fsf@apollo.stackframe.org>
Date:	Sun, 19 Oct 2008 12:09:32 +0200
From:	Sven Schnelle <svens@...ckframe.org>
To:	linux-kernel@...r.kernel.org
Subject: swiotlb_alloc_coherent: allocated memory is out of range for device

Hi List,

my kernel dies while probing parport with the following last words:

[    3.672199] parport_pc 00:0b: reported by Plug and Play ACPI
[    3.677969] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
[    3.687691] hwdev DMA mask = 0x0000000000ffffff, dev_addr = 0x0000000020000000
[    3.694916] Kernel panic - not syncing: swiotlb_alloc_coherent: allocated memory is out of range for device

I haven't started a bisection yet, but this seems to be introduced
somewhere between 2.6.26 and 2.6.27, at least 2.6.26 was working without
problems. The dmesg log + config was obtained from a kernel compiled
from git on 10/16/2008.

I've attached the configuration + dmesg log to this mail. Board is an ASUS
DSBF-D12 with 2 E5410 Processors.

Cheers,

Sven.

View attachment "panic.log" of type "text/plain" (32007 bytes)

View attachment "config-2.6.27-smp" of type "text/plain" (56841 bytes)