testing -current on an SE/30

Hi

Has anyone else here attempted to boot a -current kernel on
an SE/30? 
How about on any other m68k Mac box?  

I tried booting a -current (4.99.4) kernel on an SE/30 the
other day, 
and it basically hangs at this line:
 
 scsibus0: waiting 2 seconds for devices to settle...

and I'm just wondering if others have seen this?  (I suspect
a 
timecounter issue...)

On a related note, I'm wondering how people can expect 4.0
and beyond 
to be good releases for mac68k if no-one is testing -current
:( 

Thanks.

Later...

Greg Oster

At 9:36 Uhr -0600 27.11.2006, Greg Oster wrote:
>Has anyone else here attempted to boot a -current kernel
on an SE/30?
>How about on any other m68k Mac box?

I've booted 4.99.[34] kernels on a Quadra 650, a IIsi and an
SE/30 during
the timecounter tests, and apart from the 'panic during
reboot' issue noted
in PR 35068, they generally worked fine.

>
>I tried booting a -current (4.99.4) kernel on an SE/30
the other day,
>and it basically hangs at this line:
>
> scsibus0: waiting 2 seconds for devices to settle...

If you used GENERIC, try GENERICSBC and vice versa. There
are known issues
for combinations of scsi devices and the two mac68k 53c80
drivers that have
never been resolved.

	hauke

--
"It's never straight up and down"     (DEVO)

Hauke Fath writes:
> At 9:36 Uhr -0600 27.11.2006, Greg Oster wrote:
> >Has anyone else here attempted to boot a -current
kernel on an SE/30?
> >How about on any other m68k Mac box?
> 
> I've booted 4.99.[34] kernels on a Quadra 650, a IIsi
and an SE/30 during
> the timecounter tests, and apart from the 'panic during
reboot' issue noted
> in PR 35068, they generally worked fine.
> 
> >
> >I tried booting a -current (4.99.4) kernel on an
SE/30 the other day,
> >and it basically hangs at this line:
> >
> > scsibus0: waiting 2 seconds for devices to
settle...
> 
> If you used GENERIC, try GENERICSBC and vice versa.
There are known issues
> for combinations of scsi devices and the two mac68k
53c80 drivers that have
> never been resolved.

Well.. wadda you know!  GENERICSBC worked!  I didn't bother
trying it 
cause I was running a GENERIC kernel on this machine
before...

"go figure"...

Thanks!

Later...

Greg Oster