Mailinglist Archive: packet-writing (124 mails)
| < Previous | Next > |
debugging hard lockups
- From: Jens Axboe <axboe@xxxxxxx>
- Date: Mon, 23 Apr 2001 22:28:30 +0000 (UTC)
- Message-id: <20010424002819.U9357@xxxxxxx>
Hi,
I think most of the hard hangs people are seeing are actually induced on
purpose. The BUG() will hard hang a machine at times, usually because
interrupts are disabled or just because we are holding a spin lock.
Because of that, to debug a hard hang without a serial console you can
do something like... :
#undef BUG
#define BUG() do { \
printk("kernel BUG at %s:%d!\n", __FILE__, __LINE__); \
} while (0);
right before the SCSI_IOCTL_SEND_COMMAND define in
drivers/block/pktcdvd.c and recompile the kernel/module. _If_ you choose
to do so, look for these messages in your logs repeatedly -- I
definitely don't want to miss one of them, that's why they are BUG's
now.
--
Jens Axboe
I think most of the hard hangs people are seeing are actually induced on
purpose. The BUG() will hard hang a machine at times, usually because
interrupts are disabled or just because we are holding a spin lock.
Because of that, to debug a hard hang without a serial console you can
do something like... :
#undef BUG
#define BUG() do { \
printk("kernel BUG at %s:%d!\n", __FILE__, __LINE__); \
} while (0);
right before the SCSI_IOCTL_SEND_COMMAND define in
drivers/block/pktcdvd.c and recompile the kernel/module. _If_ you choose
to do so, look for these messages in your logs repeatedly -- I
definitely don't want to miss one of them, that's why they are BUG's
now.
--
Jens Axboe
| < Previous | Next > |