Bug 62402

Summary: easily circumventable Blade150 problem
Product: Documentation Reporter: Lodewijk Vöge <lodewijk>
Component: Books & ArticlesAssignee: freebsd-doc (Nobody) <doc>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Lodewijk Vöge 2004-02-05 21:10:16 UTC 
This is a request to append a note to the documentation for sparc64, and a
way to get the solution into Google in any case.

We had installed 5.2-RELEASE on a Blade 150. it would work okay for a while,
but would reliably die during a cvsup with a

IOMMU fault at virtual address 0xC3000000                                       
Uncorrectable DMA error AFAR 0x696000 AFSR 0x210000ff000000000

in the end the solution turned out to be to unplug the USB keyboard. I had
found one message in the archives indicating the Blade150 needed to be
installed without the keyboard because it wasn't supported at all, but this
appeared not to apply: the machine installed fine and works for a while
before panicing, always under network load. But, as it turned out, that was it.

Fix: 

Add a note to the sparc64 documentation that you really shouldn't have the
keyboard plugged in a Blade150 even if it appears to work fine at first sight.
Comment 1 Gavin Atkinson 2004-09-15 12:46:34 UTC 
Hi, 

Can you try with a more recent version of FreeBSD (as 5.3 is about to be
released) and report if this is still a problem?  If it is, this PR may
be better filed in the Sparc64 category as a bug to fix rather than
something to document.

Gavin
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2005-12-25 01:45:07 UTC 
State Changed
From-To: open->closed

Feedback timeout (> 1 year).