public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001732] New: fs-ecos bug/assertion Date: Fri, 18 Jan 2013 17:14:00 -0000 [thread overview] Message-ID: <bug-1001732-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001732 Summary: fs-ecos bug/assertion Product: eCos Version: unknown Platform: nios2_stratix2_2s60_rohs_tseplus (Stratix II, TSE+ design) OS/Version: Nios II Status: UNCONFIRMED Severity: major Priority: low Component: Filesystem support AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: praveenrai@ge.com CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=2034) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=2034) snapshot of debug window Hi, I have encountered an issue where opening a file in write mode with O_WRONLY|O_CREAT|O_TRUNC flags set is causing the code in fs-ecos.c (function jffs2_to_os_mode()) to hit BUG(). I have an onboard CFI flash and an offboard SPI flash. The problem is very intermittent and appears on both the flashes (more often on SPI flash). So far I have been able to reproduce it by erasing the SPI flash and then copying a file to it. The copy command sequence is as follows: copy->creat(destFile, filePermissions)->open( path, O_WRONLY | O_CREAT | O_TRUNC, mode )->jffs2_open()->jffs2_truncate_file(uint32_t osmode). When the error happens the argument osmode is either 0 or 10. In normal case osmode is usually 0x16F0008 or 0x16F0001. I have attached snapshot of nios debugger here for reference. Kindly let me know what could be the potential issue or areas to look at. Appreciate your help. Thanks, Praveen -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-01-18 17:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-18 17:14 bugzilla-daemon [this message] 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 2013-01-18 17:14 [Bug 1001732] New: " 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=bug-1001732-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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).