From: Jeff Angielski <jeff@theptrgroup.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS assert failed in ubifs_dirty_inode
Date: Mon, 25 Jan 2010 16:03:31 -0500 [thread overview]
Message-ID: <4B5E0723.7070903@theptrgroup.com> (raw)
In-Reply-To: <1264367251.2401.34.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Artem Bityutskiy wrote:
> The most interesting stack dump for the first error is not there because
> it was not printed to the serial console. Please, take a look here:
>
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport
>
> At the item number 4 you'll find some solutions. The 'ignore_loglevel'
> kernel option should be suitable for you. Please, add it and send me the
> stack dump.
As per your request, I passed in ignore_loglevel and captured the entire
boot process up to the login prompt. Just search for assert and you'll
find the error.
I attached the file to this email.
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
[-- Attachment #2: ubifs_assert_dirty.cap.gz --]
[-- Type: application/x-gzip, Size: 93273 bytes --]
next prev parent reply other threads:[~2010-01-25 21:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 3:03 UBIFS assert failed in ubifs_dirty_inode Jeff Angielski
2010-01-24 21:07 ` Artem Bityutskiy
2010-01-25 21:03 ` Jeff Angielski [this message]
2010-01-26 4:40 ` Artem Bityutskiy
2010-01-26 5:48 ` Matt Mackall
2010-01-26 10:03 ` Artem Bityutskiy
2010-01-26 10:07 ` Artem Bityutskiy
2010-01-27 1:44 ` Jeff Angielski
2010-01-27 2:13 ` Matt Mackall
2010-01-27 3:07 ` Jeff Angielski
2010-01-27 4:20 ` Artem Bityutskiy
2010-01-27 5:14 ` Matt Mackall
2010-01-29 11:27 ` Herbert Xu
2010-01-29 11:32 ` Artem Bityutskiy
2010-01-29 11:35 ` Herbert Xu
2010-02-02 10:42 ` Artem Bityutskiy
2010-01-29 8:48 ` Herbert Xu
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=4B5E0723.7070903@theptrgroup.com \
--to=jeff@theptrgroup.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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