Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2

[Andrew Morton <akpm@osdl.org>]

Tarkan Erimer <tarkane@gmail.com> wrote:
>
> On 11/28/05, Andrew Morton <akpm@osdl.org> 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.

> When I check my syslog, I found no error
> messages. But notice, XFS related errors have gone.

OK, we might have fixed XFS.

> I paste last few
> lines of my syslog.
> 
> ----syslog ----
> Nov 29 23:22:43 hightemple kernel: [  518.648894] NTFS-fs warning
> (device hda1): ntfs_filldir(): Skipping unrepresentable inode 0x516d.
> Nov 29 23:22:54 hightemple kernel: [  529.059660] printk: 36 messages
> suppressed.
> Nov 29 23:22:54 hightemple kernel: [  529.059669] NTFS-fs error
> (device hda1): ntfs_ucstonls(): Unicode name contains characters that
> cannot be converted to character set iso8859-1.  You might want to try
> to use the mount option nls=utf8.
> Nov 29 23:22:54 hightemple kernel: [  529.059676] NTFS-fs warning
> (device hda1): ntfs_filldir(): Skipping unrepresentable inode 0x57db.

Anton is the man.

> 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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/