linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andy Chittenden" <AChittenden@bluearc.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: skge error; hangs w/ hardware memory hole
Date: Wed, 19 Jul 2006 15:05:41 +0100	[thread overview]
Message-ID: <89E85E0168AD994693B574C80EDB9C270464C9FA@uk-email.terastack.bluearc.com> (raw)

> I'm still waiting for a positive test result. Ideally from multiple
people 
> because it's a pretty radical step to blacklist all VIA chipsets like
this
> (and it's s still possible that only some BIOS are broken, not all VIA
boards)
> In fact I've been trying to get confirmation from VIA on this, but
they
> never answered my queries.

With iommu=force, my A8V deluxe system crashes during boot.

With iommu=soft swiotlb=force, the skge driver still has problems:

skge 0000:00:0a.0: PCI error cmd=0x157 status=0x22b0
skge unable to clear error (so ignoring them).

Also seen:

skge 0000:00:0a.0: PCI error cmd=0x117 status=0x22b0

The sk98lin driver prints out loads of garbage too fast for me to read
and I can't stop it either (scroll lock doesn't stop it). It's saying
something like "unexpected IRQ status error" - there's also a number
printed which looks like 0x264.

FWIW the e100 driver works fine without either of these options

-- 
Andy, BlueArc Engineering

             reply	other threads:[~2006-07-19 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 14:05 Andy Chittenden [this message]
     [not found] <6uDGH-7Nj-57@gated-at.bofh.it>
     [not found] ` <200609200901.39460.ak@suse.de>
     [not found]   ` <45118F00.2030303@highlandsun.com>
     [not found]     ` <200609202121.14156.ak@suse.de>
     [not found]       ` <4511A101.2070707@highlandsun.com>
     [not found]         ` <5624739.1158784754480.SLOX.WebMail.wwwrun@imap-dhs.suse.de>
2006-09-24 19:50           ` skge error; hangs w/ hardware memory hole Howard Chu
  -- strict thread matches above, loose matches on Subject: below --
2006-07-03 20:52 Martin Michlmayr
2006-07-07 21:18 ` Stephen Hemminger
2006-07-07 21:28   ` Andi Kleen
2006-07-08  8:50     ` Martin Michlmayr
2006-07-09 15:24     ` Anthony DeRobertis
2006-07-12  2:46     ` Anthony DeRobertis
2006-07-12  2:54       ` Andreas Kleen
2006-07-12  4:09         ` Kevin Brown
2006-07-12 13:37           ` Andi Kleen
2006-07-23  6:32         ` Anthony DeRobertis
2006-07-24  2:12           ` Stephen Hemminger
2006-07-25  2:35           ` Andi Kleen

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=89E85E0168AD994693B574C80EDB9C270464C9FA@uk-email.terastack.bluearc.com \
    --to=achittenden@bluearc.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).