I'm using kernel version 2.0.36-pre-patch-9
I am able to lock up my system and it appears to be looping in scsi.c - in
allocate_device.
I do this by using the script
#!/bin/sh
#
dd if=/dev/scd3 /dev/null &
#sleep 1
dd if=/dev/scd4 /dev/null &
(uncommenting the sleep 1 stops the lock up)
I can only change vc's and use ctl/alt/shft:scroll-lock. ctl-alt-del does
not work and I cannot type any characters. I need to use the big-red-button
to reboot.
Using alt/scroll-lock gives the following EIP values:
EIP 0010:[<001aedd8>]
[<001aee07>]
[<001aee8d>]
[<001aedf0>]
[<001aedc7>]
[<001aee1f>]
[<001aede0>]
[<001aee1b>]
[<001aee12>]
[<001aede8>]
[<001aedf9>]
[<001aee8d>]
[<001aedc4>]
[<001aed88>]
[<001aed84>]
[<001aee0f>]
System.map shows the following
001ae9a0 t scsi_times_out
001aeac8 T request_queueable
001aece8 T allocate_device
001af008 T internal_cmnd
001af108 t scsi_request_sense
001af28c T scsi_do_cmd
>From these it seems the system is stuck looping somewhere in allocate_device.
How can I disassemble the kernel code to see exactly where the problem is?
Richard
-- Richard Waltham | Work: richard@digitalinterface.demon.co.uk At home in | Home: dormouse@farsrobt.demon.co.uk Southampton UK | 100421.1276@compuserve.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/