From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Marco Berizzi" <pupilla@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd
Date: Mon, 11 Jun 2007 04:24:15 +0530 [thread overview]
Message-ID: <a781481a0706101554n259f570bre228faff881ddf4a@mail.gmail.com> (raw)
In-Reply-To: <BAY103-DAV160F003E4B6DBCE103C7C9B21B0@phx.gbl>
> > On 6/8/07, Marco Berizzi <pupilla@hotmail.com> wrote:
> >> After few hours linux has crashed with this message:
> >> BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
> >
> > Which kernel (exactly) was this
>
> 2.6.21.3
>
> > and does this occur
> > reproducibly?
>
> I don't know. I try to explain. With all debugging options
> enabled 2.6.21.x has never crashed. After two days 2.6.21.3
> was running without any debug options, it has crashed.
> Tomorrow morning I will start that linux box with linux 2.6.21.3
> without any debug options, and I will keep you informed
> (friday evening I have switched back to 2.6.21.3 with debug
> options enabled, so the machine doesn't crash during the week
> end: this system is my company firewall.)
>
> > Also, could you please send the dmesg,
> [...]
> >
> > stack trace, etc for when this happened?
>
> I have only a monitor bitmap. Tell me if you want it.
Yes, please.
Thanks.
next prev parent reply other threads:[~2007-06-10 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 11:34 Marco Berizzi
2007-03-16 1:25 ` David Chinner
[not found] ` <BAY103-DAV13EC09E9BCB3E8C9D5EEA2B2710@phx.gbl>
2007-03-16 19:59 ` David Chinner
2007-03-17 13:00 ` Marco Berizzi
[not found] ` <BAY103-DAV9C465F21C87A900314523B2760@phx.gbl>
2007-03-20 6:46 ` David Chinner
2007-06-07 7:44 ` Marco Berizzi
2007-06-07 13:05 ` David Chinner
2007-06-08 13:59 ` Marco Berizzi
2007-06-10 7:05 ` Satyam Sharma
2007-06-10 12:20 ` Marco Berizzi
2007-06-10 22:54 ` Satyam Sharma [this message]
2007-06-12 6:14 ` David Chinner
2007-06-12 7:14 ` Marco Berizzi
2007-06-19 10:36 ` Marco Berizzi
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=a781481a0706101554n259f570bre228faff881ddf4a@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.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: 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®