From: Tarkan Erimer <tarkane@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2
Date: Tue, 29 Nov 2005 21:57:47 +0000 [thread overview]
Message-ID: <9611fa230511291357g3aa964adj6918fea50f5ee66e@mail.gmail.com> (raw)
In-Reply-To: <20051127165733.643d5444.akpm@osdl.org>
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. When I check my syslog, I found no error
messages. But notice, XFS related errors have gone. 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.
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
Nov 29 23:41:57 hightemple syslogd 1.4.1: restart.
----syslog----
Regards
next prev parent reply other threads:[~2005-11-29 21:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 11:12 Tarkan Erimer
2005-11-25 11:19 ` Arjan van de Ven
2005-11-27 11:17 ` Tarkan Erimer
2005-11-27 11:58 ` Arjan van de Ven
2005-11-27 19:08 ` Tarkan Erimer
2005-11-27 19:12 ` Arjan van de Ven
2005-11-27 19:18 ` Tarkan Erimer
2005-11-28 0:57 ` Andrew Morton
2005-11-29 21:57 ` Tarkan Erimer [this message]
2005-11-29 23:10 ` Andrew Morton
2005-11-30 13:53 ` Anton Altaparmakov
2005-12-01 20:47 ` Tarkan Erimer
2005-12-01 20:42 ` Tarkan Erimer
2005-12-02 12:49 ` Tarkan Erimer
2005-12-05 14:30 ` Tarkan Erimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9611fa230511291357g3aa964adj6918fea50f5ee66e@mail.gmail.com \
--to=tarkane@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®