From: tomy@kalkitech.in (tomy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: Mounting issue
Date: Sun, 09 Jun 2013 13:05:32 +0530 [thread overview]
Message-ID: <51B43044.8030905@kalkitech.in> (raw)
In-Reply-To: <CAC+QLdSDRrFv6WLFqr4WVMn8aw4nN99cRbmGK3VxbzRtnUStWg@mail.gmail.com>
Hello,
This is happening when we give reboot command from Linux
console. But if the files got corrupted then every time this issue
should occur rt?. This is happening very randomly.
Every running scripts will be closed as part of reboot
Regards,
Tomy
On 09-Jun-2013 12:16 PM, Mandeep Sandhu wrote:
>
>
> On Jun 8, 2013 12:56 PM, "tomy" <tomy@kalkitech.in
> <mailto:tomy@kalkitech.in>> wrote:
> >
> >
> > Hello,
> > Currently I am working on an embedded system which is
> having 512 MB NAND flash . The embedded system is having u-boot,
> kernel, root filesystem (JFFS2) and a backup file system all reside in
> NAND flash. I am now facing a booting issue randomly (reboot command
> from linux console ) and the snapshot of the error is given below
> >
>
> Does this happen only when u give the reboot command? Could it be
> possible that some files on your flash partition have been corrupted?
>
> What kernel and busybox version are you running?
>
> What does this 0x000b exit status mean? Looks like your scripts may
> have been killed by the reboot cmd I've given.
>
> HTH,
> -mandeep
>
> > udevd-work[1092]: '/etc/udev/scripts/network.sh' unexpected exit
> with status 0x000b
> > udevd-work[1089]: '/etc/udev/scripts/network.sh' unexpected exit
> with status 0x000b
> > udevd-work[1032]: '/etc/udev/scripts/mount.sh' unexpected exit with
> status 0x000b
> >
> >
> > udevd-work[1112]: '/etc/udev/scripts/network.sh' unexpected exit
> with status 0x000b
> >
> >
> > /etc/init.d/rc: line 45: 1760 Segmentation fault "$@"
> > /etc/rcS.d/S37populate-volatile.sh: line 194: 1773 Segmentation
> fault sh /etc/volatile.cache
> > ln: /var/run/ld.so.cache: No such file or directory
> > /etc/init.d/rc: line 45: 1780 Segmentation fault "$@"
> > /etc/rcS.d/S55bootmisc.sh: line 68: 1784 Segmentation fault
> /etc/init.d/hwclock.sh start
> >
> > INIT: Entering runlevel: 5
> >
> > After this, the board is not pinging and not able to login through
> console and the only solution to recover from this is power reboot.
> But in the next reboot everything will be ok.
> >
> > The problem is happening randomly may be in 30 or 40 software
> reboots. I am not sure whether the issue is happening because of
> mounting problem, but still why this is not happening in every reboots.
> >
> > So can you people help me to find out the root cause of this problem.
> >
> > Regards,
> > Tomy
> >
> >
> >
> >
> >
> >
> >
> > "Disclaimer: This message is being sent from Kalki Communication
> Technologies
> >
> > Pvt Ltd (KALKITECH). and may contain information which is
> confidential or
> >
> >
> >
> > privileged. If you are not the intended recipient, please advise the
> sender
> >
> > immediately by reply e-mail and delete this message and any attachments
> >
> >
> >
> > without retaining a copy. Any unauthorized use of the content of
> this message
> >
> > can expose the responsible party to civil and/or criminal penalties,
> >
> >
> >
> > and may constitute a more serious offense. Further the company does
> not accept
> >
> > liability for any errors, omissions, viruses or computer problems
> >
> >
> >
> > experienced as a result of this transmission. If you have received this
> >
> > message in error, notice is hereby given that no representation,
> contract or
> >
> >
> >
> > other binding obligation shall be created by this e-mail."
> >
> >
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
>
"Disclaimer: This message is being sent from Kalki Communication Technologies
Pvt Ltd (KALKITECH). and may contain information which is confidential or
privileged. If you are not the intended recipient, please advise the sender
immediately by reply e-mail and delete this message and any attachments
without retaining a copy. Any unauthorized use of the content of this message
can expose the responsible party to civil and/or criminal penalties,
and may constitute a more serious offense. Further the company does not accept
liability for any errors, omissions, viruses or computer problems
experienced as a result of this transmission. If you have received this
message in error, notice is hereby given that no representation, contract or
other binding obligation shall be created by this e-mail."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130609/6e69c120/attachment.html
next prev parent reply other threads:[~2013-06-09 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51B2D885.3050302@kalkitech.in>
2013-06-08 7:13 ` Fwd: Mounting issue tomy
2013-06-09 6:46 ` Mandeep Sandhu
2013-06-09 7:35 ` tomy [this message]
2013-06-10 6:24 ` Mandeep Sandhu
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=51B43044.8030905@kalkitech.in \
--to=tomy@kalkitech.in \
--cc=kernelnewbies@lists.kernelnewbies.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).