linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: Dan Malek <dan@netx4.com>
Cc: Daniel Wu <Daniel.Wu@alcatel.com.au>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Using zImage.initrd
Date: Fri, 09 Jun 2000 13:59:01 +1000	[thread overview]
Message-ID: <27181.960523141@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Dan Malek <dan@netx4.com> of "Thu, 08 Jun 2000 22:52:43 -0400." <39405BFB.1E231721@embeddededge.com>


On Thu, 08 Jun 2000 22:52:43 -0400, Dan Malek <dan@netx4.com> writes:
>Murray Jensen wrote:
>
>> Try this patch:
>>
>> --- fs/buffer.c 2000/05/16 01:31:41     1.1.1.12
>
>
>The 2.2.xx kernels don't have any ramdisk patch required.  This was
>broken in later 2.3.xx kernels.  Don't be trying this in 2.2 kernels.

It's not the ramdisk patch, just the simple check to ensure that the
"bdflush_tsk" variable is not NULL in wakeup_bdflush(). This patch should
be ok to try if you are getting a crash in __wake_up(). It may or may not
fix the problem, but it shouldn't hurt. Cheers!
								Murray...
--
Murray Jensen, CSIRO Manufacturing Sci & Tech,         Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
Internet: Murray.Jensen@cmst.csiro.au  (old address was mjj@mlb.dmt.csiro.au)


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-09  3:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-08 22:38 Using zImage.initrd Daniel Wu
2000-06-09  2:40 ` Murray Jensen
2000-06-09  2:52   ` Dan Malek
2000-06-09  3:59     ` Murray Jensen [this message]
2000-06-09  3:15 ` Dan Malek
2000-06-09  8:51   ` Daniel Wu
2000-06-09 15:43     ` Dan Malek
2000-06-12 23:09       ` Daniel Wu

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=27181.960523141@msa.cmst.csiro.au \
    --to=murray.jensen@cmst.csiro.au \
    --cc=Daniel.Wu@alcatel.com.au \
    --cc=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).