[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Xorg 7 on sparc64

>>>>> "JS" == Jurij Smakov writes:

Hi Jurij,

 >> write(0, "(II) Loading /usr/lib/xorg/modul"..., 45) = 45
 >> open("/usr/lib/xorg/modules/libxaa.so", O_RDONLY) = 8
 >> read(8,
 >> (The last line is verbatim: X and `strace' hang right at this point.)

 > That looks bad. It hangs in the kernel. The corresponding piece
 > from my log looks like that:

 It is worse than that(*). Not only does the X server crash, the
 module file gets busted too, and I mean it gets corrupted on the
 disk, the file system appears to get along well, though (at least a
 full e2fsck does not barf). In my case that is usually `libramdac.so'
 that gets swept away, but I have seen `libxaa.so' get corrupted as
 well. The eye examination (after `file' and `nm') also confirms that
 the shared modules turn into a pile of crap.


(*) `uname -r' reports `2.6.17-rc3-sparc64', and the Xorg version is
7.0.22, any extra information available on demand.
 > So it looks like it just opens the module file (descriptor 8) and
 > reads the first 256 bytes of it. I have no clue why read could
 > block on a normal file like that. Do you have some weird
 > filesystem? I think we have verified that the file has the
 > correct md5sum before, so it's not corrupt... Can you Stop-A at
 > this point to get to the prom? If you can, the ctrace command
 > might give you stack trace which can be useful in debugging it.

 > Best regards,

 > Jurij Smakov                                        jurij@wooyd.org
 > Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

Reply to: