From: rct@gherkin.frus.com (Bob Tracy)
To: James.Bottomley@SteelEye.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: BAD_SG_DMA panic in aha1542
Date: Mon, 30 Apr 2007 21:10:32 -0500 (CDT) [thread overview]
Message-ID: <20070501021032.61120DBA1@gherkin.frus.com> (raw)
In-Reply-To: "from (env: rct) at Apr 30, 2007 09:33:12 am"
rct wrote:
> Apologies to all concerned for an unfortunate delay in resolving this.
> (...)
> I'll go retrieve a more conservatively-configured source tree (closer to
> what DSL-N uses) and start over...
Success with the Debian 2.6.18-4-486 build, which is known to work
almost as well on the test platform as the 2.6.12 kernel that DSL-N
comes with. I used an older compiler than Debian used for their
production build, so I binary-patched the aha1542.ko and sr_mod.ko
files so insmod wouldn't complain about different vermagic strings.
That's as close as it gets without redoing everything from scratch.
I'll give Alan's and James' patches a go within the next 13 hours.
(Alan: what *else* would you name a variable associated with a bounce
buffer besides Zebedee? Thanks for the occasion to smile...)
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next reply other threads:[~2007-05-01 2:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 2:10 Bob Tracy [this message]
2007-05-01 13:33 ` Jens Axboe
2007-05-01 13:42 ` Bob Tracy
2007-05-01 13:46 ` Alan Cox
2007-05-01 18:32 ` Bob Tracy
-- strict thread matches above, loose matches on Subject: below --
2007-04-27 21:47 Bob Tracy
2007-04-27 22:13 ` Alan Cox
2007-04-27 23:56 ` Bob Tracy
2007-04-27 22:21 ` James Bottomley
2007-04-27 23:53 ` Bob Tracy
2007-04-30 14:33 ` Bob Tracy
2007-04-30 17:32 ` Jens Axboe
2007-04-30 17:39 ` Christoph Hellwig
2007-04-30 17:52 ` Jens Axboe
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=20070501021032.61120DBA1@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=James.Bottomley@SteelEye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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
all inboxes | Powered by JetHome®