linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Yu Hao <yhao016@ucr.edu>
Cc: chengzhihao1 <chengzhihao1@huawei.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: divide error in ubi_attach_mtd_dev
Date: Thu, 20 Apr 2023 19:33:19 +0200 (CEST)	[thread overview]
Message-ID: <977347543.226888.1682011999468.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CA+UBctBVHouL-3rM3zKYLpk01fXFvCpBnU7EpSRVdGW7cEjcJQ@mail.gmail.com>

----- Ursprüngliche Mail -----
> The kernel is in qemu. We find that the `mtd` is from
> `mtd = get_mtd_device(NULL, req.mtd_num);` in function `ctrl_cdev_ioctl`.
> And we are still trying to figure out what MTD is.

Can you please share the qemu command line?

Within Linux you can query /proc/mtd or /sys/class/mtd/
to get infos about the MTD in question.

Thanks,
//richard
 

  reply	other threads:[~2023-04-20 17:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  5:10 BUG: divide error in ubi_attach_mtd_dev Yu Hao
2023-04-18  5:16 ` Yu Hao
2023-04-18  6:30   ` Richard Weinberger
2023-04-20  4:49     ` Zhihao Cheng
2023-04-20 17:27       ` Yu Hao
2023-04-20 17:33         ` Richard Weinberger [this message]
2023-04-20 18:14           ` Yu Hao
2023-04-20 20:36             ` Richard Weinberger
2023-04-23  3:20               ` Zhihao Cheng
2023-04-23  8:02                 ` Richard Weinberger
2023-04-23  9:13                   ` Zhihao Cheng
2023-10-02 10:11                     ` Lee Jones
2023-10-02 10:28                       ` Richard Weinberger
2023-10-02 14:04                         ` Lee Jones
2023-10-02 14:15                           ` Richard Weinberger
2023-10-02 14:36                             ` Lee Jones
2023-06-20  9:17 ` admamiac

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=977347543.226888.1682011999468.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=vigneshr@ti.com \
    --cc=yhao016@ucr.edu \
    /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).