Mailing List Archive: Linux: Kernel

Missing dmesg parameters in 2.6.19.2

Index | Next | Previous | View Threaded

akula2.shark at gmail

Jan 19, 2007, 6:50 PM

Post #1 of 3 (222 views)
Permalink

Missing dmesg parameters in 2.6.19.2

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

hancockr at shaw

Jan 19, 2007, 7:15 PM

Post #2 of 3 (199 views)
Permalink

Re: Missing dmesg parameters in 2.6.19.2 [In reply to]

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 [at] nospamshaw
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

akula2.shark at gmail

Jan 19, 2007, 7:54 PM

Post #3 of 3 (212 views)
Permalink

Re: Missing dmesg parameters in 2.6.19.2 [In reply to]

On 1/20/07, Robert Hancock <hancockr [at] shaw> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads