Re: HEADs up - gcc 4.1 reversion & MSCP CD changes in current

["Michael L. Hitch" <mhitch%lightning.msu.montana.edu@localhost>]

On Tue, 26 Jun 2012, Tom Ivar Helbekkmo wrote:

> David Brownlee <abs%absd.org@localhost> writes:
>
> > OK, so I've not introduced any new breakage with my racd changes, but
> > something is broken.
>
> Yeah, this has been like this for a couple of months at least.
...
> With a completely current kernel, things get reordered slightly after
> the Qbus is detected (I'm copying by hand, now, so I'm skipping the
> new version announcement, and the unchanged stuff):
>
> mtc0 at uba0 csr 174500 vec 774 ipl 17
> mscpbus0 at mtc0: version 4 model 14
> mscpbus0: DMA burst size set to 4
> uda0 at uba0 csr 172150 vec 770 ipl 17
> mscpbus1 at uda0: version 6 model 13
> mscpbus1: DMA burst size set to 4
> mt0 at mscpbus0 drive 0: TK70
> mt1 at mscpbus0 drive 0: TK70
> ra0 at mscpbus1 drive 0: RA90
> ra1 at mscpbus1 drive 0: RA90
>
> Notice how it's now not announcing any of the devices until after it's
> got both buses detected, while 5.1.1 showed them immediately after the
> bus had been detected, before going on to the next controller.

  I wonder if this might be due to the change in mscp.c that does the 
device configuration in a worker thread.  I see that there is a static 
structure involved during autoconf and previously the device configuration 
was run serially for each mscpbus.  Now it likely runs the device 
configuration on both mscpbus0 and mscpbus1 simultaneously and if that's 
trying to use that status structure, it's going to be somewhat confused.

Mike


--
Michael L. Hitch                        mhitch%montana.edu@localhost
Computer Consultant
Information Technology Center
Montana State University        Bozeman, MT     USA