Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.os.386bsd.bugs
About this group
Subscribe to this group
This is a Usenet group - learn more
Protected Mode Lockup Problems--Please Help.
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   6 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Christopher L. Mikkelson  
View profile  
 More options Feb 6 1994, 5:53 pm
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: ae...@freenet.buffalo.edu (Christopher L. Mikkelson)
Date: 5 Feb 1994 22:04:36 -0600
Local: Sat, Feb 5 1994 11:04 pm
Subject: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author
Hello all!
  A friend of mine is having troubles with his machine.  Both Linux and
FreeBSD 1.0 will sporadically lock up his system.  Also, under DOS,
DJGPP will occasionally lock up and QEMM will often do a cold reboot.
I know it isn't a software problem, because it is shared by everything,
so it must be either hardware or firmware.  He is running a 386DX-40 with
AMI BIOS v 1.0.55a.

On boot, FreeBSD reports:

FreeBSD 1.0.2 (GENERICAH) #0: Sun Nov 14 18:22:24 PST 1993
  r...@gndrsh.cdrom.com:/usr/src/sys/compile/GENERICAH
CPU: i386DX (386-class CPU)
real mem  = 8384512
avail mem = 7000064
using 127 buffers containing 1044480 bytes of memory
Probing for devices on the ISA bus:
pc0 at 0x60-0x6f irq 1 on motherboard
pc0: type color
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type <16450>
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type <16450>
sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type <16550A>
sio3 not found at 0x2e8
lpt0 not found at 0x3bc
lpa0 at 0x378-0x37f on isa
lpa1 not found at 0x278
fd0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: unit 0 type 1.2MB 5.25in
fd0: unit 1 type 1.44MB 3.5in
wd0 not found at 0x1f0
ahb0 not found
aha0: reading board settings, dma=5 int=11
aha0 at 0x330 irq 11 drq 5 on isa
aha0 targ 0 lun 0: type 0(direct) fixed SCSI1
aha0 targ 0 lun 0: <FUJITSU M2624F-512      0404>
sd0: 496MB (1015812 total sec), 1429 cyl, 11 head, 64 sec, bytes/sec 512
wt0 not probed due to irq conflict with sio2 at 5
mcd0 not found at 0x300
ed0 not probed due to irq conflict with sio2 at 5
ed1 not probed due to irq conflict with sio2 at 5
ie0 not found at 0x360
is0 not found at 0x280
npx0 at 0xf0-0xff irq 13 on motherboard
biomask 840 ttymask 3a netmask 3a
changing root device to sd0a

A relatively detailed list of the BIOS settings follow:
--Basic CMOS Setup
640K Base Memory
7168K Extended Memory

--Advanced CMOS Setup
Typematic Rate Programming: Disabled
Typematic Rate Delay: 500
Typematic Rate: 15

Above 1MB memory test: Disabled
Cache: Enabled

Fast Gate A20 option: Enabled

Video ROM Shadow    C000,16K   :  Enabled
  "    "    "       C400,16K   :  Enabled
Adapter ROM Shadow  C800,16K   :  Disabled
   "     "    "     CC00,16K   :  Disabled
   "     "    "     D000,16K   :  Disabled
   "        "    "     D400,16K   :  Disabled
   "        "    "     D800,16K   :  Disabled
   "        "    "     DC00,16K   :  Disabled
   "        "    "     E000,16K   :  Disabled
   "        "    "     E400,16K   :  Disabled
   "        "    "     E800,16K   :  Disabled
   "        "    "     EC00,16K   :  Disabled
System ROM Shadow   F000,16K   :  Enabled

Boot Sector Virus Protection   :  Disabled

--Advanced Chipset Setup
Hidden Refresh:    Enabled
Keyboard Reset Control: Disabled
AT Cycle Wait State:    Disabled
Memory Read Wait State: 0 W/S
Memory Write Wait State:0 W/S
Cache Read Wait State:  2-1-1-1
Cache Write Wait State: 0 W/S
Non-Cacheable Block-1 Size: Disabled
Non-Cacheable Block-1 Base: 0 KB
Non-Cacheable Block-2 Size: Disabled
Non-Cacheable Block-2 Base: 0 KB
Cacheable RAM address range: 8M
Video BIOS Cacheable:    YES

Thanks in advance,
-Chris

--
------------------------------------------------------------
Christopher L. Mikkelson               ae...@freenet.buffalo.edu
Student, Menomonie High School         ap...@yfn.ysu.edu
        Desperately in search of a Non-Channel-One School...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Linus Torvalds  
View profile  
 More options Feb 8 1994, 5:11 am
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: torva...@klaava.Helsinki.FI (Linus Torvalds)
Date: 8 Feb 1994 12:11:29 +0200
Local: Tues, Feb 8 1994 5:11 am
Subject: Re: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author
In article <199402060404.XAA21...@freenet.buffalo.edu>,
Christopher L. Mikkelson <ae...@freenet.buffalo.edu> wrote:

