We have 3 of the 32 port Comtrol PCI cards, the original 5v only
cards, not the newer universal PCI cards, and we are trying to upgrade
the system with all these serial ports from FreeBSD 4.8 (ya, kinda
old) to FreeBSD 6.2. And we are running into what seems like a common
problem with these cards:
We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP Vortex
GDT8546RZ 4 port SATA RAID card in a Tyan S2460 system with dual AMD
Athlon MP 1600+ CPUs. We do not have any problems with this
configuration under FreeBSD 4.11, and we have the same ICP cards in
Tyan based Opterion system (S28
Doug> We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP
Doug> Vortex GDT8546RZ 4 port SATA RAID
John-Mark> We've had very similar experiences on 4.7-R. The box would
John-Mark> hang on one partition waiting for IO to come back, but
John-Mark> direct access to the disk, or accessing
John-Mark> How about drop iir?
Doug> But your suggestion does have merit, especially as recent PCI-X
Doug> and PCI-E ICP cards have no FreeBSD driver in sight.
Scott> My understanding is that the ICP division is switching over to
Scott> the architcture supported by the 'aac' driver. Adaptec
Scot
JM> Basicly a process will hang in either ffsfsn (fsync induces this
JM> write) or getblk (a read), and as far as I can find out, the io
JM> just never returns even though the underlying block device
JM> continues to work fine..
I know this is probably a stupid answer, but ... Have you upgraded
t
I've got 2 FreeBSD 5.4 systems that seem to get stuck doing disk
IO. When the system gets hung, it seems to refuse to do any disk
io. It will continue to respond to pings, and the tty driver on the
serial console continues to work and echo characters. But all the
processes seem to get stuck in the
** On Sat, 17 Dec 2005 00:49:48 +0800, Xin LI <[EMAIL PROTECTED]> said:
Xin> I have a box indicating the following sometimes:
Xin> "swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096"
We are having a very similar problem that we've been trying to
diagnose off and on for a wh
Xin> Hi
Hi.
On 19 Dec 2005 14:32:31 -0600, Douglas K. Rand <[EMAIL PROTECTED]> wrote:
Doug> Tracing command swapper pid 0 tid 0 td 0xc0698e20
Doug> sched_switch(c0698e20,0,1) at sched_switch+0x14b
Doug> mi_switch(1,0) at mi_switch+0x1ba
Doug> scheduler(0,81ec00,81e000,0,c
Sometime between 4.1.1-STABLE and 4.2-BETA we started having
difficulities with using pam_ssh and wdm. Here is a piece of our
/etc/pam.conf:
wdm authsufficient pam_ssh.so
wdm authrequiredpam_unix.so
wdm account requiredpam_unix.so try_first_p
> Drat. There it is; you've got a command that looks like it's stuck in
> the adapter.
I'll go grab the can of WD-40. :)
> I didn't see you respond to Mike T - are you using 64k or 128k stripes?
I didn't get his query until I had already started the mysqd trying to break
things. And now I'm
> Drat. There it is; you've got a command that looks like it's stuck in
> the adapter.
>
> try changing the value of TWE_Q_LENGTH in /sys/dev/twe/twereg.h to 100 and
> see if you can reproduce it.
Well, I just woke up and mysqd was stuck again in getblk, this time with a
TWE_Q_LENGTH of 100:
db
We have two pretty much identical systems: Both are Tyan Tiger MP
S2469 boards with a 3ware 7450 controller and Western Digital WD1000
100GB disks. One system has 4 disks in a RAID 10 configuration, and
the other has 2 disks in a RAID 1 configuration. One system only has a
single Athlon MP CPU, wh
Albert> We're running a 6410 with four WD1000 disks and have had only
Albert> one failure so far. Anyway, according to the author of the twe
Albert> driver, Michael Smith, a firmware upgrade for the 7xxx series
Albert> controllers should be available by now.
Thanks, I had missed that post. We mig
13 matches
Mail list logo
