01-29-2014
Thanks Corona,
This is the second time this has occured. The first time HP ASR reset the server, we then disabled ASR hoping that next time around we would be able to get some meaningful messages before resetting the server.
I don' think there's much we can do besides a total blind firmware/patch update (which won't happen!).
10 More Discussions You Might Find Interesting
1. Programming
I am using gdb to examine a core file but the output contains only the method addresses in hex.
Is there anyway to translate these addresses to a human-readable form? :confused: (0 Replies)
Discussion started by: ciregbu
0 Replies
2. Programming
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Discussion started by: dmirza
2 Replies
3. UNIX for Advanced & Expert Users
Hi all,
One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into... (9 Replies)
Discussion started by: ranj@chn
9 Replies
4. Filesystems, Disks and Memory
I'm on solaris 8. I need to check the stack trace inside my C program. I don't have printstack or walkstack. I tested getcontext and it works. But how do I get the symbols from "stack_t" ? Help please. Many thanks! (4 Replies)
Discussion started by: rydahl
4 Replies
5. Solaris
Hello ,
I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV.
On my system only mdb works. Please help me to retrieve the stack trace from this core file.
I am novice to mdb and its nuaunces. Please help me with... (2 Replies)
Discussion started by: rmv
2 Replies
6. AIX
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Discussion started by: Sachin1987
2 Replies
7. Shell Programming and Scripting
Hi All
Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable -
#! /bin/bash
error_exit()
{
echo "======================="
echo $1
echo... (4 Replies)
Discussion started by: steadyonabix
4 Replies
8. UNIX for Dummies Questions & Answers
I have a multithreaded usermode program(actually a daemon) which is in hanged state.
To debug it I tried attaching the process to gdb, but the gdb hangs.
gstack also gets hanged.
I peeped into the proc file system and saw the process to be in sleeping state.
/proc/sysrq-trigger I guess... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
9. Programming
I have a C program which is running as daemon and has some threads.
The program is running on dual core cpu and it may happen that different threads may run on different cpu core.
The problem is sometimes it crashes with some heap memory corruption probably between threads.
GDB command(t a a... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
10. Shell Programming and Scripting
I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it.
To get the files that needs to... (6 Replies)
Discussion started by: chipmunken
6 Replies
IWN(4) BSD Kernel Interfaces Manual IWN(4)
NAME
iwn -- Intel Wireless WiFi Link 4965/1000/5000/5150/5300/6000/6050 IEEE 802.11n driver
SYNOPSIS
To compile this driver into the kernel, include the following lines in your kernel configuration file:
device iwn
device pci
device wlan
device firmware
You also need to select a firmware for your device. Choose one from:
device iwn4965fw
device iwn1000fw
device iwn5000fw
device iwn5150fw
device iwn6000fw
device iwn6050fw
Or you can use
device iwnfw
to include them all.
Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5):
if_iwn_load="YES"
iwn4965fw_load="YES"
iwn1000fw_load="YES"
iwn5000fw_load="YES"
iwn5150fw_load="YES"
iwn6000fw_load="YES"
iwn6050fw_load="YES"
DESCRIPTION
The iwn driver provides support for Intel Wireless WiFi Link 4965, 1000, 5000 and 6000 series of PCI-Express network adapters. iwn supports
station, adhoc, and monitor mode operation. Only one virtual interface may be configured at any time. For more information on configuring
this device, see ifconfig(8).
This driver requires the firmware built with the iwnfw module to work.
EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
ifconfig wlan create wlandev iwn0 inet 192.168.0.20
netmask 0xffffff00
Join a specific BSS network with network name ``my_net'':
ifconfig wlan create wlandev iwn0 ssid my_net up
Join a specific BSS network with 64-bit WEP encryption:
ifconfig wlan create wlandev iwn0 ssid my_net
wepmode on wepkey 0x1234567890 weptxkey 1 up
Join a specific BSS network with 128-bit WEP encryption:
ifconfig wlan create wlandev iwn0 wlanmode adhoc ssid my_net
wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
DIAGNOSTICS
iwn%d: device timeout The driver will reset the hardware. This should not happen.
iwn%d: firmware error The onboard microcontroller crashed for some reason. The driver will reset the hardware. This should not happen.
iwn%d: timeout waiting for firmware initialization to complete The onboard microcontroller failed to initialize in time. This should not
happen.
iwn%d: could not load firmware image '%s' The driver failed to load the firmware image using the firmware(9) subsystem. Verify the iwnfw(4)
firmware module is present.
iwn%d: could not load boot firmware An attempt to upload the boot firmware image to the onboard microcontroller failed. This should not
happen.
iwn%d: could not load microcode An attempt to upload the microcode image to the onboard microcontroller failed. This should not happen.
iwn%d: could not load main firmware An attempt to upload the main firmware image to the onboard microcontroller failed. This should not
happen.
SEE ALSO
iwnfw(4), pci(4), wlan(4), wlan_ccmp(4), wlan_tkip(4), wlan_wep(4), ifconfig(8), wpa_supplicant(8)
AUTHORS
The original iwn driver was written by Damien Bergamini <damien.bergamini@free.fr>
BSD
July 20, 2010 BSD