LKML Archive on
help / color / mirror / Atom feed
From: Chris Snook <>
To: "linux-os (Dick Johnson)" <>
Cc: Linux kernel <>
Subject: Re: 64-bit AMD panic
Date: Thu, 06 Mar 2008 11:41:25 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

linux-os (Dick Johnson) wrote:
> Hello all,
> We have 64-bit production machines that use the kernel shipped with
> a RedHat distribution, linux-2.6.11-1.1369_FC4smp. There have been
> no problems until we received recent hardware. With the latest hardware,
> which the vendor claims hasn't changed, the machines panic when either
> a USB mouse or USB keyboard are plugged in.
> Machine:
> Supermicro H8DME-2
> Two quad-Core AMD Opteron CPUs
> 64GB DDR2 400 SDRAM
> 6 SATA2 3.0Gb/s HD Support
> 2 64-bit 133/100 MHz PCI-X
> 2 64=bit 100MHz PCI-X
> ATI ES1000 Graphics
> Chipset nVida MCP55 Pro
> NEC uPD720400
> USB FUCI, uses ohci_hcd driver.
> When mouse or keyboard is inserted, I get a panic with:
> "map_single bounce buffer is not DMA'ble."
> This comes from: linux-2.6.11-prep/arch/ia64/lib/swiotlb.c,
> line 440. I added 64-bit long print hex to the panic statement
> so I could display the address it doesn't like.

You're using an Itanium kernel on Opteron?

> The address it doesn't like is: 0x000000022a0aa000
> Does anybody have a clue what might be the matter and how to fix it?

If the hardware "didn't change" then it could be a BIOS bug, or just a 
different BIOS behavior that your old kernel doesn't handle well.  Try 
the same version you had on the old hardware.  I once had a desktop box 
that developed a similar behavior when I twiddled the memory hole 
remapping settings in the BIOS.

-- Chris

      parent reply	other threads:[~2008-03-06 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 17:06 linux-os (Dick Johnson)
2008-03-03 18:45 ` Christian Kujau
2008-03-03 21:22   ` Rik van Riel
2008-03-03 22:10     ` linux-os (Dick Johnson)
2008-03-03 22:21       ` Rik van Riel
2008-03-04  0:11       ` Jesper Juhl
2008-03-04 14:21         ` linux-os (Dick Johnson)
2008-03-06 16:41 ` Chris Snook [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: 64-bit AMD panic' \

* 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).