>Hello all!
>  A friend of mine is having troubles with his machine.  Both Linux and
>FreeBSD 1.0 will sporadically lock up his system.  Also, under DOS,
>DJGPP will occasionally lock up and QEMM will often do a cold reboot.
>I know it isn't a software problem, because it is shared by everything,
>so it must be either hardware or firmware.  He is running a 386DX-40 with
>AMI BIOS v 1.0.55a.

Two things I have found that cause most of these kinds of lockups under
linux: either faulty memory or a bad i387.

The faulty memory is likely to result in various other problems first
(kernel panics due to corrupted data structures), but a bad i387 can
result in these silent deaths.  With linux, you can force the math
emulation code by giving the "no387" flag to LILO at bootup: if that
removes the problems you know what the culprit is.

Especially older clone 387's are suspect, and seem to lock up the bus
under some circumstances (the indications seem to be either (a) page
faults during coprocessor errors or (b) synchronization problems between
the i386 and i387, possibly due to math errors).

                Linus


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Eric S. Hvozda  
View profile  
 More options Feb 8 1994, 4:22 pm
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: a...@clark.net (Eric S. Hvozda)
Date: 8 Feb 1994 16:22:23 -0500
Local: Tues, Feb 8 1994 4:22 pm
Subject: Re: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author
In article <2j7ogh...@klaava.helsinki.fi>,

Linus Torvalds <torva...@klaava.Helsinki.FI> wrote:
>In article <199402060404.XAA21...@freenet.buffalo.edu>,
>Christopher L. Mikkelson <ae...@freenet.buffalo.edu> wrote:
>>Hello all!
>>  A friend of mine is having troubles with his machine.  Both Linux and
>>FreeBSD 1.0 will sporadically lock up his system.  Also, under DOS,
>>DJGPP will occasionally lock up and QEMM will often do a cold reboot.
>>I know it isn't a software problem, because it is shared by everything,
>>so it must be either hardware or firmware.  He is running a 386DX-40 with
>>AMI BIOS v 1.0.55a.

>Two things I have found that cause most of these kinds of lockups under
>linux: either faulty memory or a bad i387.

It's probably the i387.  There are a set of 4 conditions, if met, will lock
a i386 if a i387 is installed.  Basically the 386 ends up waiting on the 387
and vice versa.  The gory details are covered in "Repairing and Upgrading PCs"
written by Mueller and pubished by Que.

I will post the 4 conditions when I gte home from work...
--
Ack!
Creek, not creek; Pop not soda; Car needs washed...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Eric S. Hvozda  
View profile  
 More options Feb 8 1994, 11:47 pm
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: a...@clark.net (Eric S. Hvozda)
Date: 8 Feb 1994 23:47:47 -0500
Local: Tues, Feb 8 1994 11:47 pm
Subject: Re: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author
In article <2j8vqf$...@explorer.clark.net>,
Eric S. Hvozda <a...@clark.net> wrote:

>[..lock-ups with i386 with i387 installed..]

>It's probably the i387.  There are a set of 4 conditions, if met, will lock
>a i386 if a i387 is installed.  Basically the 386 ends up waiting on the 387
>and vice versa.  The gory details are covered in "Repairing and Upgrading PCs"
>written by Mueller and pubished by Que.

>I will post the 4 conditions when I gte home from work...

As promised, from the middle of page 428:

Demand page virtual memory must be active
A 387DX must be installed and in use
DMA must be in progress
The 386 must enter a wait state

Supposedly, if all of these conitions happen on the B stepping version of
the 386DX, the 386 and 387 endup waiting on eachother forever, hence the
lockup.  Intel published this problem as Errata 21.  Usually this problem
is only noticed when OS's like OS/2, Unix, etc are used.  I'm pressed to
imagine how DOS would tickel this nifty bugger...
--
Ack!
Creek, not creek; Pop not soda; Car needs washed...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Charles Hannum  
View profile  
 More options Feb 11 1994, 9:30 am
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: mycr...@duality.gnu.ai.mit.edu (Charles Hannum)
Date: 11 Feb 1994 14:30:59 GMT
Local: Fri, Feb 11 1994 9:30 am
Subject: Re: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author

I have an easier one:

Get a floating point error with IRQ 13 masked or IF turned off.

Boom, crack, sizzle, deadlock.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Christopher L. Mikkelson  
View profile  
 More options Feb 13 1994, 5:03 pm
Newsgroups: comp.os.386bsd.bugs, comp.os.386bsd.questions
From: ae...@freenet.buffalo.edu (Christopher L. Mikkelson)
Date: 13 Feb 1994 16:03:42 -0600
Local: Sun, Feb 13 1994 5:03 pm
Subject: Re: Protected Mode Lockup Problems--Please Help.
Print | Individual message | Show original | Report this message | Find messages by this author
  The freind of mine tried removing his coprocessor to see if that would help,
but it didn't.  The system still silently locked up.
  -Chris

--
------------------------------------------------------------
Christopher L. Mikkelson               ae...@freenet.buffalo.edu
Student, Menomonie High School         ap...@yfn.ysu.edu
        Desperately in search of a Non-Channel-One School...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google