public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001732] fs-ecos bug/assertion Date: Thu, 24 Jan 2013 17:09:00 -0000 [thread overview] Message-ID: <20130124170846.25CE64680001@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001732-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001732 --- Comment #1 from praveenrai@ge.com 2013-01-24 17:08:45 GMT --- Able to reproduce the issue at will by a) Booting the system with correct node and files b) Erasing the flash c) Copying file to flash. Step (c) above results in BUG(). What these steps translate to is that if metadata is missing (with node present) the jffs2_open function is not able to get the right mode. If the mode is not right we hit the BUG(). -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2013-01-24 17:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-18 17:14 [Bug 1001732] New: " bugzilla-daemon 2013-01-18 17:19 ` [Bug 1001732] " bugzilla-daemon 2013-01-24 17:09 ` bugzilla-daemon [this message] 2013-01-25 1:35 ` bugzilla-daemon 2013-01-25 15:29 ` bugzilla-daemon 2013-01-26 18:16 ` bugzilla-daemon 2013-01-26 21:44 ` bugzilla-daemon 2013-01-27 3:07 ` bugzilla-daemon -- strict thread matches above, loose matches on Subject: below -- 2013-01-18 17:14 [Bug 1001732] New: " bugzilla-daemon 2013-01-18 17:19 ` [Bug 1001732] " bugzilla-daemon 2013-01-24 17:09 ` bugzilla-daemon 2013-01-25 1:35 ` bugzilla-daemon 2013-01-25 15:29 ` bugzilla-daemon 2013-01-26 18:16 ` bugzilla-daemon 2013-01-26 21:44 ` bugzilla-daemon 2013-01-27 3:07 ` bugzilla-daemon
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=20130124170846.25CE64680001@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).