From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Zheyu Ma <zheyuma97@gmail.com>, Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: linux-ide@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ata: pata_marvell: Warning when probing the module
Date: Mon, 11 Apr 2022 08:53:29 +0900 [thread overview]
Message-ID: <05433153-0424-ab66-1573-993d0490c5bc@opensource.wdc.com> (raw)
In-Reply-To: <CAMhUBjkVME8D5KsHvT=uddBsW_Bh6wr7qeXS=UpQD4LgPmHffQ@mail.gmail.com>
On 4/10/22 15:30, Zheyu Ma wrote:
> Hello,
>
> I found a bug in the pata_marvell module.
> When probing the driver, it seems to trigger the error path and
> executes the function marvell_cable_detect(), but the
> 'ap->ioaddr.bmdma_addr' is not initialized, which causes a warning.
I do not have this hardware so I cannot debug this. Please debug it and
send a patch. bmdma_addr is normally set in ata_pci_bmdma_init(), but some
drivers set it manually in their probe functions. No idea about the
marvell driver, I have not checked it.
>
> The following log can reveal it:
>
> [ 3.453943] Bad IO access at port 0x1 (return inb(port))
> [ 3.454430] WARNING: CPU: 7 PID: 291 at lib/iomap.c:44 ioread8+0x4a/0x60
> [ 3.457962] RIP: 0010:ioread8+0x4a/0x60
> [ 3.466362] Call Trace:
> [ 3.466572] <TASK>
> [ 3.466756] marvell_cable_detect+0xad/0xf0 [pata_marvell]
> [ 3.467699] ata_eh_recover+0x3520/0x6cc0
> [ 3.473262] ata_do_eh+0x49/0x3c0
> [ 3.473906] ata_scsi_port_error_handler+0xd96/0x1d00
> [ 3.474355] ata_scsi_error+0x243/0x290
> [ 3.475428] scsi_error_handler+0x2ff/0xea0
> [ 3.477244] kthread+0x262/0x2e0
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-04-10 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 6:30 Zheyu Ma
2022-04-10 23:53 ` Damien Le Moal [this message]
[not found] ` <556511649635338@mail.yandex.com>
2022-04-12 6:28 ` Zheyu Ma
2022-04-12 6:34 ` Zheyu Ma
2022-04-13 3:42 ` Damien Le Moal
2022-04-20 2:21 ` Zheyu Ma
2022-04-20 3:04 ` Damien Le Moal
2022-04-20 12:15 ` Zheyu Ma
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=05433153-0424-ab66-1573-993d0490c5bc@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=zheyuma97@gmail.com \
/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
all inboxes | Powered by JetHome®