Andrew Morton wrote:
> Peter Williams <pwil3058@bigpond.net.au> wrote:
> 
>>... at the the point indicated by the following output:
>>
>>[    8.197224] Freeing unused kernel memory: 288k freed
>>[    8.428217] SCSI subsystem initialized
>>[    8.510376] sym0: <810a> rev 0x23 at pci 0000:00:08.0 irq 11
>>[    8.587731] sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
>>[    8.671531] sym0: SCSI BUS has been reset.
>>[    8.725530] scsi0 : sym-2.2.1
>>[   17.256480]  0:0:0:0: ABORT operation started.
>>[   22.323534]  0:0:0:0: ABORT operation timed-out.
>>[   22.384348]  0:0:0:0: DEVICE RESET operation started.
>>[   27.458702]  0:0:0:0: DEVICE RESET operation timed-out.
>>[   27.527544]  0:0:0:0: BUS RESET operation started.
>>[   32.533775]  0:0:0:0: BUS RESET operation timed-out.
>>[   32.599173]  0:0:0:0: HOST RESET operation started.
>>[   32.669659] sym0: SCSI BUS has been reset.
>>
> 
> 
> Is there no response from sysrq-T?

Now that I've tried it there is a response.  I've attached the complete 
output from the boot including the sysrq-T output in the hang.output 
attachment to this e-mail.

> 
> Maybe adding initcall_debug to the boot command line will show extra info?
> 
> The .config would be useful, thanks.

Attached as origma.config.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce