From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Software IO-TLB Kernel panic
Date: Thu, 17 May 2001 18:49:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005607@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005601@msgid-missing>
>>>>> On Thu, 17 May 2001 19:40:17 +0200 (CEST), Martin Wilck <Martin.Wilck@fujitsu-siemens.com> said:
>>
Martin> The kernel panic occurs in map_single
Martin> (arch/ia64/lib/swiotlb.c:171).
>> Sounds like the driver is trying to map buffers that are bigger
>> than (1 << IO_TLB_SHIFT) (currently 2KB).
Martin> I looked at the code and thought that bigger buffers than
Martin> 2kB can (in principle) be created by joining subsequent
Martin> buffers. Of course, it could happen that no such contiguous
Martin> space is available. Am I wrong ?
Yes, you're right. I forgot about the joining.
--david
next prev parent reply other threads:[~2001-05-17 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 11:44 [Linux-ia64] Software IO-TLB Kernel panic Martin Wilck
2001-05-17 15:00 ` David Mosberger
2001-05-17 17:40 ` Martin Wilck
2001-05-17 18:49 ` David Mosberger [this message]
2001-05-18 19:00 ` [Linux-ia64] Software IO-TLB Kernel panic - preliminary analysis Martin Wilck
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=marc-linux-ia64-105590693005607@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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 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.