NetBSD Problem Report #23822

Received: (qmail 16012 invoked by uid 605); 21 Dec 2003 14:31:49 -0000
Message-Id: <Pine.SOL.4.58.0312211407040.28708@virgo.cus.cam.ac.uk>
Date: Sun, 21 Dec 2003 14:31:47 +0000 (GMT)
From: Ben Harris <bjh21@netbsd.org>
Sender: gnats-bugs-owner@NetBSD.org
To: gnats-bugs@gnats.netbsd.org
Subject: boot32 fails on my Risc PC

>Number:         23822
>Category:       port-acorn32
>Synopsis:       boot32 fails on my Risc PC
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-acorn32-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Dec 21 14:32:01 +0000 2003
>Closed-Date:    Sat Feb 20 16:17:11 +0000 2010
>Last-Modified:  Sat Feb 20 16:17:11 +0000 2010
>Originator:     Ben Harris
>Release:        2003-12-16
>Organization:
>Environment:
Risc PC 700, ARM610 CPU (also tested with SA-110), EtherB and EtherV
network cards, 32 MB DRAM + 2 MB VRAM, RISC OS 3.70.  Booting off NetFS.

>Description:
boot32 loads the kernel, but hangs after printing "bye bye from RISC OS!".
After a few minutes (less with the SA-110), it fills the screen with
garbage.

boot32 seems to work fine on my NC, by contrast.

>How-To-Repeat:
Using boot32 and netbsd-INSTALL.gz from the 2003-12-16 tgm build (the
latter renamed to nb32inst):

*i am :viking boot
*wimpslot -min 8192k
*boot32 nb32inst


>Fix:
Workaround is to use BtNetBSD, which still works.

>Release-Note:
>Audit-Trail:

From: Reinoud Zandijk <reinoud@netbsd.org>
To: gnats-bugs@gnats.netbsd.org
Cc:  
Subject: Re: port-acorn32/23822
Date: Mon, 23 Feb 2004 16:59:50 +0100

 Sorry for responding so late on this PR too but can you check if its still 
 valid?

 I am also most puzzled with what you wrote down as actual memory ranges 
 detected :

  Found ROM  (0) at 0x00000000 for  4096 k
  Found I/O  (0) at 0x03000000 for  8192 k
  Found I/O  (1) at 0x08000000 for 31072 k
  Found DRAM (0) at 0x10000000 for 16384 k
  Found DRAM (1) at 0x14000000 for 16384 k
  Found VRAM (0) at 0x02000000 for  2048 k


  Getting actual memorymapping ; sorting -


  Found physical memory blocks :
  [0x21f80000-0x21ffffff]  [0x1008c000-0x100dafff]  [0x100dd000-0x100e5fff]
  [0x100fe000-0x10133fff]  [0x101be000-0x108adfff]


 Notice that the first range route wrote down is outside any DRAM area. Are
 you sure it is/was stated that way? isnt it a typo? did you mean to type
 [0x021f8000-0x021fffff] ? i.e. a memory range within VRAM?

 Cheers,
 Reinoud

State-Changed-From-To: open->feedback 
State-Changed-By: reinoud 
State-Changed-When: Sat Aug 28 16:38:42 UTC 2004 
State-Changed-Why:  
In preparation of the 2-0 release, i would like to check if this is 
still a known problem. Could you please `cold-start' the machine and 
check if its also reporting this problem then? 

Cheers, 
Reinoud 
From: Reinoud Zandijk <reinoud@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-acorn32/23822
Date: Sat, 23 Sep 2006 21:13:29 +0200

 Could you please try out if its still the case? or has this been resolved? 
 As stated before, i'm pretty puzzled about :
   Found ROM  (0) at 0x00000000 for  4096 k
   Found I/O  (0) at 0x03000000 for  8192 k
   Found I/O  (1) at 0x08000000 for 31072 k
   Found DRAM (0) at 0x10000000 for 16384 k
   Found DRAM (1) at 0x14000000 for 16384 k
   Found VRAM (0) at 0x02000000 for  2048 k

   Getting actual memorymapping ; sorting -

   Found physical memory blocks :
   [0x21f80000-0x21ffffff]  [0x1008c000-0x100dafff]  [0x100dd000-0x100e5fff]
   [0x100fe000-0x10133fff]  [0x101be000-0x108adfff]

 0x21f80000 seems to be not right. The other addresses seem ok. This could 
 explain why other bootproblems are occuring. This `physical' addresses 
 displayed of course need to be in [0x10000000 - 0x11000000] or in 
 [0x14000000 - 0x15000000]

 With regards,
 Reinoud

