From: Alexander Nyberg <alexn@telia.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de
Subject: 2.6.8.1-mm, programs crashing on x86_64
Date: Fri, 20 Aug 2004 19:45:02 +0200 [thread overview]
Message-ID: <1093023902.908.8.camel@boxen> (raw)
This does not happen in linus -bk. I noticed it happens in
2.6.8-mm2 also, but not sure about earlier. I'll try some earlier
-mm's and if noone knows what could be it I'll do a binary search.
Must be quite newly introduced though...
boxen:~# chroot /mnt/store/x86/ bash
bash[911] bad frame in 32bit signal deliver frame:00000000ffffd220 rip:556605d6 rsp:ffffd500 orax:ffffffffffffffff
bash[910] bad frame in 32bit signal deliver frame:00000000ffffd220 rip:556605d6 rsp:ffffd500 orax:ffffffffffffffff
bash[910]: segfault at 00000000ffffd51c rip 00000000556605d6 rsp 00000000ffffd500 error 7
bash[911]: segfault at 00000000ffffd51c rip 00000000556605d6 rsp 00000000ffffd500 error 7
next reply other threads:[~2004-08-20 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 17:45 Alexander Nyberg [this message]
2004-08-20 20:35 ` 2.6.8.1-mm, programs crashing on x86_64 Alexander Nyberg
2004-08-20 20:35 ` Alexander Nyberg
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=1093023902.908.8.camel@boxen \
--to=alexn@telia.com \
--cc=ak@suse.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