public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: Jens Axboe <axboe@suse.de>
Cc: Stephen Lord <lord@sgi.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A new ide warning message
Date: Fri, 02 Aug 2002 13:48:08 +0200	[thread overview]
Message-ID: <3D4A7178.7050307@evision.ag> (raw)
In-Reply-To: 20020802114713.GD1055@suse.de

Uz.ytkownik Jens Axboe napisa?:
> On Fri, Aug 02 2002, Stephen Lord wrote:
> 
>>In 2.5.30 I started getting these warning messages out ide during
>>the mount of an XFS filesystem:
>>
>>ide-dma: received 1 phys segments, build 2
>>
>>Can anyone translate that into English please.
> 
> 
> Well I added that message when switching to the 2.5 style request
> mapping functions, and I think the message is perfectly clear :-). Never
> the less, it means that a segment that came into the ide layer with an
> advertised size of 1 segment was returned from blk_rq_map_sg() as having
> _two_. This can be a problem with dynamically allocated sg table (not
> that ide uses those, but still).
> 
> It's a bug and usually a critical one when this happens. I'd be inclined
> to think that Adam's changes in this path are to blame for this error.

Carefull carefull. it can be that the generic BIO code doesn't honour
the limits Adam was setting properly. And it can be of course
as well the XFS doesn't cooperate properly with those limits as well,
since ther kernel appears to be patched to support them.

It would be helpfull as well to know on which brand of host controller 
chip this was found. In esp. trm290 maybe?
> 
> Oh, and I'd be _really_ careful if you have trusted data on that drive
> (surely not when running 2.5 ide on it :-)
> 



  reply	other threads:[~2002-08-02 11:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 11:34 A new ide warning message Stephen Lord
2002-08-02 11:38 ` Marcin Dalecki
2002-08-02 11:53   ` Jens Axboe
2002-08-02 11:59     ` Jens Axboe
2002-08-02 13:47       ` Bartlomiej Zolnierkiewicz
2002-08-02 14:20         ` Jens Axboe
2002-08-02 16:01           ` Bartlomiej Zolnierkiewicz
2002-08-02 16:11             ` Jens Axboe
2002-08-03 18:41         ` Marcin Dalecki
2002-08-02 11:47 ` Jens Axboe
2002-08-02 11:48   ` Marcin Dalecki [this message]
2002-08-02 11:55     ` Jens Axboe
2002-08-02 12:05     ` Stephen Lord
2002-08-02 12:12       ` Marcin Dalecki
2002-08-02 12:30         ` Jens Axboe
2002-08-02 12:31           ` Marcin Dalecki
2002-08-02 12:41             ` Jens Axboe
2002-08-02 13:50               ` Steve Lord
2002-08-02 18:34                 ` Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2002-08-03  3:28 Adam J. Richter
2002-08-03  3:32 Adam J. Richter

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=3D4A7178.7050307@evision.ag \
    --to=dalecki@evision.ag \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    --cc=martin@dalecki.de \
    /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