LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Kyuma Ohta <whatisthis@jcom.home.ne.jp>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.20-rc2: kernel BUG at include/asm/dma-mapping.h:110!
Date: Thu, 18 Jan 2007 21:28:18 +0100	[thread overview]
Message-ID: <45AFD862.6040903@s5r6.in-berlin.de> (raw)
In-Reply-To: <459A800E.3010604@s5r6.in-berlin.de>

I wrote on 2007-01-02:
> Kyuma Ohta wrote:
> ...
>> Now,I'm testing 2.6.20-rc3 for x86_64, submitted patch for this issue;
>> "Fault has happened  in 'cleanuped' sbp2/1394 module in *not 32bit*
>> architecture hardwares ."
>>
>> As result of, sbp2 driver in 2.6.20-rc3 is seems to running 
>> w/o any faults,but communication both host and harddrive(s) 
>> was seems to be unstable yet :-(
>> Sometimes confuse packets,such as *very* older 1394 driver :-(
> 
> That is, sbp2 on 2.6.20-rc3 works less stable for you than on 2.6.19? Or
> which previous kernel is the basis of your comparison? Are there any log
> messages or other diagnostics? And what hardware do you have?
> 
> If you can tell which kernel was good for you, I could create a set of
> patches for you which allows to revert sbp2 while keeping the rest of
> the kernel at the level of 2.6.20-rc3, so that you could find the
> destabilizing change (if it happened in sbp2, not somewhere else).
[...]

So, how about it? Is there an actual regression? If so, we should find
the cause and fix before 2.6.20 is released.

Note, sbp2's optional parameter serialize_io=0 does not work correctly
yet with some devices (it never did), therefore use sbp2 with anything
than default parameters if there are problems.
-- 
Stefan Richter
-=====-=-=== ---= =--=-
http://arcgraph.de/sr/

      parent reply	other threads:[~2007-01-18 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <je7iwa1l8a.fsf@sykes.suse.de>
2006-12-29 21:52 ` Benjamin Herrenschmidt
2006-12-29 22:47   ` Stefan Richter
2006-12-30 12:41     ` Andreas Schwab
     [not found] ` <1167550089.12593.11.camel@melchior>
     [not found]   ` <jey7oowgdo.fsf@sykes.suse.de>
     [not found]     ` <1167708109.12382.26.camel@melchior>
     [not found]       ` <459A800E.3010604@s5r6.in-berlin.de>
2007-01-02 16:31         ` Stefan Richter
2007-01-18 20:28         ` Stefan Richter [this message]

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=45AFD862.6040903@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=whatisthis@jcom.home.ne.jp \
    --subject='Re: 2.6.20-rc2: kernel BUG at include/asm/dma-mapping.h:110'\!'' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).