From: Jiri Slaby <jslaby@suse.cz>
To: tingwei liu <tingw.liu@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, dhillf@gmail.com
Subject: Re: Suse 11 SP1 kernel panic on HP hardware
Date: Tue, 24 Jul 2012 23:51:35 +0200 [thread overview]
Message-ID: <500F18E7.2040809@suse.cz> (raw)
In-Reply-To: <CA+qZnSSazFWLKq5ao51JX=H-NCbwLD=6ypGXOeqQF72s7ZbTVA@mail.gmail.com>
On 07/24/2012 12:56 PM, tingwei liu wrote:
> On Tue, Jul 24, 2012 at 6:53 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> On Tue, 24 Jul 2012 18:39:20 +0800
>> tingwei liu <tingw.liu@gmail.com> wrote:
>>
>>> Suse 11 SP1 kernel panic。
>>>
>>> I can't debug it without debuginfo. Who can give me a link of sels
>>> 2.6.32.12-0.7.default.debug or give some advise.
>>
>> For distribution kernels (which tend to contain lots of other patches)
>> it is best to talk to your distribution support as a starter and/or their
>> forums.
>>
> I have report bug on suse website, but I haven't got any response until now!
Well, where exactly?
> Can you give some advice?
> I thought this maybe a kernel bug.
Yes, first upgrade to the latest kernel provided by Suse (2.6.32.59).
You can also try to reproduce with -vanilla flavour. This is a pure
upstream version with no suse patches (you will lose apparmor for example):
http://download.opensuse.org/repositories/Kernel:/SLE11-SP1/SUSE_SLE-11_SP1/
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-07-24 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 23:39 Suse 11 SP1 kernel panic on HP hardware tingwei liu
2012-07-24 10:39 ` tingwei liu
2012-07-24 10:53 ` Alan Cox
2012-07-24 10:56 ` tingwei liu
2012-07-24 11:23 ` Alan Cox
2012-07-24 21:51 ` Jiri Slaby [this message]
2012-07-25 0:12 ` tingwei liu
2012-07-24 18:03 ` Linus Torvalds
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=500F18E7.2040809@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tingw.liu@gmail.com \
/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.