Skip to contentSkip to conversation

stack trace immediately before rebooting/switching off

2.6.25-rc2 Andrey Borzenkov 3 participants 4 messages Feb 17, 2008 – Feb 18, 2008

lore
Share & tools
lore
#0 lore raw

In 2.6.25 I get stack trace immediately before system is switched off or reboots. It is too fast to capture it on VGA; netconsole does not capture it either - probably network is already shutdown at this point. I do not have serial port on this system.

Any idea how could I capture it? Thank you.

The problem did not exist in 2.6.24 and below.

-andrey

#1 lore raw
Quoted 8 lines · Andrey Borzenkov

In 2.6.25 I get stack trace immediately before system is switched off or reboots. It is too fast to capture it on VGA; netconsole does not capture it either - probably network is already shutdown at this point. I do not have serial port on this system.

Any idea how could I capture it? Thank you.

The problem did not exist in 2.6.24 and below.

Is this the e100 issue you reported later or something else?

Rafael

#2 lore raw
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Andrey Borzenkov

In 2.6.25 I get stack trace immediately before system is switched off or reboots. It is too fast to capture it on VGA; netconsole does not capture it either - probably network is already shutdown at this point. I do not have serial port on this system.

Quoted 6 lines
Quoted 3 lines

Any idea how could I capture it? Thank you.

The problem did not exist in 2.6.24 and below.

Is this the e100 issue you reported later or something else?

Well, I can't be entirely sure unless I have some way to capture this :)

#3 lore raw
In reply to Andrey Borzenkov
Quoted 9 lines · On Sun, 17 Feb 2008 15:16:53 +0300 Andrey Borzenkov <[email protected]> wrote:

In 2.6.25 I get stack trace immediately before system is switched off or reboots. It is too fast to capture it on VGA; netconsole does not capture it either - probably network is already shutdown at this point. I do not have serial port on this system.

Any idea how could I capture it? Thank you.

The problem did not exist in 2.6.24 and below.

- put an mdelay(100000) into sys_reboot() somewhere, take photo of screen

- try plain old /sbin/halt, see if that does it as well.