Modify

Opened 4 years ago

Last modified 2 years ago

#15113 new defect

ath9k could not alloc dma memory

Reported by: anonymous Owned by: developers
Priority: highest Milestone:
Component: kernel Version: Trunk
Keywords: ath9k, alloc_safe_buffer Cc:

Description

If I create a single monitor interface with the ath9k driver the moment I bring up the interface I get the following output:

[   63.397455] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73f8040!
[   63.404970] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)
[   63.413167] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73f8900!
[   63.420672] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)
[   63.428870] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73f91c0!
[   63.436387] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)
[   63.444589] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73f9a80!
[   63.452104] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)
[   63.460280] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73fa340!
[   63.467806] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)
[   63.476002] ath9k 0000:00:04.0: map_single: unable to map unsafe buffer c73fac00!
[   63.483517] ath9k 0000:00:04.0: alloc_safe_buffer: could not alloc dma memory (size=1926)

This is from the latest git revision on an ixp4xx target (gateworks cambria).

Attachments (0)

Change History (2)

comment:1 Changed 4 years ago by anonymous

I found this old post on the forum:

https://forum.openwrt.org/viewtopic.php?id=24155

It basically suggest to enable >64MB memory support in kernel:

make kernel_menuconfig

and choose

System Type -> 'INtel IXP4xx Implementation Options -> Support > 64MB RAM

However this flag does not seem to exist int he current kernel 3.10.32

R.

comment:2 Changed 2 years ago by mbilloo

I think the option you're looking for is "Use indirect PCI memory access" in System Type > Intel IXP4xx Implementation Options under IXP4xx Options. However, this will result in a performance hit and you can't mmap the PCI devices. See the help of this option for more info.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.