I have received your previous message, but only saw it after I sent mine.
(I read lkml from a different address than the one I send from, and only
check the mail received at the latter once a day)
And it appears your mail doesn't reach lkml anyway. ECN perhaps?
> On Wed, Jul 17, 2002 at 23:35:43 +0200, Filip Van Raemdonck wrote:
> > Actually, hold on...
> > I just rmmodded the aha152x module and then modprobe sd_mod and all was/is
> > fine now, except that obviously I can't get to my harddrive now - sd_mod is
> > just an unused driver.
> >
> > I'm pasting an oops below.
>
> Please run it through ksymoops (Documentation/oops-tracing.txt).
Can that be done with the ones already modified by klogd? Note that when I
talked about almost immediate hard crashes, I really meant that. Within a
second (or two or three at max) a number of new oopses are generated, ending
in a final one with the "killing interrupt handler" message. And these don't
even show up in the logs because the machine doesn't sync anymore at that
point.
I also don't have a serial cable handy.
But I'll see what I can do.
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)
> + spin_unlock_irq(&io_request_lock);
> +#endif
Note that this is not really the issue (anymore). I did this already, and
basically just left out the #if. But now I'm getting oopses when I actually
try to use a drive attached to it - which is probably caused by another part
of the last driver change than this detect issue.
Regards,
Filip
-- <broonie> Why do all the idiots on debian-user insist on trying sendmail. <Myth> because sendmail is "industry standard" <broonie> Mind you, I suppose the industry standard is to be a fscking moron. <Thing> broonie: tell them to fuck off and use M$ Exchange -- that's that market leader, surely? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/