Blade 2000 error message - DESC: The transmitting device sent aninvalid reques

#1 (**permalink**) 07-18-2008, 10:40 AM

I've just patched my Blade 2000 and noticed the following error. But on
looking more closely, I see it has happened before, so I doubt it is the
result of a patch.

I'm not noticing any ill effects, but am obviously concerned there might be.

The machine has:

2 x 1.2 GHz CPUs
2 x 147 GB fiber disks (not Sun ones)
8 GB RAM.
USB-2 card
2 x Western Digital 1 TB external disks (SATA disks, connected to the
USB-2 card).
Internal SCSI card
DDS-4 tape drive.
IDE based DVD-rewriter, on a SCSI->IDE converter.
SunPCi III card

Doing a Google, I have seen others report similar messages, although no
conclusive idea of what it really means.

Is there a way to get the OBP version without rebooting the machine?

(I know the cause of the samba / port 137 issue below, and am not
worried about that. More worrying is the hardware related warning of
'SEVERITY: Critical')

Dae

Jul 17 09:58:40 kestrel xntpd[267]: [ID 266339 daemon.notice] using
kernel phase-lock loop 0041, drift correction 0.00000
Jul 17 09:58:40 kestrel xntpd[267]: [ID 266339 daemon.notice] using
kernel phase-lock loop 0041, drift correction -19.89700
Jul 17 09:58:55 kestrel svc.startd[7]: [ID 652011 daemon.warning]
svc:/network/wins:default: Method "/usr/bin/kill `cat
/var/samba/locks/nmbd.pid`" failed with exit status 2.
Jul 17 09:58:55 kestrel last message repeated 2 times
Jul 17 09:58:55 kestrel svc.startd[7]: [ID 748625 daemon.error]
network/wins:default failed: transitioned to maintenance (see 'svcs -xv'
for details)
Jul 17 09:59:09 kestrel fmd: [ID 441519 daemon.error] SUNW-MSG-ID:
PCIEX-8000-5Y, TYPE: Fault, VER: 1, SEVERITY: Critical
Jul 17 09:59:09 kestrel EVENT-TIME: Sat Jun 14 07:39:41 BST 2008
Jul 17 09:59:09 kestrel PLATFORM: SUNW,Sun-Blade-1000, CSN: -, HOSTNAME:
kestrel
Jul 17 09:59:09 kestrel SOURCE: eft, REV: 1.16
Jul 17 09:59:09 kestrel EVENT-ID: 22a84448-5757-6797-e98c-b8ca7fbb4380
Jul 17 09:59:09 kestrel DESC: The transmitting device sent an invalid
request.
Jul 17 09:59:09 kestrel Refer to http://sun.com/msg/PCIEX-8000-5Y for
more information.
Jul 17 09:59:09 kestrel AUTO-RESPONSE: One or more device instances may
be disabled
Jul 17 09:59:09 kestrel IMPACT: Loss of services provided by the device
instances associated with this fault
Jul 17 09:59:09 kestrel REC-ACTION: Ensure that the latest drivers and
patches are installed. Otherwise schedule a repair procedure to replace
the affected device(s). Use fmdump -v -u <EVENT_ID> to identify the
devices or contact Sun for support.
Jul 17 09:59:15 kestrel /usr/sbin/vold[754]: [ID 848318 daemon.error]
rmdisk: open of "/dev/rdsk/c5t0d0s0"; Device busy
Jul 17 09:59:15 kestrel /usr/sbin/vold[754]: [ID 848318 daemon.error]
rmdisk: open of "/dev/rdsk/c6t0d0s0"; Device busy
Jul 17 09:59:16 kestrel nmbd[836]: [ID 702911 daemon.error] [2008/07/17
09:59:16, 0] lib/util_sock.c

830)
Jul 17 09:59:16 kestrel nmbd[836]: [ID 702911 daemon.error] bind
failed on port 137 socket_addr = 192.168.0.10.
Jul 17 09:59:16 kestrel nmbd[836]: [ID 702911 daemon.error] Error =
Cannot assign requested address

Burring the command suggested, I'm presented with this lot, which means
very little to me.

$ fmdump -v -u 22a84448-5757-6797-e98c-b8ca7fbb4380
TIME UUID SUNW-MSG-ID
Jun 14 07:39:42.4076 22a84448-5757-6797-e98c-b8ca7fbb4380 PCIEX-8000-5Y
20% fault.io.pci.device-invreq

Problem in:
hc://

roduct-id=SUNW,Sun-Blade-1000:server-id=kestrel/motherboard=0/hostbridge=0/pcibus=0/pcidev=4/pcifn=0
Affects: dev:////pci@8,600000/SUNW,qlc@4
FRU: hc:///component=MB
Location: MB

20% fault.io.pci.device-invreq

Problem in:
hc://

roduct-id=SUNW,Sun-Blade-1000:server-id=kestrel/motherboard=0/hostbridge=0/pcibus=0/pcidev=1/pcifn=3
Affects: dev:////pci@8,600000/firewire@1,3
FRU:
hc://