Strange Behaviour

[pgouveia]

4rd

tg3.c:v3.59.1 (August 25, 2006)
ACPI: PCI Interrupt 0000:04:04.0[A] -> GSI 26 (level, low) -> IRQ 16
eth0: Tigon3 [partno(BCM95780) rev 8100 PHY(5780)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:4d:73:80
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76144000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:04:04.1[B] -> GSI 27 (level, low) -> IRQ 17
eth1: Tigon3 [partno(BCM95780) rev 8100 PHY(5780)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:4d:73:81
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76144000] dma_mask[64-bit]
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 18
e100: eth2: e100_probe: addr 0xff6eb000, irq 18, MAC addr 00:E0:81:4D:729
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
sata_svw 0000:01:0e.0: version 1.07
ACPI: PCI Interrupt 0000:01:0e.0[A] -> GSI 11 (level, low) -> IRQ 11
ata1: SATA max UDMA/133 cmd 0xF8874000 ctl 0xF8874020 bmdma 0xF8874030 irq 11
ata2: SATA max UDMA/133 cmd 0xF8874100 ctl 0xF8874120 bmdma 0xF8874130 irq 11
ata3: SATA max UDMA/133 cmd 0xF8874200 ctl 0xF8874220 bmdma 0xF8874230 irq 11
ata4: SATA max UDMA/133 cmd 0xF8874300 ctl 0xF8874320 bmdma 0xF8874330 irq 11
ata1: SATA link down (SStatus 4)
scsi1 : sata_svw
ata2: SATA link down (SStatus 4)
scsi2 : sata_svw
ata3: SATA link down (SStatus 4)
scsi3 : sata_svw
ata4: SATA link down (SStatus 4)
scsi4 : sata_svw
ACPI: PCI Interrupt 0000:01:0e.1[A] -> GSI 11 (level, low) -> IRQ 11
3ware 9000 Storage Controller device driver for Linux v2.26.08.002-2.6.17.
ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 30 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:07:00.0 to 64
3w-9xxx: scsi5: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:.
scsi5 : 3ware 9000 Storage Controller
3w-9xxx: scsi5: Found a 3ware 9000 Storage Controller at 0xff5ff000, IRQ: 19.
3w-9xxx: scsi5: Firmware FE9X 3.08.00.016, BIOS BE9X 3.08.00.004, Ports: 16.
Vendor: AMCC Model: 9650SE-16M DISK Rev: 3.08
Type: Direct-Access ANSI SCSI revision: 05
sdb : very big device. try to use READ CAPACITY(16).
SCSI device sdb: 27343454208 512-byte hdwr sectors (13999849 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back, no read (daft)
sdb : very big device. try to use READ CAPACITY(16).
SCSI device sdb: 27343454208 512-byte hdwr sectors (13999849 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back, no read (daft)
sdb: unknown partition table
sd 5:0:0:0: Attached scsi disk sdb
Loading iSCSI transport class v2.0-754.
iscsi: registered transport (tcp)
Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006)
bonding: MII link monitoring set to 50 ms
bonding: bond0 is being deleted...
PM: Writing back config space on device 0000:04:04.0 at offset b (was 166814e4, writing 166a14e4)
PM: Writing back config space on device 0000:04:04.0 at offset 3 (was 804000, writing 804010)
PM: Writing back config space on device 0000:04:04.0 at offset 2 (was 2000000, writing 2000010)
PM: Writing back config space on device 0000:04:04.0 at offset 1 (was 2b00000, writing 2b00106)
PM: Writing back config space on device 0000:04:04.1 at offset b (was 166814e4, writing 166a14e4)
PM: Writing back config space on device 0000:04:04.1 at offset 3 (was 804000, writing 804010)
PM: Writing back config space on device 0000:04:04.1 at offset 2 (was 2000000, writing 2000010)
PM: Writing back config space on device 0000:04:04.1 at offset 1 (was 2b00000, writing 2b00106)
tg3: eth1: Link is up at 1000 Mbps, full duplex.
tg3: eth1: Flow control is on for TX and on for RX.
program scsiinfo is using a deprecated SCSI ioctl, please convert it to SG_IO
program scsiinfo is using a deprecated SCSI ioctl, please convert it to SG_IO
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on dm-6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
drbd: initialised. Version: 8.0.8 (api:86/proto:86)
drbd: GIT-hash: bd3e2c922f95c4fa0dca57a4f8c24bf8b249cc02 build by root@develsystem, 2008-02-02 12:02:18
drbd: registered as block device major 147
drbd: minor_table @ 0xc3a14800
kjournald starting. Commit interval 5 seconds
EXT3 FS on ram15, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
program scsiinfo is using a deprecated SCSI ioctl, please convert it to SG_IO
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Filesystem "dm-5": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-5
Ending clean XFS mount for filesystem: dm-5
Adding 4194296k swap on /dev/vg+vg00/nas_swap. Priority:-1 extents:1 across:4194296k
scst: Attached SCSI target mid-level at scsi0, channel 0, id 0, lun 0, type 0
scst: Attached SCSI target mid-level at scsi5, channel 0, id 0, lun 0, type 0
scst: SCST version 0.9.6-pre3 loaded successfully (max mem for commands 1012 Mb)
scst: Enabled features: TRACING
scst: Virtual device handler vdisk for type 0 registered successfully
scst: Virtual device handler vdisk_blk for type 0 registered successfully
scst: Virtual device handler vcdrom for type 5 registered successfully
iSCSI Enterprise Target Software - version 0.4.15
iotype_init(92) register fileio
iotype_init(92) register blockio
iotype_init(92) register nullio

Hello TO-L

The system have 2 x Opteron.
We already check the RAID health and everything is ok !!
I will check the multi processor config.

Thanks

PG

[To-M]

Ok, I see some IRQ issues but not sure if this is the one causing the hangs. Typically some hangs are related to a physical issue (CPU, Memory....). If possible try moving the
3Ware to another slot closer to the CPU.

Then I want you to go back in to the console tools and then boot options.
Then select Boot Parameters and select all 3 options. Then reboot.

Also update to the latest version 5_0_47_build_3200 but you may have done so already.