gbde atttach on sparc64 = kernel panic

[matt]

Thanks, works great now!

On a related note, the problem I had brought up weeks ago (gbde + ccd() +
md() = corruption) seems to have dissapeared.  The same torture tests that
were causing problems seem to be error-free now on sparc64 and x86 boxes,
and a couple trial runs with other files seems to look like it should now as
well.  In retrospect, given the traffic on the list regarding filesystem
corruption issues, that problem may not have even been related to gbde.
Hard to say I guess, but it's nice that it's working now.

-m

On Mon, 5 May 2003, Poul-Henning Kamp wrote:

> In message <20030504222506.L97149-100000 at grogged.dyndns.org>, matt writes:
> >
> >I've been playing with gbde on the latest sparc64 current (last saturday
> >anyhow), everytime I try and "gbde attach *devicename*" I get a kernel
> >panic - I'm trying to attach gbde to the md() device (which in turn is
> >pointed at a file on a ufs1 filesystem).  More details below:
> >
> >db> trace
> >panic() at panic+0x134
> >trap() at trap+0x324
> >-- memory address not aligned sfar=0xfffff80035cace51 sfsr=0x40029%o7=0xc014bd9c --
> >Decode() at Decode+0x34
> >MD5Update() at MD5Update+0x94
> >g_bde_decode_lock() at g_bde_decode_lock+0x320
>
> Fixed.
>
> MD5Update() assumed word aligned input, it should not.
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>