From owner-freebsd-stable Sat May 4 12:38:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (dhcp45-25.dis.org [216.240.45.25]) by hub.freebsd.org (Postfix) with ESMTP id 46E7B37B428; Sat, 4 May 2002 12:38:18 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g44Jafh82708; Sat, 4 May 2002 12:36:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200205041936.g44Jafh82708@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Mike Tancsa Cc: Michael Smith , stable@FreeBSD.ORG Subject: Re: 3ware problem In-reply-to: Your message of "Sat, 04 May 2002 08:48:45 EDT." <5.1.0.14.0.20020504084607.067206f0@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 May 2002 12:36:41 -0700 From: Michael Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Actually, I am seeing the same thing > > /var/log/messages.0.gz:Apr 29 14:30:04 newflint /kernel: twe0: PCI parity > error: Reseat card, move card or buggy device present.twe0: PCI parity > error: Reseat card, move card or buggy device present. > > Perhaps bogus firmware ? BIOS settings ? I moved it to two different > machines, same problem. Bogus hardware. The only really good thing to do is just ignore it entirely. IIRC, the latest Linux driver doesn't bother clearing the bit in PCI config space; if you can check their sources and tweak the driver to DTRT, I'd love to know what works, since I don't have a machine that reproduces this. = Mike -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message