From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-block <linux-block@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, regressions@lists.linux.dev,
"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)"
<linux-ide@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: TI: X15 the connected SSD is not detected on Linux next 20221006 tag
Date: Thu, 13 Oct 2022 16:11:29 +0900 [thread overview]
Message-ID: <bf1b053d-ffa6-48ab-d2d2-d59ab21afc19@opensource.wdc.com> (raw)
In-Reply-To: <CA+G9fYvRXkjeO+yDEQxwJ8+GjSmwhZ7XHHAaVWAsxAaSngj5gg@mail.gmail.com>
On 2022/10/12 16:24, Naresh Kamboju wrote:
> On TI beagle board x15 the connected SSD is not detected on linux next
> 20221006 tag.
>
> + export STORAGE_DEV=/dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84
> + STORAGE_DEV=/dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84
> + test -n /dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84
> + echo y
> + mkfs.ext4 /dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84
> mke2fs 1.46.5 (30-Dec-2021)
> The file /dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84 does
> not exist and no size was specified.
> + lava-test-raise 'mkfs.ext4
> /dev/disk/by-id/ata-SanDisk_SSD_PLUS_120GB_190702A00D84 failed; job
> exit'
>
> Test log:
> - https://lkft.validation.linaro.org/scheduler/job/5634743#L2580
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> metadata:
> git_ref: master
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: 7da9fed0474b4cd46055dd92d55c42faf32c19ac
> git_describe: next-20221006
> kernel_version: 6.0.0
> kernel-config: https://builds.tuxbuild.com/2FkkkZ51ZYhBL1G8D69YX8Pkt5F/config
> build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/659754170
> artifact-location: https://builds.tuxbuild.com/2FkkkZ51ZYhBL1G8D69YX8Pkt5F
> toolchain: gcc-10
The kernel messages that are shown in the links above do not show any "libata
version 3.00 loaded." message nor any ata/ahci message that I can see. So I
think the eSATA adapter is not even being detected and libata/ahci driver not used.
Was this working before ? If yes, can you try with the following patches reverted ?
d3243965f24a ("ata: make PATA_PLATFORM selectable only for suitable architectures")
3ebe59a54111 ("ata: clean up how architectures enable PATA_PLATFORM and
PATA_OF_PLATFORM")
If reverting these patches restores the eSATA port on this board, then you need
to fix the defconfig for that board.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-10-13 7:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 7:24 Naresh Kamboju
2022-10-13 7:11 ` Damien Le Moal [this message]
2022-10-13 12:39 ` Naresh Kamboju
2022-10-13 22:07 ` Anders Roxell
2022-10-14 0:22 ` Damien Le Moal
2022-10-14 7:31 ` Arnd Bergmann
2022-10-14 7:53 ` Damien Le Moal
2022-10-14 9:22 ` Anders Roxell
2022-10-14 9:37 ` Arnd Bergmann
2022-10-14 9:47 ` Damien Le Moal
2022-10-14 14:06 ` Serge Semin
2022-10-17 7:43 ` Anders Roxell
2022-10-17 15:52 ` Serge Semin
2022-11-30 9:40 ` Naresh Kamboju
2022-11-30 10:03 ` Niklas Cassel
2022-12-01 11:48 ` Anders Roxell
2022-12-05 1:11 ` Serge Semin
2022-12-05 10:08 ` Arnd Bergmann
2022-12-05 13:24 ` Damien Le Moal
2022-12-06 8:46 ` Serge Semin
2022-12-06 9:12 ` Damien Le Moal
2022-12-06 21:04 ` Serge Semin
2022-12-01 13:02 ` TI: X15 the connected SSD is not detected on Linux next 20221006 tag #forregzbot Thorsten Leemhuis
2022-12-07 5:40 ` Thorsten Leemhuis
2022-10-14 13:38 ` TI: X15 the connected SSD is not detected on Linux next 20221006 tag Serge Semin
2022-10-14 13:36 ` Serge Semin
2022-10-14 0:17 ` Damien Le Moal
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=bf1b053d-ffa6-48ab-d2d2-d59ab21afc19@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lukas.bulwahn@gmail.com \
--cc=naresh.kamboju@linaro.org \
--cc=niklas.cassel@wdc.com \
--cc=regressions@lists.linux.dev \
/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®