From: Patrick McHardy <kaber@trash.net>
To: odie@cs.aau.dk
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Chuck Ebbert <cebbert@redhat.com>,
x86@kernel.org
Subject: Re: 2.6.26-git: NULL pointer deref in __switch_to
Date: Mon, 16 Jun 2008 12:29:08 +0200 [thread overview]
Message-ID: <48564074.9030301@trash.net> (raw)
In-Reply-To: <1213611339.2495.11.camel@odie.local>
Simon Holm Th������������������������ wrote:
> fre, 13 06 2008 kl. 15:47 -0700, skrev Suresh Siddha:
>> On Fri, Jun 13, 2008 at 11:24:01AM -0700, Vegard Nossum wrote:
>>> On Fri, Jun 13, 2008 at 7:42 PM, Patrick McHardy <kaber@trash.net> wrote:
>>>> I get this oops once a day, its apparently triggered by something
>>>> run by cron, but the process is a different one each time.
>>>>
>>>> Kernel is -git from yesterday shortly before the -rc6 release
>>>> (last commit is the usb-2.6 merge, the x86 patches are missing),
>>>> .config is attached.
>>>>
>>>> I'll retry with current -git, but the patches that have gone in
>>>> since I last updated don't look related.
>>>>
>>> Thanks for the report.
>>>
>>>> [62060.043009] BUG: unable to handle kernel NULL pointer dereference at
>>>> 000001ff
>>>> [62060.043009] IP: [<c0102a9b>] __switch_to+0x2f/0x118
>>>> [62060.043009] *pde = 00000000
>>>> [62060.043009] Oops: 0002 [#1] PREEMPT
>> Patrick, Do you see any other error messages before this BUG stmt? Can you
>> please provide the complete kernel log till the point of failure?
>>
> Suresh, I'm pretty sure this is the same problem that I reported two
> weeks ago [1]. I suggested that you tried running lguest and reproduced
> the problem locally, but I did not hear back from you. Now Patrick is
> reporting the same problem and is also indicating that the problem is
> correlated with his use of lguest, so I'd really like you to follow up
> on this.
>
>> I have a theory for your problem and have appended a patch to test it. Can
>> you please check if the appended patch fixes your problem.
>>
> At least for me, with this patch applied on top of -rc4 or -rc6+ the
> problem still triggered after running an lguest guest for less than 30
> seconds (the guest didn't even finish the boot of an image of Ubuntu
> with no X-server).
The patch also didn't fix the problem here, I got the same crash this
morning. Unfortunately netconsole didn't log it, but its essentially
the same as the one I posted.
next prev parent reply other threads:[~2008-06-16 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 17:42 2.6.26-git: NULL pointer deref in __switch_to Patrick McHardy
2008-06-13 18:24 ` Vegard Nossum
2008-06-13 22:47 ` Suresh Siddha
2008-06-14 6:20 ` Ingo Molnar
2008-06-14 7:39 ` Patrick McHardy
2008-06-16 11:06 ` Jens Axboe
2008-06-14 7:36 ` Patrick McHardy
2008-06-16 10:15 ` Simon Holm Thøgersen
2008-06-16 10:29 ` Patrick McHardy [this message]
2008-06-16 12:10 ` Patrick McHardy
2008-06-16 17:49 ` Suresh Siddha
2008-06-16 21:21 ` Simon Holm Thøgersen
2008-06-17 23:50 ` Suresh Siddha
2008-06-18 5:34 ` Rusty Russell
2008-06-18 6:23 ` Suresh Siddha
2008-06-18 12:19 ` Rusty Russell
2008-06-18 8:42 ` Patrick McHardy
2008-06-18 13:57 ` Simon Holm Thøgersen
2008-06-13 20:10 ` Rafael J. Wysocki
2008-06-14 7:33 ` Patrick McHardy
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=48564074.9030301@trash.net \
--to=kaber@trash.net \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=odie@cs.aau.dk \
--cc=suresh.b.siddha@intel.com \
--cc=vegard.nossum@gmail.com \
--cc=x86@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