From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: FW: BUG on 2.5.74 for Tiger4
Date: Wed, 16 Jul 2003 15:25:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105836945607691@msgid-missing> (raw)
>>>>> On Wed, 16 Jul 2003 16:39:29 +0800, "Yu, Luming" <luming.yu@intel.com> said:
Luming> Is it known issue? (The tree is pulled from
Luming> http://lia64.bkbits.net/linux-ia64-2.5
Luming> <http://lia64.bkbits.net:8080/linux-ia64-2.5> yesterday).
Luming> "Kernel BUG at timer.c:380!"
Luming> This bug appears randomly. Sometimes after 'su', sometimes
Luming> simply after "ls"
Depends on _when_ you pulled it yesterday. There were some per-CPU
bugs left that could cause this. But as of yesterday afternoon, this
should be all fixed (the proper way).
--david
PS: Please don't send HTML this mailing list. No need to waste
bits...
reply other threads:[~2003-07-16 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105836945607691@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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