BBB keeps rebooting

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

BBB keeps rebooting

Jan Stary
I just reinstalled a beaglebone black with the latest snapshot.
The upgrade went fine, but after the reboot, the new /bsd keeps
rebooting over and over again. It just says

  booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4

then nothing for a few seconds, then it reboots anew.
Is anyone seeign the same?

        Jan

Reply | Threaded
Open this post in threaded view
|

Re: BBB keeps rebooting

Fred
On 09/21/17 15:44, Jan Stary wrote:

> I just reinstalled a beaglebone black with the latest snapshot.
> The upgrade went fine, but after the reboot, the new /bsd keeps
> rebooting over and over again. It just says
>
>    booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4
>
> then nothing for a few seconds, then it reboots anew.
> Is anyone seeign the same?
>
> Jan
>

doesn't sd0 hold the linux install? On my bbb sd1 hold the OpenBSD
partition and you have to hold one of the buttons on board for first
boot (I'm remote from my bbb atm so cannot remember which button needs
to held down on first boot)

eg:

sd0 at scsibus0 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct
removable
sd0: 1832MB, 512 bytes/sector, 3751936 sectors
scsibus1 at sdmmc0: 2 targets, initiator 0
sd1 at scsibus1 targ 1 lun 0: <SD/MMC, SU08G, 0080> SCSI2 0/direct removable
sd1: 7580MB, 512 bytes/sector, 15523840 sectors
boot device: sd0
root on sd1a (df088aa460d72037.a) swap on sd1b dump on sd1b

my build is a couple of weeks old:
OpenBSD 6.2-beta (GENERIC) #59: Wed Sep  6 03:25:28 MDT 2017

     [hidden email]:/usr/src/sys/arch/armv7/compile/GENERIC


hth

Fred

Reply | Threaded
Open this post in threaded view
|

Re: BBB keeps rebooting

Jan Stary
On Sep 21 15:58:04, [hidden email] wrote:

> On 09/21/17 15:44, Jan Stary wrote:
> > I just reinstalled a beaglebone black with the latest snapshot.
> > The upgrade went fine, but after the reboot, the new /bsd keeps
> > rebooting over and over again. It just says
> >
> >    booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4
> >
> > then nothing for a few seconds, then it reboots anew.
> > Is anyone seeign the same?
> >
> > Jan
> >
>
> doesn't sd0 hold the linux install?

No. On my system, sd0 is the 32GBGB card I put in it;
and obsd boots just fine.

        Jan

> On my bbb sd1 hold the OpenBSD partition
> and you have to hold one of the buttons on board for first boot (I'm remote
> from my bbb atm so cannot remember which button needs to held down on first
> boot)
>
> eg:
>
> sd0 at scsibus0 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct
> removable
> sd0: 1832MB, 512 bytes/sector, 3751936 sectors
> scsibus1 at sdmmc0: 2 targets, initiator 0
> sd1 at scsibus1 targ 1 lun 0: <SD/MMC, SU08G, 0080> SCSI2 0/direct removable
> sd1: 7580MB, 512 bytes/sector, 15523840 sectors
> boot device: sd0
> root on sd1a (df088aa460d72037.a) swap on sd1b dump on sd1b
>
> my build is a couple of weeks old:
> OpenBSD 6.2-beta (GENERIC) #59: Wed Sep  6 03:25:28 MDT 2017
>
>     [hidden email]:/usr/src/sys/arch/armv7/compile/GENERIC
>
>
> hth
>
> Fred
>

Reply | Threaded
Open this post in threaded view
|

Re: BBB keeps rebooting

Jonathan Gray-11
In reply to this post by Jan Stary
On Thu, Sep 21, 2017 at 04:44:32PM +0200, Jan Stary wrote:

