public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: ranjith@hellwire.com To: insight-gnats@sources.redhat.com Cc: rangan_c_in@yahoo.com Subject: insight/218: Error after upgradation, High cpu usage Date: Wed, 02 Apr 2003 10:23:00 -0000 [thread overview] Message-ID: <20030402102105.28675.qmail@sources.redhat.com> (raw) >Number: 218 >Category: insight >Synopsis: Error after upgradation, High cpu usage >Confidential: no >Severity: non-critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Apr 02 10:23:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: ranjith@hellwire.com >Release: 2.4.18-27 >Organization: >Environment: Linux >Description: We are getting jounal error /etc/log/messages Apr 1 07:12:56 global kernel: Assertion failure in journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)" Apr 1 12:29:35 global kernel: kjournald starting. Commit interval 5 seconds Apr 1 12:29:35 global kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,65), internal journa This happened after upgradation to 2.4.18-27 smp. Our cpu usage has also gone high. Thanks Ranjith >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-02 10:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-02 10:23 ranjith [this message] 2003-04-02 15:05 kseitz
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=20030402102105.28675.qmail@sources.redhat.com \ --to=ranjith@hellwire.com \ --cc=insight-gnats@sources.redhat.com \ --cc=rangan_c_in@yahoo.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).