From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-parisc@vger.kernel.org, Guy Martin <gmsoft@tuxicoman.be>
Subject: Re: Reproducible kernel panic using gdb
Date: Tue, 29 Oct 2013 21:37:49 +0100 [thread overview]
Message-ID: <52701C9D.7080906@gmx.de> (raw)
In-Reply-To: <1383023163.19537.3.camel@dabdike.int.hansenpartnership.com>
On 10/29/2013 06:06 AM, James Bottomley wrote:
>
> On Mon, 2013-10-28 at 16:08 +0100, Rolf Eike Beer wrote:
>> James Bottomley: wrote
>>> On Mon, 2013-10-28 at 10:00 +0100, Guy Martin wrote:
>>>> Hi Helge,
>>>>
>>>>>
>>>>> Works without crash for me on 3.12-rc6 ?
>>>>> Linux ls3011 3.12.0-rc6-64bit+
>>>>>
>>>>> Since you run 3.10.6, maybe updating the kernel might help.
>>>>> Esp. this patch, which has been backported to kernel 3.10 (and is in
>>>>> 3.10.17):
>>>>> http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.10.y&id=77587e89405f5d8225a0e750df254bcc2dcb73e1
>>>>
>>>> Still the same problem with 3.12-rc6 here :
>>>
>>> What system and CPU?
>>
>> C8000
>
> I tried this on a rp3440 (pa8800) and I can't reproduce. I think it
> might be something about the way the kernel is compiled. The (null)
> values for rp2 and IOAQ[0] look suspicious.
I tried it again, but this time on my c8000..
Again, it does not crash for me.
Kernel is 3.12.0-rc7-64bit.
I think James is right. Might be something with your compiler, but it would
be interesting what it is...
Helge
next prev parent reply other threads:[~2013-10-29 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 8:16 Reproducible kernel panic using gcc Guy Martin
2013-10-25 14:31 ` Aw: " Helge Deller
2013-10-28 9:00 ` Aw: Reproducible kernel panic using gdb Guy Martin
2013-10-28 14:30 ` James Bottomley
2013-10-28 15:08 ` Rolf Eike Beer
2013-10-29 5:06 ` James Bottomley
2013-10-29 20:37 ` Helge Deller [this message]
2013-10-31 14:35 ` Guy Martin
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=52701C9D.7080906@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=eike-kernel@sf-tec.de \
--cc=gmsoft@tuxicoman.be \
--cc=linux-parisc@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.