Re: 5.99.30 sparc panic during startup

> > Should I do commit this patch? > > yes please! Committed. Thanks, --- Izumi Tsutsui

re: 5.99.30 sparc panic during startup

> At 1:03 Uhr +0900 26.6.2010, Izumi Tsutsui wrote: > >> The patch fixes the panic on my ss20 - an UP kernel makes it to multi-user, > >> and I can log in, and access the machine from the network. There's pppoe, > >> netatalk and samba breakage, but that may be due to version skew with the > >> ne

re: 5.99.30 sparc panic during startup

> > >> the macppc and news68k zshard()'s get the actual zsc_softc * as > > >> the (void *arg), but sparc does not. > > > > > >So we should make sparc zs do so. > > > > > >It looks multiple interrupt handlers against the same interrupt level > > >are properly queued and handled in sparc/intr.c:ih_i

Re: 5.99.30 sparc panic during startup

At 1:03 Uhr +0900 26.6.2010, Izumi Tsutsui wrote: >> The patch fixes the panic on my ss20 - an UP kernel makes it to multi-user, >> and I can log in, and access the machine from the network. There's pppoe, >> netatalk and samba breakage, but that may be due to version skew with the >> netbsd-4 user

Re: 5.99.30 sparc panic during startup

On Sat, Jun 26, 2010 at 01:03:17AM +0900, Izumi Tsutsui wrote: > > > the ss10/ss20 are the ones to test. > > Attached are dmesg.boot from my SS20. One with serial console, the > > other with local framebuffer console / wscons. I net-booted the machine > > to single user mode only. > > Should I do

Re: 5.99.30 sparc panic during startup

> >> the macppc and news68k zshard()'s get the actual zsc_softc * as > >> the (void *arg), but sparc does not. > > > >So we should make sparc zs do so. > > > >It looks multiple interrupt handlers against the same interrupt level > >are properly queued and handled in sparc/intr.c:ih_insert(), so > >

Re: 5.99.30 sparc panic during startup

On Sun, 20 Jun 2010 17:13:42 +1000 matthew green wrote: > the ss10/ss20 are the ones to test. Attached are dmesg.boot from my SS20. One with serial console, the other with local framebuffer console / wscons. I net-booted the machine to single user mode only. -- tschüß, Jochen Homepage

Re: 5.99.30 sparc panic during startup

At 11:14 Uhr +0900 20.6.2010, Izumi Tsutsui wrote: >> the macppc and news68k zshard()'s get the actual zsc_softc * as >> the (void *arg), but sparc does not. > >So we should make sparc zs do so. > >It looks multiple interrupt handlers against the same interrupt level >are properly queued and handle

re: 5.99.30 sparc panic during startup

> On Sun, 20 Jun 2010 12:38:18 +1000 > matthew green wrote: > > > it would still be nice to have a good multi-zs user test to make sure. > Would a Ultra2 or a SPARCstation 10 / 20 fit that bill? > I could throw a test kernel at that hardware easily. looks like sparc64 already uses a similar sch

Re: 5.99.30 sparc panic during startup

On Sun, 20 Jun 2010 12:38:18 +1000 matthew green wrote: > it would still be nice to have a good multi-zs user test to make sure. Would a Ultra2 or a SPARCstation 10 / 20 fit that bill? I could throw a test kernel at that hardware easily. -- tschüß, Jochen Homepage: http://www.unixag-kl

re: 5.99.30 sparc panic during startup

> > It looks multiple interrupt handlers against the same interrupt level > > are properly queued and handled in sparc/intr.c:ih_insert(), so > > no need to prepare own queue in zs.c. > > this patch must be tested on a system with both serial usage and > zskbd/zsms working, and if possible, on a

re: 5.99.30 sparc panic during startup

> It looks multiple interrupt handlers against the same interrupt level > are properly queued and handled in sparc/intr.c:ih_insert(), so > no need to prepare own queue in zs.c. this patch must be tested on a system with both serial usage and zskbd/zsms working, and if possible, on a system with

Re: 5.99.30 sparc panic during startup

> > > Somebody should fix the driver so that zshard() does not call > > > device_lookup_private(). It seems entirely unnecessary. > > > > There is a dumb hack in sun3 derived zs driver. > > > > All zs devices on sun machines have the same interrupt sources > > so ancient zs drivers tried to redu

re: 5.99.30 sparc panic during startup

> > Somebody should fix the driver so that zshard() does not call > > device_lookup_private(). It seems entirely unnecessary. > > There is a dumb hack in sun3 derived zs driver. > > All zs devices on sun machines have the same interrupt sources > so ancient zs drivers tried to reduce overhead o

Re: 5.99.30 sparc panic during startup

On Sun, Jun 20, 2010 at 04:43:07AM +0900, Izumi Tsutsui wrote: > > Somebody should fix the driver so that zshard() does not call > > device_lookup_private(). It seems entirely unnecessary. > > There is a dumb hack in sun3 derived zs driver. > > All zs devices on sun machines have the same interr

re: 5.99.30 sparc panic during startup

> Somebody should fix the driver so that zshard() does not call > device_lookup_private(). It seems entirely unnecessary. i don't see how without simply revert the change to convert to using device_lookup_private(). the interrupt comes in and you have to look at all of the zs devices on the sys

Re: 5.99.30 sparc panic during startup

> Somebody should fix the driver so that zshard() does not call > device_lookup_private(). It seems entirely unnecessary. There is a dumb hack in sun3 derived zs driver. All zs devices on sun machines have the same interrupt sources so ancient zs drivers tried to reduce overhead on interrupts by

Re: 5.99.30 sparc panic during startup

On Sat, Jun 19, 2010 at 06:28:48PM +0100, Mindaugas Rasiukevicius wrote: > David Young wrote: > > > <...> > > > config_alldevs_lock(0x0, 0x700, 0x0, 0x0, 0x0, 0xf416c660) at > > > netbsd:device_lookup+0x4 > > > device_lookup(0xf0335ebc, 0x0, 0x37f, 0xf0307208, 0x0, 0x0) at > > > netbsd:device_look

Re: 5.99.30 sparc panic during startup

David Young wrote: > > <...> > > config_alldevs_lock(0x0, 0x700, 0x0, 0x0, 0x0, 0xf416c660) at > > netbsd:device_lookup+0x4 > > device_lookup(0xf0335ebc, 0x0, 0x37f, 0xf0307208, 0x0, 0x0) at > > netbsd:device_lookup_private+0x8 > > device_lookup_private(0xf0335ebc, 0x0, 0x0, 0xf0307000, 0x

Re: 5.99.30 sparc panic during startup

On Sat, Jun 19, 2010 at 06:36:57PM +0200, Hauke Fath wrote: > Hi, > > Matthew Green sent me here with a -current issue on sparc which appears to > be something else than the ususal post-netbsd-4 SMP issues on the platform. > The full boot log is here >