System freeze

Victor Richardson

unread,

Feb 23, 2000, 3:00:00 AM2/23/00

to

I am having an intermittent problem with a
2.6(generic) firewall system locking up. As people
have pointed out on this newsgroup to me, my error
message at system sleep - " apm0: APM set power
state: parameter out of range(10)" error is a result
of the battery possibly gone bad. Unfortunately, it
seems Compaq(Presario 9548) years ago thought it was
good to permanently attatch it to the motherboard.

The power error does not seem to immediately affect
connectivity for my NAT'd host, but when I return
after a few hours my client can't pass packets thru
the firewall. No ping between the OpenBSD box and
Win95, although the firewall can see the "real"
world. If I try to reload the ipf rules with a "ipf
-Fa -f /etc/ipf.rules", I get a return like
unexpected "-from". Adding a "-E" to the end returns
ipf is already initialized(makes sense). So
rebooting is the only recourse(in my limited
knowledge).

When the system reboots everything goes smoothly
until after:

Scsibus0 at atapiscsi:0: 2 targets
Wdc_atapi_intr_drq : Unexpectedly in the command
phase ; Please report this

then later

Sd0(pciide0:1:0): lost interrrupt
type: atapi
c_bcount:0
c_skip:0

and then freezes. If I cut power and reboot,
sometimes it freezes again, other times it boots
smoothly. Dmesg follows:

OpenBSD 2.6 (GENERIC) #696: Tue Nov 2 01:46:05 MST
1999

der...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

cpu0: F00F bug workaround installed
cpu0: Intel Pentium (P54C) ("GenuineIntel"
586-class) 100 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8
BIOS mem = 654336 conventional, 15728640 extended
real mem = 16384000
avail mem = 10985472
using 225 buffers containing 921600 bytes of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(af) BIOS, date 08/24/95
bios0: diskinfo 0xe055800c cksumlen 1 memmap
0xe0558088 pciinfo 0xe05580d0 apminfo 0xe05580ec
apm0 at bios0: Power Management spec V1.1
apm0: AC on, no battery
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Opti 82C557 Host"
rev 0x11
pcib0 at pci0 dev 1 function 0 "Opti 82C558 PCI-ISA"
rev 0x11
"S3 Trio32/64" rev 0x40 at pci0 dev 2 function 0 not
configured
vr0 at pci0 dev 4 function 0 "VIA Rhine/RhineII" rev
0x06: irq 11 address 00:80:c8:e5:a5:31
vr0: autoneg complete, link status good
(half-duplex, 10Mbps)
vr1 at pci0 dev 5 function 0 "VIA Rhine/RhineII" rev
0x06: irq 11 address 00:50:ba:ab:c9:7a
vr1: autoneg complete, link status good
(full-duplex, 100Mbps)
pciide0 at pci0 dev 20 function 0 "Opti 82C621 IDE"
rev 0x11: DMA (unsupported), channel 0 wired to
compatibility, channel 1 wired to compatibility
pciide0: channel 0 interrupting at irq 14
wd0 at pciide0 channel 0 drive 0: <SAMSUNG SV0432A>
wd0: can use 16-bit, PIO mode 4
wd0: 16-sector PIO, LBA, 4112MB, 8912 cyl, 15 head,
63 sec, 8421840 sectors
pciide0: channel 1 interrupting at irq 15
atapiscsi0 at pciide0 channel 1
scsibus0 at atapiscsi0: 2 targets
wdc_atapi_intr_drq: Unexpectedly in the command
phase. Please report this.
sd0 at scsibus0 targ 0 lun 0: <, , > SCSI0 0/direct
fixed
sd0: drive offline
sd0: can use 16-bit, PIO mode 0
isa0 at pcib0
isadma0 at isa0
sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01
midi0 at sb0: <SB MIDI UART>
audio0 at sb0
opl0 at sb0: model OPL3
midi1 at opl0: <SB Yamaha OPL3>
pcppi0 at isa0 port 0x61
midi2 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte
fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte
fifo
vt0 at isa0 port 0x60/16 irq 1: S3 765 (Trio64 V+),
80 col, color, 8 scr, mf2-kbd
pms0 at vt0 irq 12
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask c040 netmask c840 ttymask d842
pctr: 586-class performance counters and user-level
cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
sd0(pciide0:1:0): lost interrupt
type: atapi
c_bcount: 0
c_skip: 0
sd0(pciide0:1:0): lost interrupt
type: atapi
c_bcount: 0
c_skip: 0
sd0(pciide0:1:0): lost interrupt
type: atapi
c_bcount: 0
c_skip: 0
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
IP Filter: initialized. Default = pass all, Logging
= enabled

Any ideas about this problem? Is it all possibly a
result of the dead battery?

Any help appreciated,

Victor

Victor Richardson

unread,

Feb 23, 2000, 3:00:00 AM2/23/00

to

I'll give the snapshots a try this afternoon and let you know how it works.

Thanks,

Victor

Chris Cappuccio wrote:

> On Wed, 23 Feb 2000, Victor Richardson wrote:
>
> | of the battery possibly gone bad. Unfortunately, it
> | seems Compaq(Presario 9548) years ago thought it was
> | good to permanently attatch it to the motherboard.
> |
>

> Compaq probably left a separate plug on the board for an extra battery. But
> your best bet is probably to boot -c and disable apm

> Maybe there is something wrong in your rules?

> A lot in and around the pciide drivers has changed sinced 2.6. Can you try a
> snapshot from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/i386 ??
>
> ---
> Reverend Chris Cappuccio
> http://www.dqc.org/~chris/

Chris Cappuccio

unread,

Feb 23, 2000, 3:00:00 AM2/23/00

to

Victor Richardson

unread,

Feb 25, 2000, 3:00:00 AM2/25/00

to

Thanks for the APM advice, I don't think I could have figured that one out from
the man pages.

Chris Cappuccio wrote:

> On Wed, 23 Feb 2000, Victor Richardson wrote:
>
> | of the battery possibly gone bad. Unfortunately, it
> | seems Compaq(Presario 9548) years ago thought it was
> | good to permanently attatch it to the motherboard.
> |
>
> Compaq probably left a separate plug on the board for an extra battery. But
> your best bet is probably to boot -c and disable apm
>

I noticed that I have to execute the "boot -c" whenever the system is rebooted.
Is there a way I can make the "boot -c" part of the bios(or whatever it needs)? I
could imagine the furor that would be waiting for me if I wasn't in the office
and the system rebooted because of a power outgage or something.

>
>
> | When the system reboots everything goes smoothly
> | until after:
> |
> | Scsibus0 at atapiscsi:0: 2 targets
> | Wdc_atapi_intr_drq : Unexpectedly in the command
> | phase ; Please report this
> |
>
> A lot in and around the pciide drivers has changed sinced 2.6. Can you try a
> snapshot from ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/i386 ??

Unfortunately, my windows machine crashed right after I got your email and I lost
your follow up listing some of the directories or files that I would have to
modify after the upgrade. It took hours to transfer a small percentage of the
files to floppies(couldn't use zip), although most everything was lost when I
reformatted and re-installed Win95. I was only able to save 6 megs of data. When
will we learn?

Could you please resend those to me? Since I have no life, I'd like to upgrade
tonight and see how the current snapshots deal with pccide drivers.

Thanks,

Victor Richardson
"Free the mind, and your ass will follow."
George Clinton, Parliment/Funkadelic