Ok, thanks. Btw, with the linux-kernel mailing list being as slow as it
is, please Cc to me directly anything critical like this so that we don't
get turn-around times of several days..
The dump itself is uninteresting, because it crashes at a random place
due to jumping off into la-la-land (the last time it was around the zero
kernel address, now it's somewhere else.
> Using `System.map' to map addresses to symbols.
>
> >>EIP: 10c6ad <setup_x86_irq+99/124>
> Trace: 11ad09 <__wait_on_page+8d/ec>
> Trace: 11b1a3 <generic_file_read+43b/620>
> Trace: 120d5a <sys_read+aa/bc>
> Trace: 10a3f9 <system_call+59/a0>
The trace shows that it's __wait_on_page() that does the jumping, and it
certainly shouldn't jump to xetup_x86_irq.. The only jump it does (apart from
a schedule) is to start up the disk IO with "run_task_queue(&disk_tq)".
It looks like some disk driver isn't setting up the task queues correctly
or similar. Can you tell me (remind me - I'm sure I've heard it before)
what block device drivers you use? (loop/scsi/ide/idecd etc..)
Linus