public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Filip Van Raemdonck <filipvr@xs4all.be>
To: "Juergen E. Fischer" <fischer@linux-buechse.de>
Cc: Martin Diehl <lists@mdiehl.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] aha152x fix
Date: Thu, 18 Jul 2002 09:42:30 +0200	[thread overview]
Message-ID: <20020718074230.GD2155@debian> (raw)
In-Reply-To: <20020718055204.GA10357@linux-buechse.de>

On Thu, Jul 18, 2002 at 07:52:04AM +0200, Juergen E. Fischer wrote:
> [I seem to have had a problem with my provider's smart host. It didn't
>  deliver to everyone.  Hopefully that's resolved now. Sorry
>  I you already seen this whole or in part.]

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?

  parent reply	other threads:[~2002-07-18  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 21:10 [PATCH] aha152x fix Filip Van Raemdonck
2002-07-16 23:00 ` Alan Cox
2002-07-17  7:09   ` Filip Van Raemdonck
2002-07-17  8:02   ` Martin Diehl
2002-07-17 21:35     ` Filip Van Raemdonck
     [not found]       ` <20020718055204.GA10357@linux-buechse.de>
2002-07-18  7:42         ` Filip Van Raemdonck [this message]
2002-07-18 12:34         ` Martin Diehl
     [not found] <20020718222805.GA16641@linux-buechse.de>
2002-07-19 17:09 ` Martin Diehl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020718074230.GD2155@debian \
    --to=filipvr@xs4all.be \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fischer@linux-buechse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@mdiehl.de \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox