On Wed, Mar 20, 2013 at 09:21:31AM -0700, Yinghai Lu wrote:
> On Wed, Mar 20, 2013 at 9:03 AM, Vivek Goyal wrote:
> > On Wed, Mar 20, 2013 at 08:53:29AM -0700, Yinghai Lu wrote:
> >> On Wed, Mar 20, 2013 at 6:08 AM, Vivek Goyal wrote:
> >>
> >> > Have a general question about crashkernel_low. Why
On Wed, Mar 20, 2013 at 9:03 AM, Vivek Goyal wrote:
> On Wed, Mar 20, 2013 at 08:53:29AM -0700, Yinghai Lu wrote:
>> On Wed, Mar 20, 2013 at 6:08 AM, Vivek Goyal wrote:
>>
>> > Have a general question about crashkernel_low. Why does it need to
>> > show up as "Crash kernel low" in /proc/iomem. Wi
On Wed, Mar 20, 2013 at 08:53:29AM -0700, Yinghai Lu wrote:
> On Wed, Mar 20, 2013 at 6:08 AM, Vivek Goyal wrote:
>
> > Have a general question about crashkernel_low. Why does it need to
> > show up as "Crash kernel low" in /proc/iomem. Will it not be better
> > that all memory reserved for crash
On Wed, Mar 20, 2013 at 6:08 AM, Vivek Goyal wrote:
> Have a general question about crashkernel_low. Why does it need to
> show up as "Crash kernel low" in /proc/iomem. Will it not be better
> that all memory reserved for crashkernel (whether high or low), shows
> as "Crash Kernel" and let kexec-
On Tue, Mar 19, 2013 at 08:05:26AM -0700, Yinghai Lu wrote:
> Chao said that kdump does does work well on his system on 3.8
> without extra parameter, even iommu does not work with kdump.
> And now have to append crashkernel_low=Y in first kernel to make
> kdump work.
>
> We have now modified cras
Chao said that kdump does does work well on his system on 3.8
without extra parameter, even iommu does not work with kdump.
And now have to append crashkernel_low=Y in first kernel to make
kdump work.
We have now modified crashkernel=X to allocate memory beyong 4G (if
available) and do not allocat
6 matches
Mail list logo