On 11/29/05, Andrew Morton <[email protected]> wrote:
> Tarkan Erimer <[email protected]> wrote:
> >
> > On 11/28/05, Andrew Morton <[email protected]> wrote:
> > > XFS went nuts. Please test the latest git snapshot which has fixes for
> > > this.
> >
> > I tried 2.6.15-rc2-git6 and just released 2.6.15-rc3. Result is same.
> > I still got occasional hangs.
>
> Please generate the sysrq-T trace when the system hangs.
I tried sysrq-T trace. But, When hit the bug, system completely freezes.
Alt+sysrq+t (Normally Alt+sysrq+t works perfectly) or any other
combination does not respond. Is there any other way to trace this?
Also, I will try just-released 2.6.15-rc4 and let know the result.
> > When I check my syslog, I found no error
> > messages. But notice, XFS related errors have gone.
>
> OK, we might have fixed XFS.
Yes, thanks
> > Nov 29 23:23:57 hightemple gconfd (root-11625): starting (version
> > 2.12.1), pid 11625 user 'root'
> > Nov 29 23:23:57 hightemple gconfd (root-11625): Resolved address
> > "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
> > configuration source at position 0
> > Nov 29 23:23:57 hightemple gconfd (root-11625): Resolved address
> > "xml:readwrite:/root/.gconf" to a writable configuration source at
> > position 1
> > Nov 29 23:23:57 hightemple gconfd (root-11625): Resolved address
> > "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
> > configuration source at position 2
>
> I assume the above isn't kernel-related?
Yes, above is not related to the kernel. It is a Gnome thing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]