From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Date: Wed, 16 Feb 2005 21:04:41 +0100 [thread overview]
Message-ID: <20050216200441.GH19871@charite.de> (raw)
In-Reply-To: <20050216153338.GA26953@atrey.karlin.mff.cuni.cz>
* Jan Kara <jack@suse.cz>:
> I guess the system is SMP...
Indeed it is. Dual Xeon with SMP.
> Sadly a few lines in the beginning of the
> report are missing (probably scrolled off the screen)
Yes, this sucks. I rebooted with vesafb active, no I do have 50 lines :)
> but it seems similar like a several other oopses I've seen reported
> recently. Is this the first time you hit this bug?
It's actually the second time. The first time it hit the SAME box but
with kernel-2.6.10 (vanilla) after 30 days of uptime. Nobody had a
camera at hand, so I couldn't take a photo.
Any suggestions? I'm open to suggestions. One difference between the
2.6.10 and 2.6.10-ac12 was that 2.6.10 has no in-kernel irq
balancing, while in 2.6.10-ac12 I acivated that.
--
Ralf Hildebrandt (i.A. des IT-Zentrum) Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962
IT-Zentrum Standort CBF send no mail to spamtrap@charite.de
next prev parent reply other threads:[~2005-02-16 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 14:56 Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction) Ralf Hildebrandt
2005-02-16 15:33 ` Jan Kara
2005-02-16 20:04 ` Ralf Hildebrandt [this message]
2005-02-16 21:54 ` Dale Blount
2005-02-16 22:00 ` Ralf Hildebrandt
2005-02-16 22:55 ` Andrew Morton
2005-02-17 10:58 ` Ralf Hildebrandt
2005-02-17 13:21 ` Ralf Hildebrandt
2005-02-17 15:51 ` Randy.Dunlap
2005-02-17 16:00 ` Ralf Hildebrandt
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=20050216200441.GH19871@charite.de \
--to=ralf.hildebrandt@charite.de \
--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