On Fri, Jan 4, 2013 at 1:02 PM, Shuah Khan <shuahk...@gmail.com> wrote: > Pani'cing the system doesn't sound like a good option to me in this > case. This change to disable swiotlb is made for kdump. However, with > this change several system fail to boot, unless crashkernel_low=72M is > specified.
this patchset is new feature to put second kdump kernel above 4G. > > I would the say the right approach to solve this would be to not > change the current pci_swiotlb_detect_override() behavior and treat > swiotlb =1 upon entry equivalent to swiotlb_force set. that will make intel system have to take crashkernel_low=72M too. otherwise intel system will get panic during swiotlb allocation. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/