public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Powalowski <tobias.powalowski@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Possible 32bit i686 kernel hard crash bug 3.3.4?
Date: Wed, 02 May 2012 09:38:45 +0200	[thread overview]
Message-ID: <4FA0E485.80902@googlemail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 432 bytes --]

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.

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 --]

             reply	other threads:[~2012-05-02  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  7:38 Tobias Powalowski [this message]
2012-05-02  9:12 ` Possible 32bit i686 kernel hard crash bug 3.3.4? Jan Rękorajski
2012-05-02  9:45   ` Tobias Powalowski
2012-05-02 15:48     ` Tobias Powalowski

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=4FA0E485.80902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox