[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC

To: "Kenneth R Westerback" <kwesterback@rogers.com>
Subject: Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC
From: "Fender Q" <fenderq@buzztone.cc>
Date: Sun, 17 Mar 2002 17:33:26 -0800
Cc: <misc@openbsd.org>
Organization: Buzztone.cc
References: <002101c1ccf7$5e8d6e00$6401a8c0@buzztone.cc> <20020316234936.D5991@screaminet.com> <000701c1cd76$130c6920$6401a8c0@buzztone.cc> <20020317125012.GH17878@pinky.westerback.to>

I just finished trying the floppy30.fs image from
ftp://ftp.ca.openbsd.org/pub/OpenBSD/snapshots/i386
The March 6, 2002 Snapshot I guess.

This time it gets to:

aha0 at isa0 port 0x330/4 irq 11 drq 5: model AHA-1540A/1542A/1542B,
firmware 0.5
aha0: async, parity
fatal page fault in supervisor mode
trap type 6 code 0 eip e020a455 cs 8 eflags 10283 cr2 364 cpl 0
panic: trap type 6, code=0, pc=e020a455

And then the please reboot with any key message.

I wonder if the OpenBSD kernel can handle the 386 popad bug?
I noticed that my Linux kernel was detecting this as buggy.

Here is the output from my known working Linux kernel dmesg:

Mar 16 06:44:13 vulcan kernel: Linux version 2.2.19-6.2.15
(root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release)) #1 Wed Feb 27 11:05:02 EST 2002
Mar 16 06:44:13 vulcan kernel: BIOS-provided physical RAM map:
Mar 16 06:44:13 vulcan kernel:  BIOS-88: 000a0000 @ 00000000 (usable)
Mar 16 06:44:13 vulcan kernel:  BIOS-88: 01300000 @ 00100000 (usable)
Mar 16 06:44:13 vulcan kernel: Console: colour VGA+ 80x25
Mar 16 06:44:13 vulcan kernel: Calibrating delay loop... 7.75 BogoMIPS
Mar 16 06:44:13 vulcan kernel: Memory: 17824k/20480k available (1140k kernel
code, 408k reserved, 652k data, 72k init, 0k bigmem)
Mar 16 06:44:13 vulcan kernel: Checking if this processor honours the WP bit
even in supervisor mode... No.
Mar 16 06:44:13 vulcan kernel: Dentry hash table entries: 4096 (order 3,
32k)
Mar 16 06:44:13 vulcan kernel: Buffer cache hash table entries: 32768 (order
5, 128k)
Mar 16 06:44:13 vulcan kernel: Page cache hash table entries: 8192 (order 3,
32k)
Mar 16 06:44:13 vulcan kernel: VFS: Diskquotas version dquot_6.4.0
initialized
Mar 16 06:44:13 vulcan kernel: CPU: 386
Mar 16 06:44:13 vulcan kernel: Checking 'hlt' instruction... OK.
Mar 16 06:44:13 vulcan kernel: Checking for popad bug... Buggy.
Mar 16 06:44:13 vulcan kernel: POSIX conformance testing by UNIFIX
Mar 16 06:44:13 vulcan kernel: PCI: No PCI bus detected
Mar 16 06:44:13 vulcan kernel: Linux NET4.0 for Linux 2.2
Mar 16 06:44:13 vulcan kernel: Based upon Swansea University Computer
Society NET3.039
Mar 16 06:44:13 vulcan kernel: NET4: Unix domain sockets 1.0 for Linux
NET4.0.
Mar 16 06:44:13 vulcan kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Mar 16 06:44:13 vulcan kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Mar 16 06:44:13 vulcan kernel: TCP: Hash tables configured (ehash 32768
bhash 32768)
Mar 16 06:44:13 vulcan kernel: IPVS: Connection hash table configured
(size=4096, memory=32Kbytes)
Mar 16 06:44:13 vulcan kernel: Linux IP multicast router 0.06 plus PIM-SM
Mar 16 06:44:13 vulcan kernel: Initializing RT netlink socket
Mar 16 06:44:13 vulcan kernel: Starting kswapd v 1.5
Mar 16 06:44:13 vulcan kernel: Serial driver version 4.27 with MANY_PORTS
MULTIPORT SHARE_IRQ enabled
Mar 16 06:44:14 vulcan kernel: ttyS00 at 0x03f8 (irq = 4) is a 16450
Mar 16 06:44:14 vulcan kernel: ttyS01 at 0x02f8 (irq = 3) is a 16450
Mar 16 06:44:14 vulcan kernel: pty: 256 Unix98 ptys configured
Mar 16 06:44:14 vulcan kernel: Real Time Clock Driver v1.09
Mar 16 06:44:14 vulcan kernel: RAM disk driver initialized:  16 RAM disks of
4096K size
Mar 16 06:44:14 vulcan kernel: Floppy drive(s): fd0 is 1.44M
Mar 16 06:44:14 vulcan kernel: FDC 0 is an 8272A
Mar 16 06:44:14 vulcan kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
Mar 16 06:44:14 vulcan kernel: raid5: measuring checksumming speed
Mar 16 06:44:14 vulcan kernel:    8regs     :     4.191 MB/sec
Mar 16 06:44:14 vulcan kernel:    32regs    :     2.286 MB/sec
Mar 16 06:44:14 vulcan kernel: using fastest function: 8regs (4.191 MB/sec)
Mar 16 06:44:14 vulcan kernel: scsi : 0 hosts.
Mar 16 06:44:14 vulcan kernel: scsi : detected total.
Mar 16 06:44:14 vulcan kernel: md.c: sizeof(mdp_super_t) = 4096
Mar 16 06:44:14 vulcan kernel: Partition check:
Mar 16 06:44:14 vulcan kernel: RAMDISK: Compressed image found at block 0
Mar 16 06:44:14 vulcan kernel: autodetecting RAID arrays
Mar 16 06:44:14 vulcan kernel: autorun ...
Mar 16 06:44:14 vulcan kernel: ... autorun DONE.
Mar 16 06:44:14 vulcan kernel: apm: BIOS not found.
Mar 16 06:44:14 vulcan kernel: VFS: Mounted root (ext2 filesystem).
Mar 16 06:44:14 vulcan kernel: Configuring Adaptec (SCSI-ID 7) at IO:330,
IRQ 11, DMA priority 5
Mar 16 06:44:14 vulcan kernel: scsi0 : Adaptec 1542
Mar 16 06:44:14 vulcan kernel: scsi : 1 host.
Mar 16 06:44:14 vulcan kernel:   Vendor: QUANTUM   Model: PD1225S
Rev: 3110
Mar 16 06:44:15 vulcan kernel:   Type:   Direct-Access
ANSI SCSI revision: 02
Mar 16 06:44:15 vulcan kernel: Detected scsi disk sda at scsi0, channel 0,
id 0, lun 0
Mar 16 06:44:15 vulcan kernel:   Vendor: TOSHIBA   Model: CD-ROM XM-3401TA
Rev: 0283
Mar 16 06:44:15 vulcan kernel:   Type:   CD-ROM
ANSI SCSI revision: 02
Mar 16 06:44:15 vulcan kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0,
id 1, lun 0
Mar 16 06:44:15 vulcan kernel: Uniform CD-ROM driver Revision: 3.11
Mar 16 06:44:15 vulcan kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 2395980 [1169 MB] [1.2 GB]
Mar 16 06:44:15 vulcan kernel:  sda: sda1 sda2 < sda5 sda6 >
Mar 16 06:44:15 vulcan kernel: autodetecting RAID arrays
Mar 16 06:44:15 vulcan kernel: autorun ...
Mar 16 06:44:15 vulcan kernel: ... autorun DONE.
Mar 16 06:44:15 vulcan kernel: VFS: Mounted root (ext2 filesystem) readonly.
Mar 16 06:44:15 vulcan kernel: change_root: old root has d_count=1
Mar 16 06:44:15 vulcan kernel: Trying to unmount old root ... okay
Mar 16 06:44:15 vulcan kernel: Freeing unused kernel memory: 72k freed
Mar 16 06:44:15 vulcan kernel: Adding Swap: 131048k swap-space (priority -1)
Mar 16 06:44:15 vulcan kernel: eth0: 3c509 at 0x300 tag 1, 10baseT port,
address  00 20 af ec 0b 2b, IRQ 10.
Mar 16 06:44:15 vulcan kernel: 3c509.c:1.16 (2.2) 2/3/98
becker@cesdis.gsfc.nasa.gov.
Mar 16 06:44:15 vulcan kernel: eth1: 3c509 at 0x340 tag 2, 10baseT port,
address  00 a0 24 2e d0 8a, IRQ 7.
Mar 16 06:44:15 vulcan kernel: 3c509.c:1.16 (2.2) 2/3/98
becker@cesdis.gsfc.nasa.gov.
Mar 16 06:44:16 vulcan kernel: ne.c:v1.10 9/23/94 Donald Becker
(becker@cesdis.gsfc.nasa.gov)
Mar 16 06:44:16 vulcan kernel: NE*000 ethercard probe at 0x220: 52 54 40 20
ef 11
Mar 16 06:44:16 vulcan kernel: eth2: NE2000 found at 0x220, using IRQ 5.

I also have been searching the change logs for matches on uvm_fault but
nothing related to what I get.

Thanks for the idea Ken....

----- Original Message -----
From: "Kenneth R Westerback" <kwesterback@rogers.com>
To: "Fender Q" <fenderq@buzztone.cc>
Sent: Sunday, March 17, 2002 4:50 AM
Subject: Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC


> You might try an i386 snapshot floppy from, e.g.,
>
> ftp://ftp.ca.openbsd.org/pub/OpenBSD/snapshots/i386
>
> and see if the many fixes from 3.0 to 3.1 have addressed your
> problem.
>
> .... Ken
>
> On Sat, Mar 16, 2002 at 09:39:13PM -0800, Fender Q wrote:
> > Other machines which I have used the floppy30.fs image disk on are a
486DX66
> > and a AMD K6-233Mhz one, and actually another PIII-500Mhz system worked
fine
> > too.  Thus, meaning my disks are valid and working ok.
> >
> > uvm_fault, I was looking at the man page on "uvm" it was interesting
> > reading, I wish I could see the message better, so I could maybe guess
the
> > return address of that fault.  Also, last night since that uvm_fault
could
> > be memory related, I ran a ramexam program that ran for 2 hours on the
> > memory of my system, and didn't have one problem, also the system
presently
> > is running Linux and is stable as a rock, so I doubt there is any
hardware
> > related issue.
> >
> > I wonder if the kernel used for the floppy30.fs image has 386 support
turned
> > on?  I should check in the src/distribution section to see....
> >
> > Should this be a sendbug item?  I'm new to OpenBSD so and still trying
to
> > figure out what to post & where and such.  Thanks for the response
Peter.
> >
> > ----- Original Message -----
> > From: "Peter Varga" <peter.varga@screaminet.com>
> > To: "Fender Q" <fenderq@buzztone.cc>
> > Sent: Saturday, March 16, 2002 8:49 PM
> > Subject: Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC
> >
> >
> > > On Sat, Mar 16, 2002 at 06:32:13AM -0800, Fender Q wrote:
> > > > Everytime I try and boot from the install disk I get a uvm_fault
right
> > after
> > > > the line rootdev.  This makes the system reboot fast, and it is hard
to
> > see
> > > > all of what the message says.
> > > >
> > > > I have tried both the floppy30.fs and floppyB30.fs image and still
get
> > the
> > > > same results.  I have had success with these disks on two other
machines
> > > > with no problems.
> > >
> > > Are the machines 386 as well?
> > >
> > > >
> > > > The system in question is a 386DX25 with three network cards, two
3c509
> > (ep)
> > > > and one ne2000 (ne).  It has a SCSI AHA1542 controller card (aha)
and a
> > > > 1.2GB hard drive, and a SCSI CD-ROM drive.  The system only has 20MB
of
> > > > memory.  The system is presently running Red Hat Linux 6.2 and there
are
> > no
> > > > hardware conflicts.
> > > >
> > > > Any ideas would be great, thanks for your time.

References:
- uvm_fault and reboot on install of OpenBSD 3.0 GENERIC
  - From: "Fender Q" <fenderq@buzztone.cc>
- Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC
  - From: "Fender Q" <fenderq@buzztone.cc>

Prev by Date: Re: mounting a netbios share in openbsd...
Next by Date: Re: "reply directly, I'm not subscribed"
Prev by thread: Re: uvm_fault and reboot on install of OpenBSD 3.0 GENERIC
Next by thread: Logitech QuickCam Express
Index(es):
- Date
- Thread