From: Douglas Gilbert <dougg@torque.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux SCSI Error Question with SG Driver
Date: Thu, 09 Mar 2006 09:23:14 -0500 [thread overview]
Message-ID: <44103A52.3090509@torque.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0603090706370.15616@p34>
Justin Piszcz wrote:
> I have a tape library connected to a Linux box here and every once and a
> while I see these in dmesg:
>
> sg_low_free: bad mem_src=0, buff=0xdb6a8000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb6b0000, rqSz=28672
> sg_low_free: bad mem_src=0, buff=0xdb738000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb718000, rqSz=28672
> sg_low_free: bad mem_src=0, buff=0xdb680000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb678000, rqSz=28672
> sg_low_free: bad mem_src=0, buff=0xdb670000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb668000, rqSz=28672
> sg_low_free: bad mem_src=0, buff=0xdb660000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb658000, rqSz=28672
> sg_low_free: bad mem_src=0, buff=0xdb650000, rqSz=32768
> sg_low_free: bad mem_src=0, buff=0xdb648000, rqSz=28672
>
> Does anyone know what they refer to?
Justin,
That looks like the sg driver in the lk 2.4 series.
When it comes to free up some memory in sg_low_free()
it checks where the memory was sourced from. A
mem_src of 0 is not defined hence the error message.
Hard to say why this happens as the buff addresses
and rqSz values look reasonable.
Doug Gilbert
prev parent reply other threads:[~2006-03-09 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 12:07 Linux SCSI Error Question with SG Driver Justin Piszcz
2006-03-09 14:23 ` Douglas Gilbert [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=44103A52.3090509@torque.net \
--to=dougg@torque.net \
--cc=jpiszcz@lucidpixels.com \
--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