From: FUJITA Tomonori <tomof@acm.org>
To: mjt@tls.msk.ru
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
fujita.tomonori@lab.ntt.co.jp
Subject: Re: kernel BUG at drivers/scsi/aic7xxx/aic79xx_osm.c:1490!
Date: Sun, 9 Mar 2008 21:29:16 +0900 [thread overview]
Message-ID: <20080309212916T.tomof@acm.org> (raw)
In-Reply-To: <47D3C8A1.6040409@msgid.tls.msk.ru>
On Sun, 09 Mar 2008 14:23:13 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> Just got quite.. bad situation on a production server
> here. The machine locked up hard several times in a
> row (required hard reboot). So I finally enabled watchdog
> subsystem which helped.
>
> Now I see the following (over netconsole):
>
> DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:08:07.0
> ------------[ cut here ]------------
> kernel BUG at drivers/scsi/aic7xxx/aic79xx_osm.c:1490!
Seems that you was out of swiommu space (and aic79xx can't handle it
though it should). This happened because:
a) you produced more I/Os than swiommu can handle.
b) swiommu space leaks due to bugs.
If you hit this problem due to a), the following boot option might
help:
swiotlb=65536
The same machine run well with old kernels? If so, probably, 2.6.24
has new bugs that lead to swiommu space leak.
WARNING: multiple messages have this Message-ID (diff)
From: FUJITA Tomonori <tomof@acm.org>
To: mjt@tls.msk.ru
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: fujita.tomonori@lab.ntt.co.jp
Subject: Re: kernel BUG at drivers/scsi/aic7xxx/aic79xx_osm.c:1490!
Date: Sun, 9 Mar 2008 21:29:16 +0900 [thread overview]
Message-ID: <20080309212916T.tomof@acm.org> (raw)
In-Reply-To: <47D3C8A1.6040409@msgid.tls.msk.ru>
On Sun, 09 Mar 2008 14:23:13 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> Just got quite.. bad situation on a production server
> here. The machine locked up hard several times in a
> row (required hard reboot). So I finally enabled watchdog
> subsystem which helped.
>
> Now I see the following (over netconsole):
>
> DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:08:07.0
> ------------[ cut here ]------------
> kernel BUG at drivers/scsi/aic7xxx/aic79xx_osm.c:1490!
Seems that you was out of swiommu space (and aic79xx can't handle it
though it should). This happened because:
a) you produced more I/Os than swiommu can handle.
b) swiommu space leaks due to bugs.
If you hit this problem due to a), the following boot option might
help:
swiotlb=65536
The same machine run well with old kernels? If so, probably, 2.6.24
has new bugs that lead to swiommu space leak.
next prev parent reply other threads:[~2008-03-09 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 11:23 kernel BUG at drivers/scsi/aic7xxx/aic79xx_osm.c:1490! Michael Tokarev
2008-03-09 11:25 ` Michael Tokarev
2008-03-09 12:29 ` FUJITA Tomonori [this message]
2008-03-09 12:29 ` FUJITA Tomonori
2008-03-09 12:55 ` Michael Tokarev
2008-03-09 15:08 ` James Bottomley
2008-03-09 15:20 ` James Bottomley
2008-03-09 15:31 ` Michael Tokarev
2008-03-09 15:42 ` Michael Tokarev
2008-03-09 15:59 ` James Bottomley
2008-03-09 16:32 ` Michael Tokarev
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=20080309212916T.tomof@acm.org \
--to=tomof@acm.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.