If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):
Capturing an OSR5 panic
From: Bela Lubkin <belal@sco.com>
Subject: Re: Merge Installation/Configuration Problem on OpenServer 5.0.7
Date: Thu, 7 Aug 2003 02:45:56 GMT
References: <20030806020007.GH24551@sco.com> <20030806104945.04959.00000821@mb-m26.aol.com>
Transpower wrote:
> Bela:
>
> >Show output of `hwconfig -h`, for
> >starters. `hw -v -r pci` would be good, but it's much too long to post.
> >Also `ls -l /dev/tty2a`, just in case it's simply a wrong device node.
You are still assuming that your readers remember everything about the
thread. Please quote more, enough for a completely new reader of the
thread to know what's going on by reading just your one message.
We're still under the now irrelevant subject line of "Merge
Installation/Configuration Problem on OpenServer 5.0.7", so that doesn't
give me any clues.
I vaguely remember that maybe you were having trouble when accessing the
serial port. Yes, that must be it.
> device address vec dma comment
> ======== ============= === === ================================================
> kernel - - - rel=3.2v5.0.7 kid=2003-02-18
> cpu - - - unit=1 family=6 type=Pentium Pro
> cpuid - - - unit=1 vend=GenuineIntel step=sA1
> fpu - 13 - unit=1 type=80387-compatible
> pci 0xcf8-0xcff - - am=1 sc=0 buses=3
> eisarom - - - eisa (1.3.0)
> PnP - - - nodes=0
> clock - - - type=TSC/199.431783Mhz
> serial 0x3f8-0x3ff 4 - unit=0 type=Standard nports=1 base=0 16550A/16
> serial 0x2f8-0x2ff 3 - unit=1 type=Standard nports=1 base=8 16550A/16
> console - - - unit=vga type=0 num=12 scoansi=0 scroll=50
> adapter 0xf000-0xf0ff 15 - type=alad ha=0 bus=0 id=7 fts=sto
> adapter 0xf400-0xf4ff 10 - type=alad ha=1 bus=0 id=7 fts=sto
> floppy 0x3f2-0x3f7 6 2 unit=0 type=135ds18
> floppy - - - unit=1 type=48ds9
> kbmouse 0x60-0x64 12 - type=Keyboard|PS/2 mouse id=0x00
> parallel 0x378-0x37a 7 - unit=0
> udi - - - UDI environment
> adapter - - - ha=0 type=usb_msto UDI SCSI HBA
> OlyTune - - - Pacific CodeWorks, Inc. System TuneUp
> OlyTune - - - Olympus TuneUp Release 6.0.0P
> dcxf0 0xfc00-0xfc7f 9 - type=DE500-AA addr=00:00:F8:09:A5:CC
> cd-rom - - - type=S ha=0 id=3 lun=0 bus=0 ht=alad unit=0
> tape - - - type=S ha=1 id=6 lun=0 bus=0 ht=alad unit=0
> disk - - - type=S ha=0 id=0 lun=0 bus=0 ht=alad unit=0
> Sdsk - - - cyls=8942 hds=255 secs=63 unit=0 fts=stdb
> Sdsk-0 - - - Vnd=MAXTOR Prd=ATLASU320_73_WLS Rev=B120
> usb_ehci - 16 - PCI bus=0 dev=13 func=2
> usb_ohci - 17 - PCI bus=0 dev=13 func=0
> usb_ohci - 18 - PCI bus=0 dev=13 func=1
> cpu - 255 - unit=2 family=6 type=Pentium Pro
> cpuid - - - unit=2 vend=GenuineIntel step=sB1
> fpu - - - unit=2 type=80
Hmmm, 200MHz Pentium Pro with USB 2.0 -- odd combo.
Ok, so the two serial ports are on IRQ 4 and 3, as expected. There are
three USB HCIs on three fake IRQs. To get their real IRQs, run `hw -v
-r pci > /tmp/pci`. Look through the entries for the three with
ClassCode values of 0x0c0310 and 0x0c0320 (they'll also be recognizable
by their DeviceNum 13, Function 0/1/2, and Bus 0). Note the
InterruptLine value for each of those.
Are any of them pointed at IRQ 3 or 4?
If so: go into BIOS setup and insist that IRQs 3 & 4 are reserved for
"ISA" or "Legacy" or whatever your BIOS calls them. Or, alternatively,
take the USB add-on card out of the bus.
> crw-rw-rw- 1 bin bin 5, 8 Jul 17 1996 /dev/tty2a
That looks fine.
> >Do it from tty01 (Ctrl-Alt-F1), see if there's a
> >panic message. If so, post it here (complete).
>
> Unexpected trap in kernel mode [followed by a group of hex addresses I hope
> you don't need]
Well, yeah, the hex addresses are the meat of the thing. But they also
need to be translated locally on your system, so just seeing the hex
numbers wouldn't help much anyway. Write down the "eip" number, then
run:
# crash
> ts f000baaa
> quit
(using the eip number). That should give you a symbol name and offset.
What is it?
> PANIC: K_trap -kernel mode trap 0x0000000E
> Cannot dump 32671 pages to dump dev hd (1/41)
> space for only 25000 pages
> Dump not completed
> ** Safe to Power Off **
> -or-
> ** Press Any Key to Reboot **
This shows that you have less swap space than RAM. That's fine for
normal operation, but it prevents you from capturing a crash dump. A
captured crash dump would help debug this. So, do this. Boot with:
Boot
: defbootstr mem=1m-96m
Then provoke the panic.
Then reboot (no special bootstring), go to single-user mode, run:
# crash
> panic -w /tmp/panic
> quit
Post the contents of /tmp/panic.
>Bela<
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)

| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 2 | 3 | 11 | 192 | 1,263 |
/Bofcusm/2267.html copyright 1997-2004 Bela Lubkin All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Add your comments