HEADS UP [Re: Insta-panic with recent -current on Ultra10]

Ken Smith kensmith at cse.Buffalo.EDU
Fri Aug 27 06:01:41 PDT 2004

On Fri, Aug 27, 2004 at 07:15:51PM +0900, Pyun YongHyeon wrote:
> On Fri, Aug 27, 2004 at 06:03:02PM +1000, Chris Knight wrote:
>  > Howdy,
>  > 
>  > I'm still getting this panic on sources updated just before
>  > you tagged newvers.sh for BETA2.
>  > 
>  > ad0: 8693MB <ST39140A/861000> [17662/16/63] at ata2-master WDMA2
>                                                               ^^^^^
> Since you still use DMA on ad device, I'm afraid your kernel is not
> updated with latest loader.
> (src/sys/boot/sparc64/loader/main.c, rev 1.24 or
> Please re-cvsup and try again.

This is most likely the problem but it might not be a re-cvsup problem.
If you are following The Right Way To Update (which virtually none of
us do... :-) then you're installing the new kernel and rebooting before
running installworld.  It's installworld that takes care of installing
the new loader, which has hardcoded in it something that turns off ata

You can get around this by stopping the loader before it boots the
kernel (where it's typically counting down from 10), and do this:

	set hw.ata.ata_dma=0

That will let the new kernel boot.  And then you can go ahead with the
installworld.  The current version of the loader will be installed then,
and this step shouldn't be necessary any more.

Scott was able to locate the problem that makes this necessary yesterday.
It turned out to be something in the new ATA code after all and not what
he had originally thought.  He sent the report of what's happening
to Soeren, but it definitely won't be fixed by BETA2 which is building

						Ken Smith
- From there to here, from here to      |       kensmith at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |

More information about the freebsd-sparc64 mailing list