I tried to upgrade one of our ooooold machines
(used as print servers and similar tasks) today
from 2.6.22 to 2.6.23[.9]. The same config (with
minor tweaks for new options), i486 base arch,
X86_GENERIC=y.
The result is immediately machine reboot right
after bootloader (etherboot) passes control to
the kernel -- BEFORE "Uncompressing linux"
message.
2.6.22 worked just fine.
So I wonder if it's supposed to work in the first
place. The thing is that this machine(s) are very
slow to boot, so trying to figure out which change
is at question will require quite some time...
Thanks.
/mjt
Michael Tokarev wrote:
> I tried to upgrade one of our ooooold machines
> (used as print servers and similar tasks) today
> from 2.6.22 to 2.6.23[.9]. The same config (with
> minor tweaks for new options), i486 base arch,
> X86_GENERIC=y.
>
> The result is immediately machine reboot right
> after bootloader (etherboot) passes control to
> the kernel -- BEFORE "Uncompressing linux"
> message.
>
> 2.6.22 worked just fine.
>
> So I wonder if it's supposed to work in the first
> place. The thing is that this machine(s) are very
> slow to boot, so trying to figure out which change
> is at question will require quite some time...
It looks like 2.6.23.9 is missing checkin
7ed192906a2144ebc8ca2925a85d27b9c5355668 from Linus' tree (attached),
which is necessary to work on 386 and 486.
-hpa
H. Peter Anvin wrote:
> Michael Tokarev wrote:
[2.6.23 on an i486 machine]
>> The result is immediately machine reboot right
>> after bootloader (etherboot) passes control to
>> the kernel -- BEFORE "Uncompressing linux"
>> message.
>>
>> 2.6.22 worked just fine.
[]
> It looks like 2.6.23.9 is missing checkin
> 7ed192906a2144ebc8ca2925a85d27b9c5355668 from Linus' tree (attached),
> which is necessary to work on 386 and 486.
Well, I applied the patch (in 2.6.23 it's
arch/i386/boot/pmjump.S,
not
arch/x86/boot/pmjump.S,
but that's minor) - still the same behavior, it still reboots
instantly right when bootloader gave control to the kernel.
So it must be something else.. ;)
I'll try other kernels tomorrow, given some time (I already
spent almost the whole day today with this "machine"). This
whole story prompted me to just throw those machines away and
replace them with tiny devices (a small print server in this
case). There are still several 486-class machines out there...
By the way, this very machine I'm experimenting with is a
strange beast by itself. For example, etherboot does not
work on it properly, anything since version 5.1.0 just
freezes right after displaying the "greeting" message.
5.0.11 works. However till now, linux worked on it just
fine, -- unlike etherboot.
Thanks!
/mjt
Michael Tokarev wrote:
>> It looks like 2.6.23.9 is missing checkin
>> 7ed192906a2144ebc8ca2925a85d27b9c5355668 from Linus' tree (attached),
>> which is necessary to work on 386 and 486.
>
> Well, I applied the patch (in 2.6.23 it's
> arch/i386/boot/pmjump.S,
> not
> arch/x86/boot/pmjump.S,
> but that's minor) - still the same behavior, it still reboots
> instantly right when bootloader gave control to the kernel.
> So it must be something else.. ;)
Well, it's a good bet it's croaking somewhere in the setup code
(arch/{i386,x86}/boot). Putting debugging statements there might help.
-hpa
> Well, I applied the patch (in 2.6.23 it's
> arch/i386/boot/pmjump.S,
> not
> arch/x86/boot/pmjump.S,
> but that's minor) - still the same behavior, it still reboots
> instantly right when bootloader gave control to the kernel.
> So it must be something else.. ;)
It should be x86, they merged the i386 and x86_64 code into one arch
called x86. Try it again and see if it works
Thanks,
- Jerry