Chris Ridd wrote: > > I'm still unsure how to extract extra diagnostics from a wedged system > via a serial console. One of the advantages of the serial console is it runs at a higher priority (usually IPL 12) which allows it to still work when a lower priority driver is stuck in its interrupt code. Have you tried booting the debugger by adding the options " -Bconsole=ttya -kd" to the kernel line in grub? > > However I have since forced the box to boot this BE (111b) with a > 32-bit kernel - it only has 3GB of RAM anyway - and so far things have > been fine... Is the time to failure short enough to believe the issue is unique to booting 64-bit?
- [xwin-discuss] Nvidia driver wedges entire machine in snv_111 Chris Ridd
- [xwin-discuss] Nvidia driver wedges entire machine in snv... John Martin
- [xwin-discuss] Nvidia driver wedges entire machine in... Chris Ridd
- [xwin-discuss] Nvidia driver wedges entire machine in... Chris Ridd
- [xwin-discuss] Nvidia driver wedges entire machin... John Martin
- [xwin-discuss] Nvidia driver wedges entire ma... Chris Ridd
- [xwin-discuss] Nvidia driver wedges enti... John Martin
- [xwin-discuss] Nvidia driver wedges ... Chris Ridd
- [xwin-discuss] Nvidia driver wed... Chris Ridd
- [xwin-discuss] Nvidia driver wed... Chris Ridd
- [xwin-discuss] Nvidia driver wed... John Martin
- [xwin-discuss] Nvidia driver wed... Chris Ridd
- [xwin-discuss] Nvidia driver wed... Chris Ridd
