public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Fix for vmalloc problem was Re: 2.6.10-rc1-mm3
Date: Sat, 06 Nov 2004 00:29:43 +1100	[thread overview]
Message-ID: <418B8047.5050902@kolivas.org> (raw)
In-Reply-To: <20041105131232.GA1030@wotan.suse.de>

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

Andi Kleen wrote:
> On Fri, Nov 05, 2004 at 11:16:24PM +1100, Con Kolivas wrote:
> 
>>Andi Kleen wrote:
>>
>>>Con Kolivas <kernel@kolivas.org> writes:
>>>
>>>
>>>
>>>>It's life Jim but not as we know it...
>>>>
>>>>
>>>>This happened during modprobe of alsa modules. Keyboard still alive,
>>>>everything else dead; not even sysrq would do anything, netconsole had
>>>>no output, luckily this made it to syslog:
>>>
>>>
>>>I just tested modprobing of alsa (snd_intel8x0) and it works for me.
>>>Also vmalloc must work at least to some point.
>>>
>>>Can you confirm it's really caused by 4level by reverting all the 
>>>4level-* patches from broken out? 
>>
>>I dont recall blaming 4level. When I get a chance I'll try.
> 
> 
> This patch should fix it. Can you please test? Thanks.
> 
> -Andi
> 
> Fix silly typo in mm/vmalloc.c and some minor cleanups.

Boots fine now thanks.

Con

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-11-05 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041105001328.3ba97e08.akpm@osdl.org.suse.lists.linux.kernel>
     [not found] ` <418B5C70.7090206@kolivas.org.suse.lists.linux.kernel>
2004-11-05 11:53   ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:16     ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 12:23       ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 13:12       ` [PATCH] Fix for vmalloc problem was 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 13:29         ` Con Kolivas [this message]
2004-11-05 13:53           ` Andi Kleen

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=418B8047.5050902@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --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