Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-23 Thread Andy Ruhl
On Tue, Oct 23, 2012 at 10:31 AM, SAITOH Masanobu wrote: > This problem was fixed by arm32/bus_space.c rev. 1.65 yesterday. And another > bus_space.c's bug was fixed today by Nick. Mine still panics, I hope it's not something I'm doing wrong: sd0: 7728 MB, 15744 cyl, 16 head, 63 sec, 512 bytes

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-23 Thread SAITOH Masanobu
Hello, Andy. (2012/10/21 11:07), Andy Ruhl wrote: > On Sat, Oct 20, 2012 at 3:39 PM, Andy Ruhl wrote: >> uhub0 at usb0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 >> Fatal kernel mode prefetch abort at 0xfb44 >> trapframe: 0xc8a2bbf0, spsr=6073 >> r0 =, r1 =,

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-20 Thread Andy Ruhl
On Sat, Oct 20, 2012 at 3:39 PM, Andy Ruhl wrote: > uhub0 at usb0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > Fatal kernel mode prefetch abort at 0xfb44 > trapframe: 0xc8a2bbf0, spsr=6073 > r0 =, r1 =, r2 =c8a32f3f, r3 =60d3 > r4 =c8a32f40, r5 =0020,

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-20 Thread Andy Ruhl
On Sat, Oct 20, 2012 at 2:54 PM, Andy Ruhl wrote: > On Sat, Oct 20, 2012 at 11:46 AM, matthew green wrote: >> what is the bt here? can you try a kernel with >> LOCKDEBUG option? this looks more like a usb >> issue than an arm issue. I added some other stuff with LOCKDEBUG and the bt changed:

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-20 Thread Andy Ruhl
On Sat, Oct 20, 2012 at 11:46 AM, matthew green wrote: > what is the bt here? can you try a kernel with > LOCKDEBUG option? this looks more like a usb > issue than an arm issue. Here is the bt, and I'll have LOCKDEBUG output shortly: db> bt netbsd:vpanic+0x10 scp=0xc01f8f58 rlv=0xc01f9

re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-20 Thread matthew green
> On Fri, Oct 19, 2012 at 3:05 PM, SAITOH Masanobu wrote: > > This problem was disappeard by arm/arm32/pmap.c rev. 1.240. > > My machine still panics: > > mvgbe at mvgbec1 port 0 not configured > mvpex at mvsoc0 unit 0 not configured > mvsata at mvsoc0 unit 0 not configured > mvsdio at mvsoc0

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-20 Thread Andy Ruhl
On Fri, Oct 19, 2012 at 3:05 PM, SAITOH Masanobu wrote: > This problem was disappeard by arm/arm32/pmap.c rev. 1.240. My machine still panics: mvgbe at mvgbec1 port 0 not configured mvpex at mvsoc0 unit 0 not configured mvsata at mvsoc0 unit 0 not configured mvsdio at mvsoc0 unit 0 not configur

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-10-19 Thread SAITOH Masanobu
(2012/09/28 1:57), SAITOH Masanobu wrote: > Hi. > > (2012/09/27 2:59), Andy Ruhl wrote: >> Hello all, >> >> I posted this on port-arm a few weeks ago and I have someone helping >> me look at it, but I figured I would post again. >> >> My Seagate Dockstar has a panic with -current. The last time I

Re: Panic at init on arm (Seagate Dockstar) with -current

2012-09-27 Thread SAITOH Masanobu
Hi. (2012/09/27 2:59), Andy Ruhl wrote: > Hello all, > > I posted this on port-arm a few weeks ago and I have someone helping > me look at it, but I figured I would post again. > > My Seagate Dockstar has a panic with -current. The last time I built a > good kernel was August 23rd. I noticed a

Panic at init on arm (Seagate Dockstar) with -current

2012-09-26 Thread Andy Ruhl
Hello all, I posted this on port-arm a few weeks ago and I have someone helping me look at it, but I figured I would post again. My Seagate Dockstar has a panic with -current. The last time I built a good kernel was August 23rd. I noticed a lot of changes since then. Here is what I see: cprng s