Re: How to solve mysterious system lockups?

2007-06-07 Thread N. Harrington

--- [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:

 On Mon, 4 Jun 2007 19:46:30 -0700 (PDT)
 N. Harrington [EMAIL PROTECTED] wrote:
 
  
  Hello
I have several systems that are used as squid
  caching servers. I have some systems that use SCSI
  disks and some  that use SATA disks. They are
  identical in everyway except for the sata vs SCSI
  drives. 
  
   At random times, the sata based systems seem to
 be
  freezing. You can ping them and they respond, but
 you
  cannot log in. Nor are any logs processed during
 that
  time. 
  
   I figure it mist be something to do with the
 disks,
  but I am not sure how to solve it. There seems to
 be
  little rhyme or reason. It does not happen
 necessarily
  during busy times. It can happen in the middle of
 the
  night.
  
   Any pointers in how to track down the cause would
 be
  much appreciated.
  
   Tyan S2881 Motherboard - 4gigs mem
   Using 4 SATA (or scsi) drives
   FreeBSD amd64 6.2-STABLE.
 
 Hi Nicole,
 
 I was also having system lockup problems with my
 FreeBSD-6.x servers running Squid with SATA disks. I
 could ping it but could not login using SSH.
 
 However, in my case, it was due to high mbufs usage.
 
 What's your output of the following commands?
 
 netstat -mb 
 sysctl kern.ipc.nmbclusters   
 
 Thanking you...
 
  
   Thanks!
  
Nicole

   Hi
 I have my servers behind a load balancer that also
does TCP acceleration / offloading so my mbufs usage
is pretty low. (it manages about 24 connections tops)
 However I have been noticing a larger and larger use
of swap space. Either because of an increase on our
part in the number of files stored or from upgrading
to the newest squid versions (2.6-STABLE12 and 13)
 (last look showed me having 9 million objects in
storeage for that one server)
 
  So, we could be suffering from the same thing but
from different causes. I plan to be adding more memory
soon (from 4gigs to 6 and 8) as a test. 
 
 Also I have been adding SW_Watchdog to my kernels for
now. It seems very good so far at sensing the death
and rebooting. As well as soon adding some debugging
to it to hopefully capture something useful.


 Be well.

  Nicole

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-06 Thread WorldLink Management
On Mon, 4 Jun 2007 19:46:30 -0700 (PDT)
N. Harrington [EMAIL PROTECTED] wrote:

 
 Hello
   I have several systems that are used as squid
 caching servers. I have some systems that use SCSI
 disks and some  that use SATA disks. They are
 identical in everyway except for the sata vs SCSI
 drives. 
 
  At random times, the sata based systems seem to be
 freezing. You can ping them and they respond, but you
 cannot log in. Nor are any logs processed during that
 time. 
 
  I figure it mist be something to do with the disks,
 but I am not sure how to solve it. There seems to be
 little rhyme or reason. It does not happen necessarily
 during busy times. It can happen in the middle of the
 night.
 
  Any pointers in how to track down the cause would be
 much appreciated.
 
  Tyan S2881 Motherboard - 4gigs mem
  Using 4 SATA (or scsi) drives
  FreeBSD amd64 6.2-STABLE.

Hi Nicole,

I was also having system lockup problems with my FreeBSD-6.x servers running 
Squid with SATA disks. I could ping it but could not login using SSH.

However, in my case, it was due to high mbufs usage.

What's your output of the following commands?

netstat -mb 
sysctl kern.ipc.nmbclusters   

Thanking you...

 
  Thanks!
 
   Nicole
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-06 Thread Tek Bahadur Limbu

Nicole Harrington wrote:

Hello
  I have several systems that are used as squid
caching servers. I have some systems that use SCSI
disks and some  that use SATA disks. They are
identical in everyway except for the sata vs SCSI
drives. 


 At random times, the sata based systems seem to be
freezing. You can ping them and they respond, but you
cannot log in. Nor are any logs processed during that
time. 


 I figure it mist be something to do with the disks,
but I am not sure how to solve it. There seems to be
little rhyme or reason. It does not happen necessarily
during busy times. It can happen in the middle of the
night.

 Any pointers in how to track down the cause would be
much appreciated.

 Tyan S2881 Motherboard - 4gigs mem
 Using 4 SATA (or scsi) drives
 FreeBSD 6.2-STABLE.


Hi Nicole,

I had once experienced the same problem of system lockups in my 
FreeBSD-6.x servers running Squid. Most of them used SATA disks.


I could ping the servers but could not SSH into them. It seemed as tcp 
connections had stopped in the servers.


However, my problem was caused by high mbufs usage. What do you get from 
the following commands?


netstat -mb
sysctl kern.ipc.nmbclusters

Try increasing your mbufs if in case they are too low.

But your problem might not be related to mbufs and sockets.

Thanking you...




 Thanks!

  Nicole


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-05 Thread Garrett Cooper

N. Harrington wrote:

--- Garrett Cooper [EMAIL PROTECTED] wrote:

  

N. Harrington wrote:


Hello
  I have several systems that are used as squid
caching servers. I have some systems that use SCSI
disks and some  that use SATA disks. They are
identical in everyway except for the sata vs SCSI
drives. 


 At random times, the sata based systems seem to
  

be


freezing. You can ping them and they respond, but
  

you


cannot log in. Nor are any logs processed during
  

that

time. 


 I figure it mist be something to do with the
  

disks,


but I am not sure how to solve it. There seems to
  

be


little rhyme or reason. It does not happen
  

necessarily


during busy times. It can happen in the middle of
  

the


night.

 Any pointers in how to track down the cause would
  

be


much appreciated.

 Tyan S2881 Motherboard - 4gigs mem
 Using 4 SATA (or scsi) drives
 FreeBSD amd64 6.2-STABLE.

 Thanks!

  Nicole
  
  

Nicole,
What's the driver in use for the SATA and the
SCSI drives?
-Garrett



 Hi Garret
 Here is the driver info.

-- SATA

atapci0: SiI 3114 SATA150 controller port
0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f

mem
0xfeafec00-0xfeafefff irq 17 at device 5.0 on pci3
ata2: ATA channel 0 on atapci0
ata3: ATA channel 1 on atapci0
ata4: ATA channel 2 on atapci0
ata5: ATA channel 3 on atapci0
pci3: display, VGA at device 6.0 (no driver
attached)
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci1: AMD 8111 UDMA133 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
device 7.1 on pci0
ata0: ATA channel 0 on atapci1
ata1: ATA channel 1 on atapci1
pci0: serial bus, SMBus at device 7.2 (no driver
attached)
pci0: bridge at device 7.3 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0
pci2: ACPI PCI bus on pcib2

-- SCSI

ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 
0x8000-0x80ff,0x7800-0x78ff

mem 0xfc89c000-0xfc89dfff irq 24 at device 10.0 on
pci2
ahd0: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 
0x8800-0x88ff,0x8400-0x84ff

mem 0xfc89e000-0xfc89 irq 25 at device 10.1 on
pci2
ahd1: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
pci0: base peripheral, interrupt controller at
device 10.1 (no driver attached)
pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0
pci1: ACPI PCI bus on pcib3
pci0: base peripheral, interrupt controller at
device 11.1 (no driver attached)



 Thanks!

  Nicole
Ok, so it's an AMD 8111 northbridge versus an Adaptec onboard SCSI 
controller.


1. What release / version of FreeBSD are you using? You should upgrade 
to 6.2 STABLE because there have been a variety of issues worked out in 
previous releases.
2. Do you have any logs for activity during the hours when it locks up 
(in particular anything interesting / fishy popping up)?

3. What scheduler are you using? 4BSD, ULE?
4. Does your machine (using the SATA controllers) lock up under heavy 
load? If so, you may have a northbridge cooling issue that you need to 
put a fan on. For instance, the motherboard that I was using for a while 
(ASUS P5N-E SLI) was really close to my CPU heatsink, and there was a 
lot of heat transfer between my northbridge and CPU heatsink, which was 
raising the onboard temperatures 5~10 degrees C. The new motherboard 
(ASUS P5B DLX) doesn't do that though.


Cheers,
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-05 Thread Chuck Swiger

On Jun 4, 2007, at 8:49 PM, N. Harrington wrote:

 Hi Garret
 Here is the driver info.

-- SATA

atapci0: SiI 3114 SATA150 controller port
0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f


Ah-- regrettably, the Silicon Image 3112  3114 chips have some  
significant hardware defects, which tend to show up more frequently  
when you put the disk system under significant load (especially  
RAID).  It's likely to be the case that switching to a better SATA  
controller would resolve the problems you are seeing with your SATA- 
based machines.


If you have a chance, perhaps see whether building a kernel with the  
following patch does anything to help the disk lockups you've seen:


--- sys/dev/ataata-chipset.c~  Wed Jun  1 14:24:26 2005
+++ sys/dev/ataata-chipset.c   Tue Jun  5 12:54:58 2007
@@ -2240,7 +2240,7 @@
 struct ata_pci_controller *ctlr = device_get_softc(dev);
 struct ata_chip_id *idx;
 static struct ata_chip_id ids[] =
-{{ ATA_SII3114,   0x00, SIIMEMIO, SII4CH,   ATA_SA150, SiI  
3114 },
+{{ ATA_SII3114,   0x00, SIIMEMIO, (SII4CH|SIIBUG),  ATA_SA150,  
SiI 3114 },
  { ATA_SII3512,   0x02, SIIMEMIO, 0,ATA_SA150, SiI  
3512 },
  { ATA_SII3112,   0x02, SIIMEMIO, 0,ATA_SA150, SiI  
3112 },
  { ATA_SII3112_1, 0x02, SIIMEMIO, 0,ATA_SA150, SiI  
3112 },


The effect of this change is to limit the SilI controller into doing  
DMA transfers which are smaller than 8KB, which seems to mitigate the  
most significant problems with the chipset, at the cost of some  
performance.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-05 Thread N. Harrington

--- Garrett Cooper [EMAIL PROTECTED] wrote:

 N. Harrington wrote:
  --- Garrett Cooper [EMAIL PROTECTED]
 wrote:
 

  N. Harrington wrote:
  
  Hello
I have several systems that are used as squid
  caching servers. I have some systems that use
 SCSI
  disks and some  that use SATA disks. They are
  identical in everyway except for the sata vs
 SCSI
  drives. 
 
   At random times, the sata based systems seem to

  be
  
  freezing. You can ping them and they respond,
 but

  you
  
  cannot log in. Nor are any logs processed during

  that
  
  time. 
 
   I figure it mist be something to do with the

  disks,
  
  but I am not sure how to solve it. There seems
 to

  be
  
  little rhyme or reason. It does not happen

  necessarily
  
  during busy times. It can happen in the middle
 of

  the
  
  night.
 
   Any pointers in how to track down the cause
 would

  be
  
  much appreciated.
 
   Tyan S2881 Motherboard - 4gigs mem
   Using 4 SATA (or scsi) drives
   FreeBSD amd64 6.2-STABLE.
 
   Thanks!
 
Nicole


  Nicole,
  What's the driver in use for the SATA and the
  SCSI drives?
  -Garrett
  
 
   Hi Garret
   Here is the driver info.
 
  -- SATA
 
  atapci0: SiI 3114 SATA150 controller port
 

0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f
 
  mem
  0xfeafec00-0xfeafefff irq 17 at device 5.0 on pci3
  ata2: ATA channel 0 on atapci0
  ata3: ATA channel 1 on atapci0
  ata4: ATA channel 2 on atapci0
  ata5: ATA channel 3 on atapci0
  pci3: display, VGA at device 6.0 (no driver
  attached)
  isab0: PCI-ISA bridge at device 7.0 on pci0
  isa0: ISA bus on isab0
  atapci1: AMD 8111 UDMA133 controller port
  0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf
 at
  device 7.1 on pci0
  ata0: ATA channel 0 on atapci1
  ata1: ATA channel 1 on atapci1
  pci0: serial bus, SMBus at device 7.2 (no driver
  attached)
  pci0: bridge at device 7.3 (no driver attached)
  pcib2: ACPI PCI-PCI bridge at device 10.0 on
 pci0
  pci2: ACPI PCI bus on pcib2
 
  -- SCSI
 
  ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port
 
  0x8000-0x80ff,0x7800-0x78ff
  mem 0xfc89c000-0xfc89dfff irq 24 at device 10.0 on
  pci2
  ahd0: [GIANT-LOCKED]
  aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X
  67-100Mhz, 512 SCBs
  ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port
 
  0x8800-0x88ff,0x8400-0x84ff
  mem 0xfc89e000-0xfc89 irq 25 at device 10.1 on
  pci2
  ahd1: [GIANT-LOCKED]
  aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X
  67-100Mhz, 512 SCBs
  pci0: base peripheral, interrupt controller at
  device 10.1 (no driver attached)
  pcib3: ACPI PCI-PCI bridge at device 11.0 on
 pci0
  pci1: ACPI PCI bus on pcib3
  pci0: base peripheral, interrupt controller at
  device 11.1 (no driver attached)
 
 
 
   Thanks!
 
Nicole
 Ok, so it's an AMD 8111 northbridge versus an
 Adaptec onboard SCSI 
 controller.
 
 1. What release / version of FreeBSD are you using?
 You should upgrade 
 to 6.2 STABLE because there have been a variety of
 issues worked out in previous releases.

 I have a range of Versions from 6.1-Pre to 6.2-STABLE
as of a few months ago.

 2. Do you have any logs for activity during the
 hours when it locks up 
 (in particular anything interesting / fishy popping
 up)?

 Nope. That would make it too easy :)
 They commit suicide without a note.

 3. What scheduler are you using? 4BSD, ULE?

4BSD

 4. Does your machine (using the SATA controllers)
 lock up under heavy 
 load? If so, you may have a northbridge cooling
 issue that you need to 
 put a fan on. For instance, the motherboard that I
 was using for a while 
 (ASUS P5N-E SLI) was really close to my CPU
 heatsink, and there was a 
 lot of heat transfer between my northbridge and CPU
 heatsink, which was 
 raising the onboard temperatures 5~10 degrees C. The
 new motherboard 
 (ASUS P5B DLX) doesn't do that though.

 The lockups seem rather random. I have healthd
running and they never seem to show very warm. The
room is cold and the servers have great fans. Altho
healthd can seem wonky as the cpu temp has actually
gone below the minimum. Also the -2Volt line seems
very low. But some servers runs forever that way.

 At least with SCSI, since it seems to manage itself
as another layer away from the system, you get some
error messages. Sort of like windows 3.1 dropping to
dos. Verses sata issues where it's just blue screen of
death but without even some debugging code.

 I am going to try the patch chuck Swiger sent me and
see how that effects things. Also try a few
replacement sata cards. Altho that is always fun
especially in 1U servers. As well as seeing if using
SAS drives may help if I can find some cheap enough. 
 Do you think that using the ULE scheduler could
really help? 

 Thanks

  Nicole


 Cheers,
 -Garrett
 

___
freebsd-questions@freebsd.org mailing list

Re: How to solve mysterious system lockups?

2007-06-05 Thread Kris Kennaway
On Mon, Jun 04, 2007 at 04:40:56PM -0700, Nicole Harrington wrote:
 Hello
   I have several systems that are used as squid
 caching servers. I have some systems that use SCSI
 disks and some  that use SATA disks. They are
 identical in everyway except for the sata vs SCSI
 drives. 
 
  At random times, the sata based systems seem to be
 freezing. You can ping them and they respond, but you
 cannot log in. Nor are any logs processed during that
 time. 
 
  I figure it mist be something to do with the disks,
 but I am not sure how to solve it. There seems to be
 little rhyme or reason. It does not happen necessarily
 during busy times. It can happen in the middle of the
 night.
 
  Any pointers in how to track down the cause would be
 much appreciated.

See the email I sent yesterday to a similar question.

Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-05 Thread youshi10

On Tue, 5 Jun 2007, N. Harrington wrote:



--- Garrett Cooper [EMAIL PROTECTED] wrote:


N. Harrington wrote:

--- Garrett Cooper [EMAIL PROTECTED]

wrote:




N. Harrington wrote:


Hello
  I have several systems that are used as squid
caching servers. I have some systems that use

SCSI

disks and some  that use SATA disks. They are
identical in everyway except for the sata vs

SCSI

drives.

 At random times, the sata based systems seem to


be


freezing. You can ping them and they respond,

but



you


cannot log in. Nor are any logs processed during


that


time.

 I figure it mist be something to do with the


disks,


but I am not sure how to solve it. There seems

to



be


little rhyme or reason. It does not happen


necessarily


during busy times. It can happen in the middle

of



the


night.

 Any pointers in how to track down the cause

would



be


much appreciated.

 Tyan S2881 Motherboard - 4gigs mem
 Using 4 SATA (or scsi) drives
 FreeBSD amd64 6.2-STABLE.

 Thanks!

  Nicole



Nicole,
What's the driver in use for the SATA and the
SCSI drives?
-Garrett



 Hi Garret
 Here is the driver info.

-- SATA

atapci0: SiI 3114 SATA150 controller port




0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f


mem
0xfeafec00-0xfeafefff irq 17 at device 5.0 on pci3
ata2: ATA channel 0 on atapci0
ata3: ATA channel 1 on atapci0
ata4: ATA channel 2 on atapci0
ata5: ATA channel 3 on atapci0
pci3: display, VGA at device 6.0 (no driver
attached)
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci1: AMD 8111 UDMA133 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf

at

device 7.1 on pci0
ata0: ATA channel 0 on atapci1
ata1: ATA channel 1 on atapci1
pci0: serial bus, SMBus at device 7.2 (no driver
attached)
pci0: bridge at device 7.3 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 10.0 on

pci0

pci2: ACPI PCI bus on pcib2

-- SCSI

ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port



0x8000-0x80ff,0x7800-0x78ff
mem 0xfc89c000-0xfc89dfff irq 24 at device 10.0 on
pci2
ahd0: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port



0x8800-0x88ff,0x8400-0x84ff
mem 0xfc89e000-0xfc89 irq 25 at device 10.1 on
pci2
ahd1: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
pci0: base peripheral, interrupt controller at
device 10.1 (no driver attached)
pcib3: ACPI PCI-PCI bridge at device 11.0 on

pci0

pci1: ACPI PCI bus on pcib3
pci0: base peripheral, interrupt controller at
device 11.1 (no driver attached)



 Thanks!

  Nicole

Ok, so it's an AMD 8111 northbridge versus an
Adaptec onboard SCSI
controller.

1. What release / version of FreeBSD are you using?
You should upgrade
to 6.2 STABLE because there have been a variety of
issues worked out in previous releases.


I have a range of Versions from 6.1-Pre to 6.2-STABLE
as of a few months ago.


2. Do you have any logs for activity during the
hours when it locks up
(in particular anything interesting / fishy popping
up)?


Nope. That would make it too easy :)
They commit suicide without a note.


3. What scheduler are you using? 4BSD, ULE?


4BSD


4. Does your machine (using the SATA controllers)
lock up under heavy
load? If so, you may have a northbridge cooling
issue that you need to
put a fan on. For instance, the motherboard that I
was using for a while
(ASUS P5N-E SLI) was really close to my CPU
heatsink, and there was a
lot of heat transfer between my northbridge and CPU
heatsink, which was
raising the onboard temperatures 5~10 degrees C. The
new motherboard
(ASUS P5B DLX) doesn't do that though.


The lockups seem rather random. I have healthd
running and they never seem to show very warm. The
room is cold and the servers have great fans. Altho
healthd can seem wonky as the cpu temp has actually
gone below the minimum. Also the -2Volt line seems
very low. But some servers runs forever that way.

At least with SCSI, since it seems to manage itself
as another layer away from the system, you get some
error messages. Sort of like windows 3.1 dropping to
dos. Verses sata issues where it's just blue screen of
death but without even some debugging code.

I am going to try the patch chuck Swiger sent me and
see how that effects things. Also try a few
replacement sata cards. Altho that is always fun
especially in 1U servers. As well as seeing if using
SAS drives may help if I can find some cheap enough.
Do you think that using the ULE scheduler could
really help?


Don't try it in 6.x. It's not stable by any means.

7-CURRENT's getting a lot closer though, especially as of late (past week)..

-Garrett

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-04 Thread Garrett Cooper

N. Harrington wrote:

Hello
  I have several systems that are used as squid
caching servers. I have some systems that use SCSI
disks and some  that use SATA disks. They are
identical in everyway except for the sata vs SCSI
drives. 


 At random times, the sata based systems seem to be
freezing. You can ping them and they respond, but you
cannot log in. Nor are any logs processed during that
time. 


 I figure it mist be something to do with the disks,
but I am not sure how to solve it. There seems to be
little rhyme or reason. It does not happen necessarily
during busy times. It can happen in the middle of the
night.

 Any pointers in how to track down the cause would be
much appreciated.

 Tyan S2881 Motherboard - 4gigs mem
 Using 4 SATA (or scsi) drives
 FreeBSD amd64 6.2-STABLE.

 Thanks!

  Nicole
  

Nicole,
   What's the driver in use for the SATA and the SCSI drives?
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to solve mysterious system lockups?

2007-06-04 Thread N. Harrington

--- Garrett Cooper [EMAIL PROTECTED] wrote:

 N. Harrington wrote:
  Hello
I have several systems that are used as squid
  caching servers. I have some systems that use SCSI
  disks and some  that use SATA disks. They are
  identical in everyway except for the sata vs SCSI
  drives. 
 
   At random times, the sata based systems seem to
 be
  freezing. You can ping them and they respond, but
 you
  cannot log in. Nor are any logs processed during
 that
  time. 
 
   I figure it mist be something to do with the
 disks,
  but I am not sure how to solve it. There seems to
 be
  little rhyme or reason. It does not happen
 necessarily
  during busy times. It can happen in the middle of
 the
  night.
 
   Any pointers in how to track down the cause would
 be
  much appreciated.
 
   Tyan S2881 Motherboard - 4gigs mem
   Using 4 SATA (or scsi) drives
   FreeBSD amd64 6.2-STABLE.
 
   Thanks!
 
Nicole

 Nicole,
 What's the driver in use for the SATA and the
 SCSI drives?
 -Garrett

 Hi Garret
 Here is the driver info.

-- SATA

atapci0: SiI 3114 SATA150 controller port
0xbc00-0xbc07,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa80f

mem
0xfeafec00-0xfeafefff irq 17 at device 5.0 on pci3
ata2: ATA channel 0 on atapci0
ata3: ATA channel 1 on atapci0
ata4: ATA channel 2 on atapci0
ata5: ATA channel 3 on atapci0
pci3: display, VGA at device 6.0 (no driver
attached)
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci1: AMD 8111 UDMA133 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
device 7.1 on pci0
ata0: ATA channel 0 on atapci1
ata1: ATA channel 1 on atapci1
pci0: serial bus, SMBus at device 7.2 (no driver
attached)
pci0: bridge at device 7.3 (no driver attached)
pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0
pci2: ACPI PCI bus on pcib2

-- SCSI

ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 
0x8000-0x80ff,0x7800-0x78ff
mem 0xfc89c000-0xfc89dfff irq 24 at device 10.0 on
pci2
ahd0: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 
0x8800-0x88ff,0x8400-0x84ff
mem 0xfc89e000-0xfc89 irq 25 at device 10.1 on
pci2
ahd1: [GIANT-LOCKED]
aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X
67-100Mhz, 512 SCBs
pci0: base peripheral, interrupt controller at
device 10.1 (no driver attached)
pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0
pci1: ACPI PCI bus on pcib3
pci0: base peripheral, interrupt controller at
device 11.1 (no driver attached)



 Thanks!

  Nicole



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]