> I just reinstalled a beaglebone black with the latest snapshot.
> The upgrade went fine, but after the reboot, the new /bsd keeps
> rebooting over and over again. It just says
>
>   booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4
>
> then nothing for a few seconds, then it reboots anew.
> Is anyone seeign the same?
>
> Jan
>

Both a snapshot kernel and a locally built one boot fine with root on sd
card here.

>> OpenBSD/armv7 BOOTARM 0.9
boot>
booting sd0a:/bsd: 3921740+165128+561472 [282178+90+520048+244541]=0x57115c

OpenBSD/armv7 booting ...
arg0 0xc087115c arg1 0xe05 arg2 0x88000000
Allocating page tables
freestart = 0x80872000, free_pages = 128910 (0x0001f78e)
IRQ stack: p0x808a0000 v0xc08a0000
ABT stack: p0x808a1000 v0xc08a1000
UND stack: p0x808a2000 v0xc08a2000
SVC stack: p0x808a3000 v0xc08a3000
Creating L1 page table at 0x80874000
Mapping kernel
Constructing L2 page tables
undefined page pmap [ using 1047316 bytes of bsd ELF symbol table ]
board type: 3589
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2017 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.2-beta (GENERIC) #76: Tue Sep 19 04:30:34 MDT 2017
    [hidden email]:/usr/src/sys/arch/armv7/compile/GENERIC
real mem  = 536870912 (512MB)
avail mem = 517292032 (493MB)
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0: ARM Cortex-A8 r3p2 (ARMv7)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0
...

>> OpenBSD/armv7 BOOTARM 0.9
boot>
booting sd0a:/bsd: 3933596+165624+561144 [282400+90+521200+244991]=0x579920

OpenBSD/armv7 booting ...
arg0 0xc0879920 arg1 0xe05 arg2 0x88000000
Allocating page tables
freestart = 0x8087a000, free_pages = 128902 (0x0001f786)
IRQ stack: p0x808a8000 v0xc08a8000
ABT stack: p0x808a9000 v0xc08a9000
UND stack: p0x808aa000 v0xc08aa000
SVC stack: p0x808ab000 v0xc08ab000
Creating L1 page table at 0x8087c000
Mapping kernel
Constructing L2 page tables
undefined page pmap [ using 1049136 bytes of bsd ELF symbol table ]
board type: 3589
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2017 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.2-beta (GENERIC) #2: Fri Sep 22 13:32:05 AEST 2017
    [hidden email]:/usr/src/sys/arch/armv7/compile/GENERIC
real mem  = 536870912 (512MB)
avail mem = 517259264 (493MB)
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0: ARM Cortex-A8 r3p2 (ARMv7)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0
...

Reply | Threaded
Open this post in threaded view
|

Re: BBB keeps rebooting

Jan Stary
In reply to this post by Jan Stary
On Sep 21 17:46:33, [hidden email] wrote:

> On Sep 21 15:58:04, [hidden email] wrote:
> > On 09/21/17 15:44, Jan Stary wrote:
> > > I just reinstalled a beaglebone black with the latest snapshot.
> > > The upgrade went fine, but after the reboot, the new /bsd keeps
> > > rebooting over and over again. It just says
> > >
> > >    booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4
> > >
> > > then nothing for a few seconds, then it reboots anew.
> > > Is anyone seeign the same?
> > >
> > > Jan
> > >
> >
> > doesn't sd0 hold the linux install?
>
> No. On my system, sd0 is the 32GBGB card I put in it;

Ah, that's how the _installer_ saw it.
But the booted obsd thinks it's sd1, since Sep 19.
These are the last two working dmesgs:

http://stare.cz/dmesg/beaglebone-black.20170709
http://stare.cz/dmesg/beaglebone-black.20170919

Running diff on them:

