From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Alain Knaff <alain@knaff.lu>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [GIT PULL] bzip2/lzma kernel compression
Date: Sun, 11 Jan 2009 03:47:56 +0100 [thread overview]
Message-ID: <20090111024756.GB7077@elte.hu> (raw)
In-Reply-To: <86802c440901091343p6797536bxf73107fa1672d29b@mail.gmail.com>
* Yinghai Lu <yinghai@kernel.org> wrote:
> On Fri, Jan 9, 2009 at 12:52 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> > On Fri, Jan 9, 2009 at 10:45 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> >> Hi Linus,
> >>
> >> This tree contains the bzip2 and LZMA kernel compression work that
> >> Alain Knaff has done. Sending this as a separate pull request in case
> >> you think that it is too late or immature for this cycle.
> >>
> >> The good part is that it is a highly "brittle" feature -- if it fails,
> >> it will fail noisily and obviously.
> >>
> >> I have not included the ARM parts that Alain developed; I will leave
> >> those to be fed through rmk.
> >>
> >> One of the main attractions of this patchset is that it uses the newer
> >> lib/zlib_inflate code even for the kernel decompressor. Once all
> >> architectures that use the older lib/inflate.c have been converted
> >> over, we can remove that code entirely.
> >
> > it seems still have some problem
> > mydisk13_x86_64.lzma is by lzma -9
> >
> > [ 47.404316] RAMDISK: lzma image found at block 0
> > [ 51.676838] RAMDISK: incomplete write (-28 != 130)
> > [ 51.894794] calling 5_generic_delete_inode_async+0x0/0xa9 @ 2316
> > [ 51.900895] initcall 5_generic_delete_inode_async+0x0/0xa9 returned
> > 0 after 3 usecs
> > [ 51.901117] kjournald starting. Commit interval 5 seconds
> > [ 51.901130] EXT3 FS on ram0, internal journal
> > [ 51.901138] EXT3-fs: mounted filesystem with ordered data mode.
> > [ 51.901151] VFS: Mounted root (ext3 filesystem) on device 1:0.
> > [ 51.901168] async_waiting @ 1
> > [ 51.904191] calling 6_generic_delete_inode_async+0x0/0xa9 @ 2317
> > [ 51.907123] initcall 6_generic_delete_inode_async+0x0/0xa9 returned
> > 0 after 2861 usecs
> > [ 51.947093] async_continuing @ 1 after 44846 usec
> > [ 51.951839] Freeing unused kernel memory: 448k freed
> > [ 51.957245] init_special_inode: bogus i_mode (4467)
> >
>
> the .lzma is corrupted. it is strange. i was compiling kernel when lzma
> it...
>
> recreate that .lzma the kernel works well.
was the linux/.lzma file corrupted, and once you removed the stale file it
all works fine and the problem does not come back?
I.e. the tree as offered by hpa is fine?
Ingo
next prev parent reply other threads:[~2009-01-11 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 18:45 H. Peter Anvin
2009-01-09 20:52 ` Yinghai Lu
2009-01-09 21:43 ` Yinghai Lu
2009-01-11 2:47 ` Ingo Molnar [this message]
2009-01-11 2:50 ` H. Peter Anvin
2009-01-11 7:07 ` Yinghai Lu
[not found] ` <4968A737.7040909@knaff.lu>
2009-01-11 0:33 ` H. Peter Anvin
2009-01-11 7:01 ` Alain Knaff
2009-01-15 13:19 Etienne Lorrain
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=20090111024756.GB7077@elte.hu \
--to=mingo@elte.hu \
--cc=alain@knaff.lu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®