From: Raghavan.Anurag@in.bosch.com (Anurag Raghavan (RBEI/ETW11))
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad block Management Patch
Date: Tue, 24 Jan 2017 07:15:33 +0000 [thread overview]
Message-ID: <8c362ab6c4194debb9dcced1714cb368@SGPMBX1023.APAC.bosch.com> (raw)
In-Reply-To: <20170124070950.GA13251@kroah.com>
Hi Greg,
Thank You for the information. I have few more concerns here,
I am facing the following uncorrectable ECC error, Can you suggest any kernel version or any patches to overcome this issue.
Error logs:
[ 1.797141] UBI error: ubi_io_read: error -74 (ECC error) while reading 253952 bytes from PEB 445:8192, read 253952 bytes
[ 1.808274] UBIFS error (pid 491): ubifs_scan: corrupt empty space at LEB 489:233760
[ 1.816037] UBIFS error (pid 491): ubifs_scanned_corruption: corruption at LEB 489:233760
[ 1.828660] UBIFS error (pid 491): ubifs_scan: LEB 489 scanning failed
[ 1.835215] UBIFS warning (pid 491): ubifs_ro_mode: switched to read-only mode, error -117
[ 1.843502] UBIFS error (pid 491): make_reservation: cannot reserve 58 bytes in jhead 2, error -117
[ 1.852569] UBIFS error (pid 491): do_writepage: cannot write page 0 of inode 76584, error -117
dpkg: error: unable to sync new file '/var/lib/dpkg/arch-new': Structure needs cleaning
Best regards
Raghavan Anurag
RBEI/ETW1
Tel. +91(422)667-4001 | Mobil 9986968950
-----Original Message-----
From: kernelnewbies-bounces@kernelnewbies.org [mailto:kernelnewbies-bounces at kernelnewbies.org] On Behalf Of Greg KH
Sent: Tuesday, January 24, 2017 12:40 PM
To: Anurag Raghavan (RBEI/ETW11) <Raghavan.Anurag@in.bosch.com>
Cc: Kernelnewbies at kernelnewbies.org
Subject: Re: Bad block Management Patch
On Tue, Jan 24, 2017 at 07:02:25AM +0000, Anurag Raghavan (RBEI/ETW11) wrote:
> Hi All,
>
> I am using kernel version-3.0.35
That is very very old and obsolete and insecure. I strongly recommend you update to a modern and maintained kernel version in order to get any help from the community, and to ensure that your device actually works properly.
If you are stuck at this kernel version because it is supported by a vendor, please contact them for support as you are paying them, and they are the only ones that can help you out.
Good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2017-01-24 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 7:02 Bad block Management Patch Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:09 ` Greg KH
2017-01-24 7:15 ` Anurag Raghavan (RBEI/ETW11) [this message]
2017-01-24 7:38 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 4:56 Anurag Raghavan (RBEI/ETW11)
2017-01-24 4:56 ` Anurag Raghavan (RBEI/ETW11)
2017-01-24 7:58 ` Boris Brezillon
2017-01-24 8:11 ` Richard Weinberger
2017-01-24 4:56 Anurag Raghavan (RBEI/ETW11)
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=8c362ab6c4194debb9dcced1714cb368@SGPMBX1023.APAC.bosch.com \
--to=raghavan.anurag@in.bosch.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.