Re: [cooker-amd64] 2.6 custom kernel, now compiled and working here, but issues..

[Gwenole Beauchesne]

On Wed, 28 Jan 2004, Duncan wrote:

> I now have a 2.6 custom (naturally, since I've not found an amd64
> Mdk kernel package out yet) kernel up and running

I am working on it now that glibc + NPTL fully built at last. ;-)

Don't be impatient I am currently under medecine (sh*ty weather) and I
noticed I wrote some weird things at times, so don't be scared if there 
are missing words in this mail. ;-)

> 1)  Question: Kernel package differences
> 
> What are the current differences between the regular 2.6.x mdk kernel, the
> mdk-tmb version, and the vanilla Linus/AM version? Now that I started with
> the std mdk one and know SOME 2.6 kernel works,

You will always want additional patches from amd64.org.

> 2)  Question:  Compile process warnings, specifically cast
> 
> With the 2.6 kernel compile process far quieter than 2.4, any warnings
> stick out far more.  In particular, I noticed several cast pointer/init
> warnings, which could be VERY significant for AMD64. Are all these
> warnings critical bugs waiting to cause a kernel panic, or are there cases
> where they can be safely ignored without issue?

Some can be safely ignored. Read the code to be sure.

> Should I be sure and report those warnings as a bug?  If so, where?  
> File them in MDK-bugzilla? Send them to the official kernel folks (or
> module/subsystem maintainer)?  Just post them here and ask how serious
> they are?  Mail them to GB? <g>

Juan already is already taken of them in his spare time when x86 is OK.
;-)  Now, if this is a serious problem and a real and reproducable one
with proper hardware, it can be fixed. I generally disable well known
non-64bit clean drivers.

> 2a)  Question:  Compile process warning error dump?
> 
> Does there happen to be a convenient dump of such warnings
> from a compile, that I can scrape them out of, or do I need to redirect
> the compile output to a file or screen-scrape manually?  (That one feels
> newbie-ish, but hey.. <g>)

I usually rpm -ba kernel-2.x.spec >& build.log in a screen, and tail -f
for continuous output.