On Thursday, December 30, 2010, carlos palma wrote: > 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.
Thanks for the info. Why did you put "regression" into double quotes? Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
