* 2.6.18-mm1 make oldconfig missed SATA
@ 2006-09-24 23:00 Grant Coady
2006-09-25 0:12 ` Jeff Garzik
0 siblings, 1 reply; 6+ messages in thread
From: Grant Coady @ 2006-09-24 23:00 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: linux-kernel
Hi there,
2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
the new libata screen, caught me out -- this may be an issue for 2.6.19
upgraders that a quick make oldconfig rebuild will fail to boot?
Grant.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.18-mm1 make oldconfig missed SATA
2006-09-24 23:00 2.6.18-mm1 make oldconfig missed SATA Grant Coady
@ 2006-09-25 0:12 ` Jeff Garzik
2006-09-25 0:38 ` Valdis.Kletnieks
2006-09-25 1:24 ` Grant Coady
0 siblings, 2 replies; 6+ messages in thread
From: Jeff Garzik @ 2006-09-25 0:12 UTC (permalink / raw)
To: Grant Coady; +Cc: Sam Ravnborg, linux-kernel
Grant Coady wrote:
> 2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
> the new libata screen, caught me out -- this may be an issue for 2.6.19
> upgraders that a quick make oldconfig rebuild will fail to boot?
The symbols changed. No facility for upgrading .config symbols...
people who config their own kernels are expected to handle such things...
Jeff
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.18-mm1 make oldconfig missed SATA
2006-09-25 0:12 ` Jeff Garzik
@ 2006-09-25 0:38 ` Valdis.Kletnieks
2006-09-25 9:25 ` Michael Tokarev
2006-09-25 1:24 ` Grant Coady
1 sibling, 1 reply; 6+ messages in thread
From: Valdis.Kletnieks @ 2006-09-25 0:38 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Grant Coady, Sam Ravnborg, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Sun, 24 Sep 2006 20:12:10 EDT, Jeff Garzik said:
> Grant Coady wrote:
> > 2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
> > the new libata screen, caught me out -- this may be an issue for 2.6.19
> > upgraders that a quick make oldconfig rebuild will fail to boot?
>
> The symbols changed. No facility for upgrading .config symbols...
> people who config their own kernels are expected to handle such things...
I remember getting hit with this several times in the last few -mm's as I
did bisecting and kept crossing over the patch that did that. Fortunately,
'make oldconfig' was nice enough to keep me honest and prompt me for the new
symbol names.
What the Kbuild system *could* use is, for the end of 'make oldconfig', a
report like this for 'y' or 'm' symbols that have evaporated:
The following enabled symbols found in the .config were not defined in any Kconfig file:
CONFIG_FROOBY
CONFIG_DEBUG_FROOBY
So people aren't totally mystified Admittedly, I've only gotten bit by
silently dissapearing symbols 4-5 times since 2.5.55 or so, but the times
it happened it would have been nice to know....
(OK, I admit it - at least once of those 4-5 times it was because I ran
'make oldconfig' and I hadn't applied a local patch that added a Kconfig option.
Even in that case, a "Yo, dood, something went poof" msg would have saved me
a lot of bang-head-against-wall debugging. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.18-mm1 make oldconfig missed SATA
2006-09-25 0:12 ` Jeff Garzik
2006-09-25 0:38 ` Valdis.Kletnieks
@ 2006-09-25 1:24 ` Grant Coady
1 sibling, 0 replies; 6+ messages in thread
From: Grant Coady @ 2006-09-25 1:24 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Grant Coady, Sam Ravnborg, linux-kernel
On Sun, 24 Sep 2006 20:12:10 -0400, Jeff Garzik <jeff@garzik.org> wrote:
>Grant Coady wrote:
>> 2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
>> the new libata screen, caught me out -- this may be an issue for 2.6.19
>> upgraders that a quick make oldconfig rebuild will fail to boot?
>
>The symbols changed. No facility for upgrading .config symbols...
>people who config their own kernels are expected to handle such things...
Oh sure, way back I used to run `make oldconfig; make menuconfig` and check
the config -- I guess complacency sets in and it is a ((Surprise!))
Grant.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.18-mm1 make oldconfig missed SATA
2006-09-25 0:38 ` Valdis.Kletnieks
@ 2006-09-25 9:25 ` Michael Tokarev
2006-09-25 13:31 ` Valdis.Kletnieks
0 siblings, 1 reply; 6+ messages in thread
From: Michael Tokarev @ 2006-09-25 9:25 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Jeff Garzik, Grant Coady, Sam Ravnborg, linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Sun, 24 Sep 2006 20:12:10 EDT, Jeff Garzik said:
>> Grant Coady wrote:
>>> 2.6.18-mm1 make oldconfig didn't pull SATA config from 2.6.18 old screen to
>
>>> the new libata screen, caught me out -- this may be an issue for 2.6.19
>>> upgraders that a quick make oldconfig rebuild will fail to boot?
>> The symbols changed. No facility for upgrading .config symbols...
>> people who config their own kernels are expected to handle such things...
>
> I remember getting hit with this several times in the last few -mm's as I
> did bisecting and kept crossing over the patch that did that. Fortunately,
> 'make oldconfig' was nice enough to keep me honest and prompt me for the new
> symbol names.
>
> What the Kbuild system *could* use is, for the end of 'make oldconfig', a
> report like this for 'y' or 'm' symbols that have evaporated:
>
> The following enabled symbols found in the .config were not defined in any Kconfig file:
> CONFIG_FROOBY
> CONFIG_DEBUG_FROOBY
>
> So people aren't totally mystified Admittedly, I've only gotten bit by
> silently dissapearing symbols 4-5 times since 2.5.55 or so, but the times
> it happened it would have been nice to know....
It already does that, but prints them in the beginning, not after config.
Try make silentoldconfig and see the first screen of warnings when it will
ask the first question.
/mjt
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.18-mm1 make oldconfig missed SATA
2006-09-25 9:25 ` Michael Tokarev
@ 2006-09-25 13:31 ` Valdis.Kletnieks
0 siblings, 0 replies; 6+ messages in thread
From: Valdis.Kletnieks @ 2006-09-25 13:31 UTC (permalink / raw)
To: Michael Tokarev; +Cc: Jeff Garzik, Grant Coady, Sam Ravnborg, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Mon, 25 Sep 2006 13:25:54 +0400, Michael Tokarev said:
> Valdis.Kletnieks@vt.edu wrote:
> > So people aren't totally mystified Admittedly, I've only gotten bit by
> > silently dissapearing symbols 4-5 times since 2.5.55 or so, but the times
> > it happened it would have been nice to know....
>
> It already does that, but prints them in the beginning, not after config.
Damn, I *never* noticed, because it was scrolled away. ;)
> Try make silentoldconfig and see the first screen of warnings when it will
> ask the first question.
I saw the recent help patches for that - how long has it been in there and I
didn't notice? (Though I admit I say that one and just moved along, thinking
that it was an upstream push of RedHat's linux-2.6-build-nonintconfig.patch
they carry in Fedora, but actually *looking* at that patch, it's something
different).
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-09-25 13:32 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-09-24 23:00 2.6.18-mm1 make oldconfig missed SATA Grant Coady
2006-09-25 0:12 ` Jeff Garzik
2006-09-25 0:38 ` Valdis.Kletnieks
2006-09-25 9:25 ` Michael Tokarev
2006-09-25 13:31 ` Valdis.Kletnieks
2006-09-25 1:24 ` Grant Coady
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®