--- dmesg/beaglebone-black.20170709 Sun Jul  9 17:11:21 2017
+++ dmesg/beaglebone-black.20170919 Fri Sep 22 09:17:14 2017
[...]
-scsibus0 at sdmmc0: 2 targets, initiator 0
-sd0 at scsibus0 targ 1 lun 0: <SD/MMC, SU32G, 0080> SCSI2 0/direct removable
-sd0: 30436MB, 512 bytes/sector, 62333952 sectors
-scsibus1 at sdmmc1: 2 targets, initiator 0
-sd1 at scsibus1 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct removable
-sd1: 1832MB, 512 bytes/sector, 3751936 sectors
+amdisplay0 at simplebus0
+amdisplay0: no display attached.
+scsibus0 at sdmmc1: 2 targets, initiator 0
+sd0 at scsibus0 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct removable
+sd0: 1832MB, 512 bytes/sector, 3751936 sectors
+scsibus1 at sdmmc0: 2 targets, initiator 0
+sd1 at scsibus1 targ 1 lun 0: <SD/MMC, SU32G, 0080> SCSI2 0/direct removable
+sd1: 30436MB, 512 bytes/sector, 62333952 sectors
 vscsi0 at root
 scsibus2 at vscsi0: 256 targets
 softraid0 at root
 scsibus3 at softraid0: 256 targets
 boot device: sd0
-root on sd0a (93aae518915c8841.a) swap on sd0b dump on sd0b
+root on sd1a (93aae518915c8841.a) swap on sd1b dump on sd1b
 WARNING: CHECK AND RESET THE DATE!


So it seems the sd0 and sd1 are detected the other way round now.
I haven't swapped them, they are the same for years.

I will keep the /obsd as /bsd.good and try to build another /bsd

        Jan

Reply | Threaded
Open this post in threaded view
|

Re: BBB keeps rebooting

Jan Stary
On Sep 22 09:23:02, [hidden email] wrote:

> On Sep 21 17:46:33, [hidden email] wrote:
> > On Sep 21 15:58:04, [hidden email] wrote:
> > > On 09/21/17 15:44, Jan Stary wrote:
> > > > I just reinstalled a beaglebone black with the latest snapshot.
> > > > The upgrade went fine, but after the reboot, the new /bsd keeps
> > > > rebooting over and over again. It just says
> > > >
> > > >    booting sd0a:/bsd: 3919680+167292+561628 [281802+90+520048+244541]=0x5718f4
> > > >
> > > > then nothing for a few seconds, then it reboots anew.
> > > > Is anyone seeign the same?
> > > >
> > > > Jan
> > > >
> > >
> > > doesn't sd0 hold the linux install?
> >
> > No. On my system, sd0 is the 32GBGB card I put in it;
>
> Ah, that's how the _installer_ saw it.
> But the booted obsd thinks it's sd1, since Sep 19.
> These are the last two working dmesgs:
>
> http://stare.cz/dmesg/beaglebone-black.20170709
> http://stare.cz/dmesg/beaglebone-black.20170919
>
> Running diff on them:
>
> --- dmesg/beaglebone-black.20170709 Sun Jul  9 17:11:21 2017
> +++ dmesg/beaglebone-black.20170919 Fri Sep 22 09:17:14 2017
> [...]
> -scsibus0 at sdmmc0: 2 targets, initiator 0
> -sd0 at scsibus0 targ 1 lun 0: <SD/MMC, SU32G, 0080> SCSI2 0/direct removable
> -sd0: 30436MB, 512 bytes/sector, 62333952 sectors
> -scsibus1 at sdmmc1: 2 targets, initiator 0
> -sd1 at scsibus1 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct removable
> -sd1: 1832MB, 512 bytes/sector, 3751936 sectors
> +amdisplay0 at simplebus0
> +amdisplay0: no display attached.
> +scsibus0 at sdmmc1: 2 targets, initiator 0
> +sd0 at scsibus0 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct removable
> +sd0: 1832MB, 512 bytes/sector, 3751936 sectors
> +scsibus1 at sdmmc0: 2 targets, initiator 0
> +sd1 at scsibus1 targ 1 lun 0: <SD/MMC, SU32G, 0080> SCSI2 0/direct removable
> +sd1: 30436MB, 512 bytes/sector, 62333952 sectors
>  vscsi0 at root
>  scsibus2 at vscsi0: 256 targets
>  softraid0 at root
>  scsibus3 at softraid0: 256 targets
>  boot device: sd0
> -root on sd0a (93aae518915c8841.a) swap on sd0b dump on sd0b
> +root on sd1a (93aae518915c8841.a) swap on sd1b dump on sd1b
>  WARNING: CHECK AND RESET THE DATE!
>
>
> So it seems the sd0 and sd1 are detected the other way round now.
> I haven't swapped them, they are the same for years.
>
> I will keep the /obsd as /bsd.good and try to build another /bsd

