News Group Posts

serial panic capture

Disabling usb

From: Bela Lubkin <belal@sco.com>
Subject: Re: Merge Installation/Configuration Problem on OpenServer 5.0.7
Date: Fri, 8 Aug 2003 01:39:12 GMT
References: <20030807215253.GK24551@sco.com>
<20030807200843.03007.00001256@mb-m01.aol.com> 

Transpower wrote:

> The current system--serial ports and USB ports--works perfectly under Windows
> XP.  Therefore, the problem is with SCO.

Agreed.  I'm trying to find out what the problem is, using the tools
available.

> >Since the USB stuff isn't working anyway, I suggest you take the card
> >out and see if the serial port gets better.  It might.
> 
> Quite probably; however, I'm using all of the USB devices and serial ports with
> XP just fine, so I'm not going to mess with the hardware right now.  Next week
> I hope to have the new hardware here and will retest with SCO.

Another way you can disable USB is this.  Boot with:

  Boot
  : defbootstr disable=usb_uhci,usb_ohci,usb_ehci

Then try to access the serial port.  If the problem was due to an
interaction with USB, the serial port should now work.  If it panics the
same as before, it probably isn't USB.

> >Then write down the whole set of numbers and post them here.  We're
> >unable to read your mind.
> >
> 
> Here is the whole set:
> 
> cr0 0x8001003B     cr2  0x00000000 cr3 0x00002000  tlb  0x00000000
> ss  0x00006A28     uesp 0xF008CF75 efl 0x00010216  ipl  0x00000007
> cs  0x00000158     eip  0x00000000 err 0x00000000  trap 0x0000000E 
> eax 0xF0300CBD  ecx  0x00000002 edx 0xF02E6A28  ebx  0xF0328260
> esp 0xE0000998  ebp  0xE00009B4 esi 0x00000008     edi  0x00000002
> ds  0x00000160  es   0x00000160 fs  0x00000000  gs   0x00000000
> cpu 0x00000001
> 
> ># crash -d /dev/swap
> >  > panic -w /tmp/panic
> 
> Unfortunately the crash command responds with 'dumpfile = /dev/swap, namelist =
> /unix, outfile = stdout, 0xdfffc03c is an invalid current process adress.' 
> Whatever that means...

It basically means that it looks like a corrupt dump to `crash`.  Well,
one of the numbers up there looks weird: the "uesp" value looks like
what should be in "eip".  So, run:

  # crash       # not -d /dev/swap
  > ts f008cf75
  > quit

What's the symbol+offset?

Two other tools might be able to make more sense of the dump; it's not
terribly likely, but worth a try anyway.  One:

  # scodb -d /dev/swap
  scodb> stack

Two:

  # sysdump -i /dev/swap -a

Both should be attemped immediately after you've forced another panic,
and gone straight to single-user mode afterwards.  Otherwise /dev/swap
may already have been overwritten by system activity.

> Hey at least my UNIX accounting system and database files still work.  ;)

Good...

>Bela<

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.