From: Tobias Powalowski <tobias.powalowski@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible 32bit i686 kernel hard crash bug 3.3.4?
Date: Wed, 02 May 2012 17:48:44 +0200 [thread overview]
Message-ID: <4FA1575C.8010400@googlemail.com> (raw)
In-Reply-To: <4FA10250.5050104@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Am 02.05.2012 11:45, schrieb Tobias Powalowski:
> Am 02.05.2012 11:12, schrieb Jan Rękorajski:
>> On Wed, 02 May 2012, Tobias Powalowski wrote:
>>
>>> Hi,
>>> since we bumped to 3.3.4 some users reported hard crashes:
>>> https://bugs.archlinux.org/task/29694
>>> I cannot exactly say what it triggers it happens for me randomly.
>>> This kernel version is not usable for my server anymore.
>>> Hope you can help us. x86_64 seems not to be affected.
>> What version of binutils you built that kernel with?
>> Is it by any chance 2.22.52.0.2?
>>
> Well it's from 20120323 with this patch attached:
> https://projects.archlinux.org/svntogit/packages.git/commit/trunk/PKGBUILD?h=packages/binutils&id=9b0778356b73dd77ed7f98eae5dd5c1f5824ae96
>
> greetings
> tpowa
>
Ok issues identified,
broken binutils caused this.
Soryy for the blurb.
greetings
tpowa
--
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tpowa@archlinux.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
prev parent reply other threads:[~2012-05-02 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 7:38 Possible 32bit i686 kernel hard crash bug 3.3.4? Tobias Powalowski
2012-05-02 9:12 ` Jan Rękorajski
2012-05-02 9:45 ` Tobias Powalowski
2012-05-02 15:48 ` Tobias Powalowski [this message]
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=4FA1575C.8010400@googlemail.com \
--to=tobias.powalowski@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.