Lately, there have been reports of problems when using
the emu10k1 driver and a kernel compiled with HIGHMEM support.
I finally managed to observe the problem myself and basically this
e-mail is a request for help to try and solve this.
1. The problem is only observed when using a kernel compiled with
HIGHMEM support, even if actual RAM available is less than 1GiB
(192MiB in my case).
2. The emu10k1 uses DMA to get sound data from host memory.
3. DMA memory is allocated with pci_alloc_consistent (in
4. The emu10k1 reads some bytes from host memory and caches them
locally (up to 128 bytes). These can then be read back through PCI IO
registers (using inl()).
5. When I compare the values in host memory to the ones read by the card
_some times_ they are different (all of the 128 bytes read). The values
read by the card are usually zero when this happens.
6. Once the problem starts if I start/stop the same sound application
(freeing and then allocating the same DMA memory pages) the problem
persists. If I stop the application, start another one (with a
different buffer usually allocating more memory), stop it, go
back to the initial one, the problem is gone.
At the hardware level what is the difference between a kernel with
HIGHMEM support and one without? I see that the physical/virtual
addresses of the pages obtained with pci_alloc_consistent are within
the same range...
If it's a bug in the driver why would it only show up some times and
only if HIGHMEM support is enabled?
Thanks for any help,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 07 2002 - 21:00:27 EST