linux-kernel - Re: skge error; hangs w/ hardware memory hole

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: <44C317FF.8030705@suespammers.org>
Date:	Sun, 23 Jul 2006 02:32:31 -0400
From:	Anthony DeRobertis <asd@...spammers.org>
To:	Andreas Kleen <ak@...e.de>
CC:	Stephen Hemminger <shemminger@...l.org>,
	Martin Michlmayr <tbm@...ius.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, kevin@...experts.com
Subject: Re: skge error; hangs w/ hardware memory hole

Andreas Kleen wrote:

> 
> You need to use iommu=soft swiotlb=force
> 
> The standard IOMMU is also broken on VIA, but forced swiotlb should
> work.

Didn't work :-(

Excepts from the log:

Bootdata ok (command line is BOOT_IMAGE=2.6.17-1-smp ro root=902
iommu=soft swiotlb=force single)
...
skge eth0: enabling interface
skge 0000:00:0a.0: PCI error cmd=0x117 status=0x22b0
skge unable to clear error (so ignoring them)
skge eth0: Link is up at 1000 Mbps, full duplex, flow control tx and rx

And then the NIC didn't work. Attaching full dmesg.

View attachment "dmesg.0" of type "text/plain" (19390 bytes)