On Thu, 30 Nov 2000, Russell Cattelan wrote:
> > but before IDE device probing (I think). Is this a known bug? Plain test11
> > works fine, and so does an earlier -XFS-test10 tree. I can provide
> > debugging output, if needed..
>
> Not as of yet.
>
> What else can you tell us.
Sorry, was late yesterday:
- gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
- K7V with VT82C686 controller + QUANTUM FIREBALLP KX13.6
- 128MB RAM
- Debian Woody (glibc 2.2)
- 10Gig XFS partition
Did a fresh checkout of current CVS last night, same results.
XFS-beta tree (test5 based) works fine. I tested the kernel on 2 different
K7V boxes and both hang at the same point (it seems).
> Can you break into kdb?
Tried compiling kdb in just now, getting some weird errors on some
perfectly legal looking defines ie
....
unsigned int bp_free:1; /* This entry is available */
....
/usr/src/XFS/linux-2.4-xfs/linux/include/linux/kdbprivate.h:91: parse
error before `:'
...etc...etc...
/usr/src/XFS/linux-2.4-xfs/linux/include/linux/kdbprivate.h:112: warning: array
`kdb_breakpoints' assumed to have one element
/usr/src/XFS/linux-2.4-xfs/linux/include/linux/dis-asm.h:148: storage size
of `display_endian' isn't known
> if so a back trace would be a good starting point.
Unfortunately I don't have time to fix the kdb compile today. Perhaps this
weekend. Any help appreciated..
Thanks,
-andy
--
AlsaPlayer, http://www.alsaplayer.org/
|