There is a bug in the Tyan S4881/S4882 PCI-X bridges that was fixed with a
patch in 7.x (thank you very much). This patch is not present in the
8.2-STABLE code and the symptoms (watchdog timeouts) have recurred.
The watchdog timeouts do not appear to be present after I switched to an
Intel gi
"make buildworld" fails when trying to "make buildworld" (no options)
with 8.2-RELEASE with 8.2-STABLE sources as of 2/6/2012 updated at 9:15 AM
from ftp.freebsd.org.
The compile fails in the same spot every time; this is not a random
failure. I have seen some evidence, however, that there ma
A patch which allows FreeBSD 8.3-STABLE to use the Broadcom GigE bge ports
on the Tyan S4882 quad Opteron motherboard (and almost certainly on the
S4881 motherboard, which had the same problem with 7.4-STABLE) has been
developed by YongHyeon Pyun.
The problem involves a bug in the PCI bridge w
I've been running 7.X on a Tyan S4881 (4 dual-core Opteron CPUs) since
nearly the beginning of the 7.X cycle, and have just started to see
watchdog timeouts on the Broadcom bge0 GigE port.
This occurs with a kernel and world compiled on 11/22, and also with a
kernel compiled on 11/11 with the
Problem is watchdog timeouts with a Broadcom GigE interface on a Tyan
S4881 using 7.4-PRERELEASE as of 11/22 and 7.3-STABLE as of 11/11.
I've done the following, with no success:
(1) Tried the second port, bge1, in case the first had gone bad, and
(2) Recompiled samba34 (failure occurs when
The Tyan S4881 works perfectly with 7.3-RELEASE-p3; I'll be reinstalling
7.4 and providing the requested diagnostics once I have a backup made.
(Broadcom bge watchdog timeouts under moderate (25% max of GigE) load)
Mike Squires
mi...@siralan.org
___
I'm having watchdod timeout problems with the bge driver in 7.4-PRERELEASE
on a Tyan S4881 motherboard (the S4881 has 4 Opteron sockets, 2 PCI-E
slots, and 3 PCI-X slots, plus VGA and dual Broadcom "bge" GigE ports.)
I don't know if this problem also affects the similar Tyan S4882 motherboard,
On Thu, 30 Dec 2010, Jeremy Chadwick wrote:
Please provide output from the following command, as root:
pciconf -lbvc
And only include the bge1 and bge0 devices in your output. Thanks.
This is the output, as root, using the kernel with the 10/7/2010 bge code
(which works for me). I can p
Here is pciconf -lvbc under 8.3-RELEASE p8:
hostb0@pci0:0:0:0: class=0x06 card=0x chip=0x00171166 rev=0x32
hdr=0x00
vendor = 'ServerWorks (Was: Reliance Computer Corp)'
device = 'CMIC-SL'
class = bridge
subclass = HOST-PCI
hostb1@pci0:0:0:1: c
On Sun, 12 May 2013, Glen Barber wrote:
On Sat, May 11, 2013 at 10:57:44PM -0400, Michael L. Squires wrote:
I upgraded to FreeBSD 8.4-RC3 and noticed a problem with the fxp
driver on an older Supermicro single CPU single core Xeon
motherboard.
[...]
Copyright (c) 1992-2013 The FreeBSD
I'm not sure this is a kernel issue.
I re-installed 8.3Release p8 (have to get work done!) and then installed a
8.4 Prerelease kernel (I'm still running cvsup, going to svn is a number
of crisis problems down from the list of things to fix today).
Booted with the 8.4 Prerelease kernel but usi
The problem is not with the kernel/motherboard combination but with the
world/motherboard combination.
8.3-R p8 with the 8.3R p8 world works fine.
8.4-Prerelease (what I get using cvsup "8_4") works fine.
8.3R p8 with the 8.4 Pre world has DHCP problems (see example below)
8.4 Pre with the 8.
I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of 8.4-RC3. I had problems with the installation, wouldn't
boot until I used a Windows 98 FDISK to write a master boot record (no
idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X board with two
I'll have access to the test box on Tuesday, will test a fixed IP number
then. I'm unable to test that here since reinstalling 8.4 on the NAT box
will require eventually reinstalling 8.3-RELEASE and I'm not the only one
using the NAT box for Internet access.
The test box had 8.3-RC3 installed
On Mon, 27 May 2013, YongHyeon PYUN wrote:
On Sun, May 26, 2013 at 08:38:41PM +0900, YongHyeon PYUN wrote:
On Fri, May 24, 2013 at 04:36:46PM +0900, Hiroki Sato wrote:
Hiroki Sato wrote
in <20130524.162926.395058052118975996@allbsd.org>:
hr> YongHyeon PYUN wrote
hr> in <20130524054
Short answer: it didn't work.
On Tue, 28 May 2013, YongHyeon PYUN wrote:
On Mon, May 27, 2013 at 01:02:14PM -0400, Michael L. Squires wrote:
On Mon, 27 May 2013, YongHyeon PYUN wrote:
On Sun, May 26, 2013 at 08:38:41PM +0900, YongHyeon PYUN wrote:
On Fri, May 24, 2013 at 04:36:46PM
I've not worked with 10.x a lot, so please excuse novice mistakes.
I upgraded the OS on a quad Opteron Tyan S4881 (known to have SMP
bugs, but I haven't seen any and I've been running this system for
years). I upgraded from an earlier version of FreeBSD-10.x to
FreeBSD 10.2-BETA1 r285551.
Pr
On Thu, 16 Jul 2015, Michael L. Squires wrote:
I've not worked with 10.x a lot, so please excuse novice mistakes.
I upgraded the OS on a quad Opteron Tyan S4881 (known to have SMP bugs, but I
haven't seen any and I've been running this system for years). I upgraded
from an
I'm using an older Supermicro 1U box as my NAT box for my home network; I
also read email on it by logging in remotely using Cygwin's ssh to run
pine.
I've noticed a change in behavior which ocurred when I upgraded from 7.1-STABLE
compiled 2/8/2009 to 7.2-PRERELEASE compiled 4/24/2009.
The
I started having speed problems after shifting from 7.1-STABLE to
7.1-PRERELEASE. They have continued with 7.2-STABLLE.
Reverting to the 7.1-STABLE kernel eliminated the problem.
After downloading 7.2-STABLE from cvsup.freebsd.org at about 10:40 AM EST
on 5/20/2009, doing a buildworld/buildker
On Thu, 21 May 2009, Pyun YongHyeon wrote:
On Wed, May 20, 2009 at 05:55:29PM -0400, Michael L. Squires wrote:
I started having speed problems after shifting from 7.1-STABLE to
7.1-PRERELEASE. They have continued with 7.2-STABLLE.
Reverting to the 7.1-STABLE kernel eliminated the problem
I had a similar build error with 7.2-STABLE with a different error -
internal compiler error.
After updating and having buildworld fail in the same spot I completely
cleaned my /usr/obj and /usr/src directories (need "cd /usr/obj;chflags -R
noschg *;rm -rf *" for /usr/obj and then downloaded t
Not that it will help you, but I'm running 6.2-PRERELEASE compiled 9/23
with three Adaptec controllers and no problems; none of them is a 29160,
however.
ahc0: port 0xe000-0xe0ff mem
0xfebfd000
-0xfebfdfff irq 16 at device 14.0 on pci0
ahc0: [GIANT-LOCKED]
ahc1: port 0xe400-0xe4ff mem
0xfe
On Mon, 29 Nov 2004, Jon Noack wrote:
alex bustamante wrote:
How come that when i run X11 under FreeBSD my Intellimouse is a lot slower
than in X11 under Linux? I use Option Protocol "auto" under FreeBSD and
I had a very slow mouse when running a kernel with the debug options
enabled, running 5.x
I've been experimenting with various cards, most cheap. The monitors are
HP P1110 21" surplus, very bright (too bright) and very sharp. These are
the PC version with VGA connectors, not the ones with BNC connectors.
I currently have a Matrox G450 in dual-head mode under 5.3-STABLE with
Xorg,
I had a similar problem with a machine with two Adaptec 2940UW
controllers. When I upgraded from somethng like 4.7 to 4.8 the machine
stopped booting. My workaround was to go with a single controller.
The problem seems to be that at some point in the 4.X development cycle
the way in which SCS
The information needed to wire down SCSI devices (which appears to be
necesary in some cases with systems that have more than 1 SCSI controller)
is contained in
/usr/src/sys/i386/conf/NOTES for v4.10, and
/sys/conf/NOTES for 5.3-STABLE
Thanks to Scott Long for pointing out the latter.
Mike Squir
For security reasons the linux-base version has been updated from 7 to 8;
when I follow the instructions in /usr/ports/UPDATING I get a message from
the linux-8 make process that I should have first installed rpm 4.0.4
(apparently /var/lib/rpm/packages.rpm is in db1 format, and linux-8 wants
it
I've been playing with vinum and gvinum with a RAID-1 boot setup (now
abandoned, hardware RAID was $29 - SM P4DC6+ with Adaptec 2005S) and with
a RAID5 array using a Compaq version of the Adaptec 39160 card.
I've found that only "geom_vinum_load="YES" works in order to get the RAID
5 array moun
I have an NFS exported directory "/share" which contains "/share/Mac"; the
"Mac" directory is itself exported vi netatalk, and contains several GB of
Macintosh files.
If I execute
tar cf /dev/null Mac when "/share" is my current directory on the 4.10 box
nothing happens, other than consuming a
On Tue, 22 Feb 2005 [EMAIL PROTECTED] wrote:
Hi there,
I have carried out extensive hardware tests and most of the hardware
(including most of the memory, the cpu and main board) have already been
replaced but this makes no difference to stability. I also believe this issue
was already there when
On Sat, 12 Mar 2005, Dan Ponte wrote:
Hi all.
I've been seeing lots of ACPI errors in my dmesg lately. They haven't
FreeBSD 5.3-STABLE #3: Wed Jan 12 16:34:03 EST 2005
There were some changes to ACPI at about that time which caused
motherboards with buggy BIOSes to have problems. These were fix
Problem: Bogus modification dates cause tar/bsdtar 1.02.023 failure,
gnutar works
The files were created from old Macintosh files using netatalk. One file
has a bogus modification date of Nov 16, 1913, which appears to cause
"bsdtar" to fail:
newserv# tar cvf /tmp/test.tar hpLaserJet456Ins
On Thu, 9 Mar 2006, Peter Guhl wrote:
Hi again
On Thu, 2006-03-09 at 11:11 +0100, Peter Guhl wrote:
/usr/ports/textproc/wv, part of the dependencies, fails:
configure: error: * * * unable to find libwmf-config; unable to continue
* * *
libwmf is installed. libwmf-config is in /usr/local/bi
This looks like the problem I have with 5.4-STABLE after a kernel change
on 9/5/2005 to /usr/src/sys/dev/pci/pci.c.
The sysclt paramater "hw.pci.enable_io_modes" is supposed to allow PCs
with "lazy" BIOSes to boot, but this setting had no effect on my 8100.
If your problem is the same as mine
I tried to install a RAID5 array using both vinum and gvinum under
5.3-RELEASE and couldn't get a reliable system running. I reinstalled
using 4.11-STABLE and so far the system (and vinum) have been error-free.
The 5.4-RELEASE documentation only mentions that "geom_vinum" provides a
GEOM compa
This may be a similar problem to the one discussed in the Intel ICH2
thread.
System is a Toshiba 8100. System boots from a 5.4-STABLE kernel compiled
5/3/2005 but locks up on boot with kernels compiled in the past few days.
I re-cvsup'd after the first lockup and build a GENERIC kernel, same
A new kernel based on sources of 9/28/2005 still fails to boot on a
Toshiba 8100 with a UDMA33 IDE onboard controller. The parameters passed
to atapci0 are different from those passed by the earlier kernel, and the
system locks up this point.
I'm not including the dmesg, etc., since that's
On Thu, 29 Sep 2005, Michael L. Squires wrote:
A new kernel based on sources of 9/28/2005 still fails to boot on a Toshiba
8100 with a UDMA33 IDE onboard controller. The parameters passed to atapci0
are different from those passed by the earlier kernel, and the system locks
up this point
On Sat, 24 Sep 2005, Billy Newsom wrote:
Okay, Tim, I just reported the same bug in a previous post. So did Julian C.
Dunn. I think this is an issue with some recent code changes in CVS...
See these threads:
critical BOOT failure updating to latest 5-Stable (5.4)
9/23/2005 12:07 AM
ATA locku
I have a Toshiba 8100 notebook which runs 5.4-STABLE. Kernels compiled
after some time in September 2005 fail to boot; the machine locks up right
after the ata controller is called in the boot messages.
I have traced the problem to a change to /usr/src/sys/dev/pci.c, (see
below from my cvsup
> Its an older dual PIII. Can anyone tell me if the dumps point to a
> hardware issue, or if its crashing in the same spot each time ? I can blast
> it with buildworlds and it never dies. Generally I have yet to find bad
> hardware that could pass that But always a first time.
I have a P6
4.10-BETA caused no problems during building world, the kernel, or
portupgrade compared to 4.9-STABLE of early March.
Bytebench results for 4.10-BETA and 4.9-STABLE are very similar, for
what that's worth.
Hardware is a P6DGH/dual PII/300/two vinum RAID5 arrays using old Seagate
Elite drives (5 x
43 matches
Mail list logo
