Crashes are not simple to debug... the only choice is to raise a ticket with Brocade. You do have two option:

1. do an upgrade to a later release (maybe 10.2.01g in case you are at the 10.2.01 release stream) and see whether the problem goes  away or not
2. raise a ticket with Brocade.

R, Oliver

At 22:52 19.04.2009, Farooq Butt wrote:
There is a horrible log message displayed frequently in my ServerIron 450 ... during application usage
 
WSM MODULE (1) App CPU    0 MB SHM, 2 Application Processors
        CPU 1 in state of WSM_STATE_RUNNING
        CPU 2 in state of UNKNOWN
WARN: WSM module App CPU 2 at slot 1 rebooted, state=48000280
(1898484)(1)WSM crash
WARN: wsm App CPU 2 at slot 1 crashed(0)
WARN: bring down all App CPU at slot 1 and restart them
pos_word_write(0, 080002a0, 00000000) failed after 2 trial(read as 480002a0)
pos_word_write(0, 08000280, 00000000) failed after 2 trial(read as 48000280)
 
 
Please guide me about he fault ... thanx in advance




--------------------------------------------------------------------
root: [email protected]
http-tunnel: named,bind,syslogd
bit.bucket: /dev/proxy-null
procmail:
"|/usr/local/bin/procmail"

The latest revision of this advisory is available at

ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-06:13.sendmail.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (FreeBSD)

iD8DBQFEIXZWFdaIBMps37IRAldYAJ9nd+wQMJlQObUuio5tBEFwD0ULwwCbB2eI
u3JkyVwHx4WOgmZkg9QKang=
=d3RW
-----END PGP
SIGNATURE-----




See all the ways you can stay connected to friends and family
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp

Reply via email to