This bug was fixed in the package linux - 2.6.24-12.18
---
linux (2.6.24-12.18) hardy; urgency=low
[Amit Kucheria]
* Move Marvell 8686 and 8688 to LUM
* Poulsbo: Sync patches with moblin/ume-hardy tree
* Break if a patch fails to apply
* SAUCE: implement smarter atime
Applied back ported patch
http://bugs.gentoo.org/attachment.cgi?id=143585
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled
with warnings
https://bugs.launchpad.net/bugs/194207
You received
Yeah I am still using the machines in question for pretty heavy I/O load
(they are dedicated storage servers for an OpenVZ cluster). They are
running RAID5 from the card. Can't remember the specs on it, if I could
run the CLI tool I would tell you. But its a definite regression in that
if the CLI
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Colin King
(colin-king)
Status: Triaged = In Progress
--
arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled
with warnings
https://bugs.launchpad.net/bugs/194207
You
have become unusable in 2.6.24.
Besides the annoying warning, what else goes wrong? (I recently reported
duplicate bug #197982)
--
arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled
with warnings
https://bugs.launchpad.net/bugs/194207
You received this bug
The flood of kernel warnings will hang your machine given a large enough
I/O load... we currently need to kill klogd to keep our machines running
for any longer period of time.
--
arcmsr + archttp64 calls dma_free_coherent() with irqs disabled - dmesg filled
with warnings
That's interesting; I only get the warning when I run the cli64 tool
to query drive status. Regular use of the SATA controller doesn't
trigger any warnings for me, no matter what the load. Probably the
difference is in how we are utilizing the Areca card; I'm just using
a simple passthrough mode
Thanks Dave,
I'm just updating this report with the upstream git commit id and
summary for the patch to resolve this. Thanks.
commit 69e562c234440fb7410877b5b24f4b29ef8521d1
Author: Daniel Drake [EMAIL PROTECTED]
Date: Wed Feb 20 13:29:05 2008 +
[SCSI] arcmsr: fix message allocation