State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 01 Sep 2008 02:41:00 +0000
State-Changed-Why:
Feedback timeout. Anyone else have this hardware?


From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: gnats-bugs@NetBSD.org
Cc: port-acorn32-maintainer@NetBSD.org, netbsd-bugs@NetBSD.org,
        gnats-admin@NetBSD.org, dholland@NetBSD.org, bjh21@NetBSD.org,
        tsutsui@ceres.dti.ne.jp
Subject: Re: port-acorn32/23822 (boot32 fails on my Risc PC)
Date: Mon, 1 Sep 2008 22:52:30 +0900

 dholland@NetBSD.org wrote:

 > Synopsis: boot32 fails on my Risc PC
  :
 > Feedback timeout. Anyone else have this hardware?

 I guess it has been fixed by this commit:
 http://mail-index.netbsd.org/source-changes/2008/02/03/msg001864.html
 ---
 Izumi Tsutsui

From: David Holland <dholland-bugs@netbsd.org>
To: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
Cc: gnats-bugs@NetBSD.org, port-acorn32-maintainer@NetBSD.org,
	netbsd-bugs@NetBSD.org, gnats-admin@NetBSD.org, dholland@NetBSD.org,
	bjh21@NetBSD.org
Subject: Re: port-acorn32/23822 (boot32 fails on my Risc PC)
Date: Mon, 1 Sep 2008 18:51:52 +0000

 On Mon, Sep 01, 2008 at 10:52:30PM +0900, Izumi Tsutsui wrote:
  > > Synopsis: boot32 fails on my Risc PC
  >  :
  > > Feedback timeout. Anyone else have this hardware?
  > 
  > I guess it has been fixed by this commit:
  > http://mail-index.netbsd.org/source-changes/2008/02/03/msg001864.html

 Great :-)  Can we close the PR then?

 -- 
 David A. Holland
 dholland@netbsd.org

From: Nick Hudson <nick.hudson@dsl.pipex.com>
To: gnats-bugs@netbsd.org
Cc: port-acorn32-maintainer@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org,
 Ben Harris <bjh21@netbsd.org>,
 chris@netbsd.org
Subject: Re: port-acorn32/23822 (boot32 fails on my Risc PC)
Date: Mon, 8 Sep 2008 08:14:18 +0100

 On Monday 01 September 2008 19:55:03 David Holland wrote:
 >  On Mon, Sep 01, 2008 at 10:52:30PM +0900, Izumi Tsutsui wrote:
 >   > > Synopsis: boot32 fails on my Risc PC
 >   > >
 >   > > Feedback timeout. Anyone else have this hardware?
 >   >
 >   > I guess it has been fixed by this commit:
 >   > http://mail-index.netbsd.org/source-changes/2008/02/03/msg001864.html
 >
 >  Great :-)  Can we close the PR then?

 Maybe request a pullup for netbsd-4?

 Chris will know... Chris?

 >
 >  --
 >  David A. Holland
 >  dholland@netbsd.org

 Nick

State-Changed-From-To: open->closed
State-Changed-By: hubertf@NetBSD.org
State-Changed-When: Sat, 20 Feb 2010 16:17:11 +0000
State-Changed-Why:
Feedback timeout.
If this still is a problem with a recent NetBSD version, please re-submit.

 - Hubert
 .


>Unformatted:
 >> NetBSD/acorn32 RISC OS Boot, Revision 3.20
 >> (cyber@tgm.netbsd.org, Tue Dec 16 13:00:23 UTC 2003)
 >> Booting NetBSD/acorn32 on a RiscPC/A7000/NC

 Booting nb32inst (howto = 0x0)
 Got 1926 memory pages each 4 kilobytes to mess with.

 Getting memory configuration

 Found ROM  (0) at 0x00000000 for  4096 k
 Found I/O  (0) at 0x03000000 for  8192 k
 Found I/O  (1) at 0x08000000 for 31072 k
 Found DRAM (0) at 0x10000000 for 16384 k
 Found DRAM (1) at 0x14000000 for 16384 k
 Found VRAM (0) at 0x02000000 for  2048 k

 Getting actual memorymapping ; sorting -

 Found physical memory blocks :
 [0x21f80000-0x21ffffff]  [0x1008c000-0x100dafff]  [0x100dd000-0x100e5fff]
 [0x100fe000-0x10133fff]  [0x101be000-0x108adfff]


 Loading nb32inst 3666544+186120=0x3acbb4

 Preparing for booting nb32inst ... shift and check ... OK!

 Starting at 0xf0000000
 Will boot in a few secs due to relocation....
 bye bye from RISC OS!

Home	PR Database Search