Hi Alan,
Actually this problem started with ac2. All seems to work well until I
reboot the machine with 'shutdown' or 'reboot' or 'ctl-alt-del'.
The machine shuts down properly to the point where all filesystems
are remounted readonly, which is the point where I normally see an
immediate reboot. Starting with pre4-ac2 I just get an indefinite
hang instead of the reboot.
The terminal driver still seems to work because I can use the
ctl-alt-Fx keys to switch to other pseudo-terminals but the login
process is already gone so I can't actually do anything at the
login prompts. It takes a hard reset to complete the reboot,
after which the machine comes up normally with clean filesystems.
I see this on three different machines with different motherboards
and CPU's [K6-2, athlon, athlon-xp], two VIA chipsets and one SiS.
No error messages print anywhere, so I'm not sure how to debug.
Do you need a kernel config file or dmesg output?
You're not the only one hitting this. My symptoms seam identicle to
yours.
What do you notice about the order of messages in relationship to how
they were ordered pre 2.4.21-pre4-ac2? Before I would see all the
shutdown messages then "flushing ide" then the reboot or power down
message. Now the reboot or power down message shows up before or
durring the md raid device shutdown. Then I get the flushing ide
mesasage and it dies part way through.
walt wrote:
> Hi Alan,
>
> Actually this problem started with ac2. All seems to work well until I
> reboot the machine with 'shutdown' or 'reboot' or 'ctl-alt-del'.
>
> The machine shuts down properly to the point where all filesystems
> are remounted readonly, which is the point where I normally see an
> immediate reboot. Starting with pre4-ac2 I just get an indefinite
> hang instead of the reboot.
>
> The terminal driver still seems to work because I can use the
> ctl-alt-Fx keys to switch to other pseudo-terminals but the login
> process is already gone so I can't actually do anything at the
> login prompts. It takes a hard reset to complete the reboot,
> after which the machine comes up normally with clean filesystems.
>
> I see this on three different machines with different motherboards
> and CPU's [K6-2, athlon, athlon-xp], two VIA chipsets and one SiS.
>
> No error messages print anywhere, so I'm not sure how to debug.
> Do you need a kernel config file or dmesg output?
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Mon, 2003-02-10 at 17:33, walt wrote:
> Hi Alan,
>
> Actually this problem started with ac2. All seems to work well until I
> reboot the machine with 'shutdown' or 'reboot' or 'ctl-alt-del'.
>
> The machine shuts down properly to the point where all filesystems
> are remounted readonly, which is the point where I normally see an
> immediate reboot. Starting with pre4-ac2 I just get an indefinite
> hang instead of the reboot.
I know about it, I've not yet had time to track it down
The fix in patch-2.4.21-pre4-ac4 looks like it works to remove the
reboot hang. I ran it thourgh a few reboots to test. Thanks.
As a side note I still see the "Rebooting..." message before the md:
messages.
- Bryan
Alan Cox wrote:
> On Mon, 2003-02-10 at 17:33, walt wrote:
>>Actually this problem started with ac2. All seems to work well until I
>>reboot the machine with 'shutdown' or 'reboot' or 'ctl-alt-del'.
>>
>>The machine shuts down properly to the point where all filesystems
>>are remounted readonly, which is the point where I normally see an
>>immediate reboot. Starting with pre4-ac2 I just get an indefinite
>>hang instead of the reboot.