... and it boots just fine, from sd0 again (dmesg below).
I don't know why it detected the disks the other way round before.

        Jan


OpenBSD 6.2-beta (GENERIC) #0: Fri Sep 22 10:04:20 CEST 2017
    [hidden email]:/usr/src/sys/arch/armv7/compile/GENERIC
real mem  = 536870912 (512MB)
avail mem = 517255168 (493MB)
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0: ARM Cortex-A8 r3p2 (ARMv7)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0
prcm0 at omap0 rev 0.2
dmtimer0 at omap0 rev 3.1
dmtimer1 at omap0 rev 3.1
simplebus0 at mainbus0: "ocp"
simplebus1 at simplebus0: "l4_wkup"
simplebus2 at simplebus1: "scm"
ompinmux0 at simplebus2
simplebus3 at simplebus2: "scm_conf"
intc0 at simplebus0 rev 5.0
omgpio0 at simplebus0: rev 0.1
gpio0 at omgpio0: 32 pins
omgpio1 at simplebus0: rev 0.1
gpio1 at omgpio1: 32 pins
omgpio2 at simplebus0: rev 0.1
gpio2 at omgpio2: 32 pins
omgpio3 at simplebus0: rev 0.1
gpio3 at omgpio3: 32 pins
com0 at simplebus0: ti16750, 64 byte fifo
com0: console
tiiic0 at simplebus0 rev 0.11
iic0 at tiiic0
"ti,tps65217" at iic0 addr 0x24 not configured
"atmel,24c256" at iic0 addr 0x50 not configured
nxphdmi0 at iic0 addr 0x70: rev 0x0301
nxphdmi0: no display detected
tiiic1 at simplebus0 rev 0.11
iic1 at tiiic1
"atmel,24c256" at iic1 addr 0x54 not configured
"atmel,24c256" at iic1 addr 0x55 not configured
"atmel,24c256" at iic1 addr 0x56 not configured
"atmel,24c256" at iic1 addr 0x57 not configured
ommmc0 at simplebus0
sdmmc0 at ommmc0: 4-bit, sd high-speed, mmc high-speed
ommmc1 at simplebus0
sdmmc1 at ommmc1: 1-bit
omdog0 at simplebus0 rev 0.1
cpsw0 at simplebus0: version 1.12 (0), address 90:59:af:82:2e:7e
ukphy0 at cpsw0 phy 0: Generic IEEE 802.3u media interface, rev. 1: OUI 0x0001f0, model 0x000f
amdisplay0 at simplebus0
amdisplay0: no display attached.
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, SU32G, 0080> SCSI2 0/direct removable
sd0: 30436MB, 512 bytes/sector, 62333952 sectors
scsibus1 at sdmmc1: 2 targets, initiator 0
sd1 at scsibus1 targ 1 lun 0: <SD/MMC, MMC02G, 0000> SCSI2 0/direct removable
sd1: 1832MB, 512 bytes/sector, 3751936 sectors
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
boot device: sd0
root on sd0a (93aae518915c8841.a) swap on sd0b dump on sd0b
WARNING: CHECK AND RESET THE DATE!