This message has been generated automatically as a part of a summary report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.36.  Please verify if it still should be listed and let the tracking team
know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=25402
Subject		: kernel (2.6.37-8-generic_amd64) panic on boot (with message "map_single: bounce buffer is not DMA'ble) - possible regression !!!
Submitter	: carlos <carlos.palma@ono.com>
Date		: 2010-12-21 19:58 (9 days old)


--

[ message continues ]

I can confirm that this "regression" still exists with the kernel 
2.6.37-rc8.
The Call Trace is basically the same:

...
Kernel panic - not syncing: map_single ...
Pid 935, comm: NetworkManager Tainted
call trace
panic+oxbf/0x200
? default_spin_lock_flags+0x9/0x10
?swiotlb_tlb_map_single+0x1ce/0x250
?map_single+0x46/0x60
swiotlb_map_page+0xa6/0xf
... and then the FREEZE ... only a hard reset brings to live (with 
2.6.36-2) Linux.

carlos.



--

[ message continues ]

Thanks for the info.

Why did you put "regression" into double quotes?

Rafael
--

[ message continues ]

Because, at the beginning I tough it could be also a DELL firmware problem.
The 32 bit version works fine, the 64 bits under KVM works fine (tested 
with 1GB ram).
Only a few days ago I found similar problems also on DELL machines...
Happy new year

carlos



--

[ message continues ]