Re: Missing dmesg parameters in 2.6.19.2

Re: Missing dmesg parameters in 2.6.19.2

[Robert Hancock]

Sunil Naidu wrote:
> Hello All,
> 
> Atlast I have succeeded in booting 2.6.19.2 on mutiple x86 machines. I
> did observe a strange dmesg parameter behavior in this case:-
> 
> 
> 1) Compiling with SMP as Generic (CONFIG_X86_PC is not set, CONFIG_M686=y)
> 
> ........
> ........
> Using x86 segment limits to approximate NX protection
> ........
> ........
> Using APIC driver default
> ........
> ........
> 
> 2) Compiling with SMP as Processor specific (CONFIG_X86_PC=y,
> CONFIG_MPENTIUM4=y)
> 
> I do not find the above mentioned parameters in this case.

I don't think the "segment limits" message shows up in stock kernels, 
are you sure that was from 2.6.19.2? That sounds like a Fedora kernel 
with Exec Shield.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

Re: Missing dmesg parameters in 2.6.19.2

[Sunil Naidu]

On 1/20/07, Robert Hancock <hancockr@shaw.ca> wrote:
> > 1) Compiling with SMP as Generic (CONFIG_X86_PC is not set, CONFIG_M686=y)
> >
> > ........
> > ........
> > Using x86 segment limits to approximate NX protection
> > ........
> > ........
> > Using APIC driver default
> > ........
> > ........
> >
> > 2) Compiling with SMP as Processor specific (CONFIG_X86_PC=y,
> > CONFIG_MPENTIUM4=y)
> >
> > I do not find the above mentioned parameters in this case.
>
> I don't think the "segment limits" message shows up in stock kernels,
> are you sure that was from 2.6.19.2? That sounds like a Fedora kernel
> with Exec Shield.
>
> --
> Robert Hancock      Saskatoon, SK, Canada

I am very sorry, have lost my mind with the night out with these
kernels (messed up).

Yep, you are right. Case 1 is FC6 kernel. Case 2 is my customization
with 2.6.19.2. I was thinking about APIC in Case 2....


~Akula2

Missing dmesg parameters in 2.6.19.2

[Sunil Naidu]

Hello All,

Atlast I have succeeded in booting 2.6.19.2 on mutiple x86 machines. I
did observe a strange dmesg parameter behavior in this case:-


1) Compiling with SMP as Generic (CONFIG_X86_PC is not set, CONFIG_M686=y)

.........
.........
Using x86 segment limits to approximate NX protection
.........
.........
Using APIC driver default
.........
.........

2) Compiling with SMP as Processor specific (CONFIG_X86_PC=y,
CONFIG_MPENTIUM4=y)

I do not find the above mentioned parameters in this case.


I am trying to figure out what might have happened here? Any clues pl...


Thanks,

~Akula2