From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: update to 5.15.16
Date: Tue, 25 Jan 2022 19:14:31 +0100 [thread overview]
Message-ID: <20220125181431.JDnvURVmQ9OujqfcppvVgZkC9IObQ10veA9Tcheq2TE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/35216#issuecomment-1021472983
Comment:
```
[ 8.378770] sysfs: cannot create duplicate filename '/devices/platform/ff3d0000.i2c/i2c-4/4-0022/typec/port0/port0.0/partner'
[ 8.378792] CPU: 2 PID: 523 Comm: 4-0022 Not tainted 5.15.16_1 #1
[ 8.378800] Hardware name: Pine64 Pinebook Pro (DT)
[ 8.378805] Call trace:
[ 8.378807] dump_backtrace+0x0/0x1e0
[ 8.378824] show_stack+0x18/0x24
[ 8.378832] dump_stack_lvl+0x68/0x84
[ 8.378842] dump_stack+0x18/0x34
[ 8.378848] sysfs_warn_dup+0x60/0x7c
[ 8.378858] sysfs_do_create_link_sd+0x13c/0x14c
[ 8.378865] sysfs_create_link+0x24/0x4c
[ 8.378872] typec_probe+0x98/0x12c
[ 8.378881] call_driver_probe+0x2c/0x140
[ 8.378892] really_probe+0xb4/0x370
[ 8.378899] __driver_probe_device+0xf8/0x120
[ 8.378906] driver_probe_device+0x40/0x100
[ 8.378914] __device_attach_driver+0x98/0x130
[ 8.378919] bus_for_each_drv+0x78/0xd0
[ 8.378926] __device_attach+0xdc/0x1c0
[ 8.378934] device_initial_probe+0x14/0x20
[ 8.378939] bus_probe_device+0x98/0xa0
[ 8.378946] device_add+0x320/0x4f4
[ 8.378952] device_register+0x20/0x30
[ 8.378959] typec_register_altmode+0x1e8/0x350
[ 8.378966] typec_partner_register_altmode+0x10/0x20
[ 8.378972] tcpm_pd_svdm+0x554/0x594
[ 8.378981] tcpm_handle_vdm_request+0x250/0x34c
[ 8.378988] tcpm_pd_data_request+0xb8/0x544
[ 8.378995] tcpm_pd_rx_handler+0xf4/0x110
[ 8.379000] kthread_worker_fn+0x118/0x260
[ 8.379007] kthread+0x108/0x110
[ 8.379012] ret_from_fork+0x10/0x20
[ 8.379058] typec_displayport port0-partner.1: failed to create symlinks
[ 8.379066] typec_displayport: probe of port0-partner.1 failed with error -17
```
Did you test dpaltmode? Tested with 2 docks/dongle and it does not seem to work at least for me.
Did not notice anything odd except these two issues.
next prev parent reply other threads:[~2022-01-25 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 2:11 [PR PATCH] " CameronNemo
2022-01-25 10:37 ` Johnnynator
2022-01-25 18:14 ` Johnnynator [this message]
2022-01-25 20:17 ` CameronNemo
2022-01-25 20:18 ` CameronNemo
2022-01-25 22:13 ` Johnnynator
2022-01-30 12:30 ` Johnnynator
2022-03-11 18:32 ` [PR PATCH] [Updated] " CameronNemo
2022-03-11 18:34 ` CameronNemo
2022-03-11 18:34 ` CameronNemo
2022-03-12 7:05 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.15.27 CameronNemo
2022-03-12 7:05 ` CameronNemo
2022-04-09 22:39 ` [PR PATCH] [Updated] pinebookpro-kernel: update to 5.15.28 CameronNemo
2022-04-10 1:20 ` CameronNemo
2022-04-10 3:23 ` pinebookpro-kernel: update to 5.15.33 CameronNemo
2022-04-13 23:32 ` [PR PATCH] [Updated] " CameronNemo
2022-04-13 23:44 ` pinebookpro-kernel: update to 5.15.34 CameronNemo
2022-04-13 23:44 ` CameronNemo
2022-05-09 19:36 ` [PR PATCH] [Updated] " CameronNemo
2022-05-09 21:40 ` [PR PATCH] [Merged]: pinebookpro-kernel: update to 5.15.38 paper42
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=20220125181431.JDnvURVmQ9OujqfcppvVgZkC9IObQ10veA9Tcheq2TE@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).