netdev - Re: [RFC] skge: limit DMA to 32 bit

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]

Date:	Tue, 21 Sep 2010 08:02:53 -0700
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] skge: limit DMA to 32 bit

On Tue, 21 Sep 2010 09:15:19 +0200
Stanislaw Gruszka <sgruszka@...hat.com> wrote:

> We have old fedora bug report about not working skge device on some
> Gigabyte motherboard:
> https://bugzilla.redhat.com/show_bug.cgi?id=447489
> 
> In dmesg there are messages:
> 
> skge 0000:02:0b.0: PCI error cmd=0x7 status=0x22b0
> skge 0000:02:0b.0: unable to clear error (so ignoring them)
> 
> Status value 0x22b0 include PCI_STATUS_REC_MASTER_ABORT bit set, what
> mean that DMA transfer on PCI bus was aborted.
> 
> I provided to user modified driver with module parameter, that allow
> to experiment with different dma_mask's. He told that maximum working 
> dma_mask for him is 32 bits set.
> 
> Is 32bit DMA limit for every skge device acceptable patch?

No. The device does support 64 bit DMA, the problem is a crap implementation
of the device the motherboard. Therefore a PCI quirk or module parameter
is a better solution.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html