* Re: Missing dmesg parameters in 2.6.19.2
[not found] <fa.fNZG37ToxSA055/pURYuraLOnPA@ifi.uio.no>
@ 2007-01-20 3:15 ` Robert Hancock
2007-01-20 3:54 ` Sunil Naidu
0 siblings, 1 reply; 3+ messages in thread
From: Robert Hancock @ 2007-01-20 3:15 UTC (permalink / raw)
To: Sunil Naidu; +Cc: linux-kernel
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/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Missing dmesg parameters in 2.6.19.2
2007-01-20 3:15 ` Missing dmesg parameters in 2.6.19.2 Robert Hancock
@ 2007-01-20 3:54 ` Sunil Naidu
0 siblings, 0 replies; 3+ messages in thread
From: Sunil Naidu @ 2007-01-20 3:54 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Missing dmesg parameters in 2.6.19.2
@ 2007-01-20 2:50 Sunil Naidu
0 siblings, 0 replies; 3+ messages in thread
From: Sunil Naidu @ 2007-01-20 2:50 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-01-20 3:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <fa.fNZG37ToxSA055/pURYuraLOnPA@ifi.uio.no>
2007-01-20 3:15 ` Missing dmesg parameters in 2.6.19.2 Robert Hancock
2007-01-20 3:54 ` Sunil Naidu
2007-01-20 2:50 Sunil Naidu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox