Skip to contentSkip to conversation

apparent sn_console deadlock

DISCUSSION William Lee Irwin III 2 participants 3 messages Aug 3, 2004

lore
Share & tools
lore
#0 lore raw

I seem to be having trouble around the switchover from sal_console_early to sal_console on an Altix with 2.6.8-rc2-mm2. As I've been out of the ia64 loop for a while, I figured it might be good to check in and see if this is a known issue or some easily-recognizable gaffe before going through too much trouble to debug it.

The apparent failure mode is some kind of deadlock and/or loss of console output. Userspace doesn't make progress to normal booting (as it would if the console were merely misdirected), though it's not directly observable. system logs and other indicators show no trace of userspace having run on 2.6.8-rc2-mm2.

Bootlog (altix.log.7.gz) and .config attached. Also attached is a bootlog from a small attempt not to switch out of sal_console_early (altix.log.9.gz) i.e. bailing out of sn_sal_serial_console_init() immediately without registering or unregistering consoles or doing anything.

Thanks.

-- wli

#1 lore raw
Quoted 12 lines · William Lee Irwin III

I seem to be having trouble around the switchover from sal_console_early to sal_console on an Altix with 2.6.8-rc2-mm2. As I've been out of the ia64 loop for a while, I figured it might be good to check in and see if this is a known issue or some easily-recognizable gaffe before going through too much trouble to debug it.

The apparent failure mode is some kind of deadlock and/or loss of console output. Userspace doesn't make progress to normal booting (as it would if the console were merely misdirected), though it's not directly observable. system logs and other indicators show no trace of userspace having run on 2.6.8-rc2-mm2.

Quoted 5 lines

Bootlog (altix.log.7.gz) and .config attached. Also attached is a bootlog from a small attempt not to switch out of sal_console_early (altix.log.9.gz) i.e. bailing out of sn_sal_serial_console_init() immediately without registering or unregistering consoles or doing anything.

Your first log indicates that you're passing 'console=ttyS0' to the kernel at boot time. As of 2.6.8-rc2 (IIRC) you need to pass 'console=ttySG0' instead. You'll also want to create a new character device, /dev/ttySG0 with major 204, minor 40.

I wasn't able to see the config file you attached, but I think you've correctly turned on the SGI L1 console support (in the serial drivers section of the character devices menu of Kconfig).

Jesse

#2 lore raw
In reply to William Lee Irwin III
Quoted 5 lines · William Lee Irwin III
Quoted 5 lines

Bootlog (altix.log.7.gz) and .config attached. Also attached is a bootlog from a small attempt not to switch out of sal_console_early (altix.log.9.gz) i.e. bailing out of sn_sal_serial_console_init() immediately without registering or unregistering consoles or doing anything.

Quoted 7 lines · Jesse Barnes

Your first log indicates that you're passing 'console=ttyS0' to the kernel at boot time. As of 2.6.8-rc2 (IIRC) you need to pass 'console=ttySG0' instead. You'll also want to create a new character device, /dev/ttySG0 with major 204, minor 40.
I wasn't able to see the config file you attached, but I think you've correctly turned on the SGI L1 console support (in the serial drivers section of the character devices menu of Kconfig).

After console=ttySG0, making the device node, and removing the debug hack of keeping the early SAL console, everything works now.

Thanks.

-- wli