Discussion:
TRAP 000e in os2lvm
(too old to reply)
Andi B.
2007-05-21 19:10:51 UTC
Permalink
Raw Message
I sometimes get lvm traps. This last occoured when I tried to access a CF-Card
with 3 HPFS and JFS partitions via a card reader.

INFORMATION ZUR ALARMNACHRICHT (TRAP)
OS/2-Kernel-Überarbeitung 14.104a_UNI
Exception in module: OS2LVM
TRAP 000e ERRCD=0000 ERACC=**** ERLIM=********
EAX=00000000 EBX=001f0030 ECX=0000ffff EDX=fdc180f0
ESI=00000000 EDI=fdcf300c EBP=f96d7d58 FLG=00012292
CS:EIP=0168:fd4419b2 CSACC=c09b CSLIM=ffffffff
SS:ESP=1550:f96d7d28 SSACC=c093 SSLIM=ffffffff
DS=0160 DSACC=c093 DSLIM=ffffffff CR0=8001001b
ES=0160 ESACC=c093 ESLIM=ffffffff CR2=00000068
FS=0000 FSACC=**** FSLIM=********
GS=0000 GSACC=**** GSLIM=********

No Symbols Found


Buildlevel of os2lvm.dmd is -
Signature: @#IBM:14.105#@ IBM Logical Volume Manager
Vendor: IBM
Revision: 14.105
File Version: 14.105
Description: IBM Logical Volume Manager


Hints?

Regards, Andi
Hendrik Schmieder
2007-05-28 16:20:27 UTC
Permalink
Raw Message
Post by Andi B.
I sometimes get lvm traps. This last occoured when I tried to access a CF-Card
with 3 HPFS and JFS partitions via a card reader.
INFORMATION ZUR ALARMNACHRICHT (TRAP)
OS/2-Kernel-Überarbeitung 14.104a_UNI
Exception in module: OS2LVM
TRAP 000e ERRCD=0000 ERACC=**** ERLIM=********
EAX=00000000 EBX=001f0030 ECX=0000ffff EDX=fdc180f0
ESI=00000000 EDI=fdcf300c EBP=f96d7d58 FLG=00012292
CS:EIP=0168:fd4419b2 CSACC=c09b CSLIM=ffffffff
SS:ESP=1550:f96d7d28 SSACC=c093 SSLIM=ffffffff
DS=0160 DSACC=c093 DSLIM=ffffffff CR0=8001001b
ES=0160 ESACC=c093 ESLIM=ffffffff CR2=00000068
FS=0000 FSACC=**** FSLIM=********
GS=0000 GSACC=**** GSLIM=********
No Symbols Found
Buildlevel of os2lvm.dmd is -
Vendor: IBM
Revision: 14.105
File Version: 14.105
Description: IBM Logical Volume Manager
Hints?
Can't say anything about the LVM problem,
but why are yiou usning an UNI kernel instead of the W4 kernel ?

Hendrik
Andi B.
2007-06-02 11:59:53 UTC
Permalink
Raw Message
Post by Hendrik Schmieder
Can't say anything about the LVM problem,
but why are yiou usning an UNI kernel instead of the W4 kernel ?
Hendrik
Hm, last time I upgraded the kernel I searched for the right one and as I
remember correct, the difference between UNI and W4 is small and I should use
the UNI kernel if I do not have a special old 586 or 486 processor. But maybe
I'm completly wrong on this.

I remember Scott has posted some time ago which kernel to use but I couldn't
find this post anymore. So if you know for sure it's better to use the W4
instead of the UNI kernel, I will install the W4.

Regards,
Andi
Doug Bissett
2007-06-03 21:18:55 UTC
Permalink
Raw Message
Post by Andi B.
Post by Hendrik Schmieder
Can't say anything about the LVM problem,
but why are yiou usning an UNI kernel instead of the W4 kernel ?
Hendrik
Hm, last time I upgraded the kernel I searched for the right one and as I
remember correct, the difference between UNI and W4 is small and I should use
the UNI kernel if I do not have a special old 586 or 486 processor. But maybe
I'm completly wrong on this.
I remember Scott has posted some time ago which kernel to use but I couldn't
find this post anymore. So if you know for sure it's better to use the W4
instead of the UNI kernel, I will install the W4.
Regards,
Andi
If I remember correctly, Scott basically said, that the UNI kernel
should only be used with WSEB, on an SMP system, when you need to run
in UNI mode. Otherwise, you should use either the SMP kernel (for
obvious reasons), or the W4 kernel.

Whether that will make any difference to your problem, or not, I don't
know, but it may be worth trying...
--
From the eComStation 1.2 of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Scott G
2007-06-10 17:38:17 UTC
Permalink
Raw Message
Post by Andi B.
Hm, last time I upgraded the kernel I searched for the right one and as
I remember correct, the difference between UNI and W4 is small and I
should use the UNI kernel if I do not have a special old 586 or 486 processor.
Specifically the 486sx needs the W4 kernel, otherwise correct.

The trap 000e is presumably due to some bogosity in the USB RM driver.
Get the latest one or something and hope for the best.... Personally,
I'm using Linux or Windoze these days (depending if I need obscure
Windoze-only device support).
-Scott

Steven Levine
2007-05-31 03:38:28 UTC
Permalink
Raw Message
In <***@news.aic.at>, on 05/21/2007
at 09:10 PM, "Andi B." <***@gmx.net> said:

Hi,
Post by Andi B.
INFORMATION ZUR ALARMNACHRICHT (TRAP)
OS/2-Kernel-Überarbeitung 14.104a_UNI
Exception in module: OS2LVM
TRAP 000e ERRCD=0000 ERACC=**** ERLIM=********
EAX=00000000 EBX=001f0030 ECX=0000ffff EDX=fdc180f0
ESI=00000000 EDI=fdcf300c EBP=f96d7d58 FLG=00012292
CS:EIP=0168:fd4419b2 CSACC=c09b CSLIM=ffffffff
SS:ESP=1550:f96d7d28 SSACC=c093 SSLIM=ffffffff
DS=0160 DSACC=c093 DSLIM=ffffffff CR0=8001001b
ES=0160 ESACC=c093 ESLIM=ffffffff CR2=00000068
FS=0000 FSACC=**** FSLIM=********
GS=0000 GSACC=**** GSLIM=********
I'd need to know the load address of os2lvm.dmd before I could hazard a
guess.

If you use

<http://home.earthlink.net/~steve53/os2diags/DumpTrapScreen.zip>

to scan the first diskette of a trap dump, there's often so useful data.
Of course, a system dump is always best. It's a lot easier to see the
context of the trap. For example, the trap could be some driver passing
bad data to os2lvm.dmd.

Regards,

Steven
--
--------------------------------------------------------------------------------------------
Steven Levine <***@earthlink.bogus.net> MR2/ICE 3.00 beta 05 #10183
eCS/Warp/DIY/14.103a_W4 www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
Andi B.
2007-06-02 11:53:20 UTC
Permalink
Raw Message
....
Post by Steven Levine
I'd need to know the load address of os2lvm.dmd before I could hazard a
guess.
Too bad, a had another trap the day before yesterday and so my dump file is
overwritten. This was a trap while playing aroung with Warpvision and as video
playback is not so important on OS/2 - eComStation I don't want bothering you
with this.

The first trap in os2lvm occures when there was a CF-Card inserted in an USB
card reader. This usually works, but sometimes generates a trap.

If I had the first dump file and we were able to identify the drivers involved
(lvm or usb i suppose), would be there any chance to improve them? We do not
have access to the sources I think, so is there any possibility to repair bugs?
I ask this because I'm not sure if it makes any sense to post traps here
anymore. Of course, if there is only a little chance to improve our favorite
system, I'll do my very best to deliver all information and help as much I can
next time I get this trap.

Regards,
Andi
Steven Levine
2007-06-03 03:32:17 UTC
Permalink
Raw Message
In <***@news.aic.at>, on 06/02/2007
at 01:53 PM, "Andi B." <***@gmx.net> said:

Hi,
Post by Andi B.
If I had the first dump file and we were able to identify the drivers
involved (lvm or usb i suppose), would be there any chance to improve
them? We do not have access to the sources I think, so is there any
possibility to repair bugs?
The simple answer is you will never know unless someone looks at the dump
file.

While it's true that we don't have access to all the sources, we have
access to some of the driver sources and there's nothing to prevent one
from making binary patches.


Regards,

Steven
--
--------------------------------------------------------------------------------------------
Steven Levine <***@earthlink.bogus.net> MR2/ICE 3.00 beta 05 #10183
eCS/Warp/DIY/14.103a_W4 www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
Loading...