https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #70 from secan (secancri...@gmail.com) ---
Yes, but you see, we who have the Dell Poweredge T40, which is not a laptop and
we do not use any usb-c device plugged in, we still receive the error message.
Since we have opened this
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #69 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #68)
> I'm still trying to understand if these errors have any impact, or instead
> are just cosmetical
At boot time where no dock is attached,
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #68 from secan (secancri...@gmail.com) ---
I'm still trying to understand if these errors have any impact, or instead are
just cosmetical
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #67 from John Darrah (xyl...@gmail.com) ---
On Fri, 2023-06-23 at 03:46 -0700, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #66 from secan (secancri...@gmail.com) ---
> So,
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #66 from secan (secancri...@gmail.com) ---
So, any of you guys, have tried kernel 6.1.x. Is the error still present?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #65 from John Darrah (xyl...@gmail.com) ---
On Mon, 2022-12-12 at 07:39 -0800, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #64 from Andy Shevchenko
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #64 from Andy Shevchenko (andy.shevche...@gmail.com) ---
An additional information from affected machines:
https://www.reddit.com/r/Dell/comments/ii5oqd/dell_t40_acpi_error/
Not sure if it's helpful for USB Type-C case.
We have now
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #63 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to John Darrah from comment #62)
> Created attachment 31 [details]
> dmesg for 5.15.0-2-amd64 / Debian
It seems it lacks of any additional debug prints added into
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #62 from John Darrah (xyl...@gmail.com) ---
Created attachment 31
--> https://bugzilla.kernel.org/attachment.cgi?id=31=edit
dmesg for 5.15.0-2-amd64 / Debian
Here is a dmesg from a newer kernel:
Linux nyx 5.15.0-2-amd64 #1
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #61 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to Paul Menzel from comment #60)
> Reading my original post again, the USB-C adapter Dell DA200 was inserted
> after boot (90 s).
Yeah, there are two cases when it
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #60 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
Reading my original post again, the USB-C adapter Dell DA200 was inserted after
boot (90 s).
--
You may reply to this email to add a comment.
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #59 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to Andy Shevchenko from comment #58)
> (In reply to Paul Menzel from comment #57)
> > Well, then Linux does have a design problem, doesn’t it?
>
> You may
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #58 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to Paul Menzel from comment #57)
> Well, then Linux does have a design problem, doesn’t it?
You may put it this way, of course...
> At least the log messages for the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #57 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
Well, then Linux does have a design problem, doesn’t it?
At least the log messages for the handler could be reworked, so no error level
message is reported.
--
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #56 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to Paul Menzel from comment #55)
> So the I²C host controller driver needs to be loaded earlier then?
It's not possible (feasible).
--
You may reply to this email
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #55 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
So the I²C host controller driver needs to be loaded earlier then?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #54 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to Paul Menzel from comment #53)
> Isn’t this a design problem, Linux’ ACPI subsystem (or the firmware) should
> address?
>
> > acpi_mask_gpe= [HW,ACPI]
> >
https://bugzilla.kernel.org/show_bug.cgi?id=203529
Andy Shevchenko (andy.shevche...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #53 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
Isn’t this a design problem, Linux’ ACPI subsystem (or the firmware) should
address?
> acpi_mask_gpe= [HW,ACPI]
> Due to the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #52 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #51)
> It did work by adding acpi_mask_gpe=0x20, no more error messages related to
> acpi.
>
> Now, my question still stands, as "is/are the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #51 from secan (secancri...@gmail.com) ---
It did work by adding acpi_mask_gpe=0x20, no more error messages related to
acpi.
Now, my question still stands, as "is/are the device/s recognized and fully
functional"?
--
You may reply
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #50 from secan (secancri...@gmail.com) ---
Hello Andy,
So, you say that everything is working as it should, just that due to the boot
order, acpi kicks that error? I've tried to boot with acpi_mask_gpe=511 but
dmesg kicks me the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #49 from Andy Shevchenko (andy.shevche...@gmail.com) ---
Thanks!
Now, you see there:
[0.480354] ACPI: Enabled 11 GPEs in block 00 to 7F
[0.480493] ACPI Error: No handler for Region [WST1] (dfea9681)
[GenericSerialBus]
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #48 from secan (secancri...@gmail.com) ---
Created attachment 297589
--> https://bugzilla.kernel.org/attachment.cgi?id=297589=edit
dmesg1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #47 from secan (secancri...@gmail.com) ---
Hello Andy,
I've managed to reconpile the server with the patch that you've provided me. I
also switched distros from RHEL to Fedora 34 (to have a more recent kernel).
The behaviour is the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #46 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #44)
> Hello Andy,
>
> As requested, I've added the kernel boot flags, and attached the "dmesg"
> output.
Okay, in your case device seems to be
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #45 from secan (secancri...@gmail.com) ---
Created attachment 297577
--> https://bugzilla.kernel.org/attachment.cgi?id=297577=edit
dmesg log
--
You may reply to this email to add a comment.
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #44 from secan (secancri...@gmail.com) ---
Hello Andy,
As requested, I've added the kernel boot flags, and attached the "dmesg"
output.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #43 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #42)
> So this is what I did. Due to the fact that Redhat is very peculiar when it
> comes to patching, I went the kpatch way (the method that RH
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #42 from secan (secancri...@gmail.com) ---
Hello Andy,
So this is what I did. Due to the fact that Redhat is very peculiar when it
comes to patching, I went the kpatch way (the method that RH recommends).
Unfortunately the patch
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #41 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #40)
> I would definetly do that, it's just that this is above my skills level.
> Andy can you please instruct me how to do that? If I use kernel
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #40 from secan (secancri...@gmail.com) ---
I would definetly do that, it's just that this is above my skills level. Andy
can you please instruct me how to do that? If I use kernel 4.18 is it doable?
John Darrah, could you test the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #39 from Andy Shevchenko (andy.shevche...@gmail.com) ---
Created attachment 297409
--> https://bugzilla.kernel.org/attachment.cgi?id=297409=edit
Debug patch for I²C ACPI handler
Please, try to build kernel with the attached patch
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #38 from John Darrah (xyl...@gmail.com) ---
On Wed, 2021-06-16 at 00:13 -0700, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #32 from Zhang Rui (rui.zh...@intel.com)
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #37 from John Darrah (xyl...@gmail.com) ---
On Wed, 2021-06-16 at 00:13 -0700, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #32 from Zhang Rui (rui.zh...@intel.com)
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #36 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to Zhang Rui from comment #31)
> Hi, Andy,
> I'm not quite familiar with how IC2 controller/devices are enumerated.
>
> But for the current problem,
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #35 from secan (secancri...@gmail.com) ---
ll /sys/bus/acpi/devices/device:81/
total 0
drwxr-xr-x. 3 root root0 Jun 14 05:23 INT3515:00
drwxr-xr-x. 3 root root0 Jun 14 05:23 MAX34407:00
drwxr-xr-x. 3 root root0 Jun 14
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #34 from secan (secancri...@gmail.com) ---
Hello Zhang,
As requested, here's the output:
grep . /sys/bus/acpi/devices/*/path | grep I2C0
/sys/bus/acpi/devices/device:81/path:\_SB_.PCI0.I2C0
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #33 from Zhang Rui (rui.zh...@intel.com) ---
*** Bug 213323 has been marked as a duplicate of this bug. ***
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #32 from Zhang Rui (rui.zh...@intel.com) ---
John and secan,
please run "grep . /sys/bus/acpi/devices/*/path | grep I2C0", to find out which
acpi device is the _SB.PCI0.I2C0 device. Say, if it is
/sys/bus/acpi/devices/device:80, and
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #31 from Zhang Rui (rui.zh...@intel.com) ---
Hi, Andy,
I'm not quite familiar with how IC2 controller/devices are enumerated.
But for the current problem,
OperationRegion (WST1) is located under _SB.PCI0.I2C0, but all the
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #30 from secan (secancri...@gmail.com) ---
But my guess is that the device is not enumerated at all:
[root@vHost ~]# find /* | grep -i int34b2
[root@vHost ~]#
BR,
Cristian
--
You may reply to this email to add a comment.
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #29 from secan (secancri...@gmail.com) ---
Hello,
here's my output too:
/sys/bus/pci/devices/:00:15.0/firmware_node/INT3515:00/path:\_SB_.PCI0.I2C0.UCMX
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #28 from John Darrah (xyl...@gmail.com) ---
On Mon, 2021-06-14 at 20:05 -0700, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #27 from Zhang Rui (rui.zh...@intel.com)
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #27 from Zhang Rui (rui.zh...@intel.com) ---
If ((SMD0 != One))
{
Name (_HID, "INT34B2") // _HID: Hardware ID
Method (_HRV, 0, NotSerialized) // _HRV: Hardware Revision
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #26 from secan (secancri...@gmail.com) ---
(In reply to Paul Menzel from comment #25)
> (In reply to secan from comment #21)
> > RHEL 8.4
>
> I am never used RHEL. The guide on LinuxConfig.org [1] documents it for
> Fedora.
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #25 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to secan from comment #21)
> RHEL 8.4
I am never used RHEL. The guide on LinuxConfig.org [1] documents it for Fedora.
Basically, clone the Linux source
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #24 from secan (secancri...@gmail.com) ---
Here you go mister:
[root@vHost ~]# grep . /sys/bus/acpi/devices/INT34*/status
/sys/bus/acpi/devices/INT340E:00/status:15
/sys/bus/acpi/devices/INT3420:00/status:0
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #23 from Zhang Rui (rui.zh...@intel.com) ---
Device (I2C0)
Name (_HID, "INT34B2") // _HID: Hardware ID
So the _STA of INT34B2 device does not return 15.
please attach the output of
grep .
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #22 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #19)
> Hello,
>
> I'm willing and available to test the patch, just please show me (instruct
> me) how? :-)
If you are talking about patch from
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #21 from secan (secancri...@gmail.com) ---
RHEL 8.4
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #20 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to secan from comment #19)
> I'm willing and available to test the patch, just please show me (instruct
> me) how? :-)
What distribution do you use?
--
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #19 from secan (secancri...@gmail.com) ---
Hello,
I'm willing and available to test the patch, just please show me (instruct me)
how? :-)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #18 from Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) ---
(In reply to Zhang Rui from comment #17)
> Plus, the ACPI Errors are gone with Andy's patch, right?
That’s from comment 12.
> @secan, @ John Darrah @Paul Menzel
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #17 from Zhang Rui (rui.zh...@intel.com) ---
Plus, the ACPI Errors are gone with Andy's patch, right?
@secan, @ John Darrah @Paul Menzel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #16 from Zhang Rui (rui.zh...@intel.com) ---
(In reply to Andy Shevchenko from comment #14)
> (In reply to John Darrah from comment #13)
> > On Fri, 2021-06-04 at 07:57 -0700, bugzilla-dae...@bugzilla.kernel.org
> > wrote:
>
> ...
>
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #15 from secan (secancri...@gmail.com) ---
Hello,
Same output on Dell PowerEdge T40:
[root@vHost ~]# grep -H 15 /sys/bus/acpi/devices/*/status
/sys/bus/acpi/devices/ACPI000C:00/status:15
/sys/bus/acpi/devices/INT0E0C:00/status:15
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #14 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to John Darrah from comment #13)
> On Fri, 2021-06-04 at 07:57 -0700, bugzilla-dae...@bugzilla.kernel.org
> wrote:
...
> > (Usually we run `grep -H 15
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #13 from John Darrah (xyl...@gmail.com) ---
On Fri, 2021-06-04 at 07:57 -0700, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> Andy Shevchenko (andy.shevche...@gmail.com) changed:
>
https://bugzilla.kernel.org/show_bug.cgi?id=203529
Andy Shevchenko (andy.shevche...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #11 from John Darrah (xyl...@gmail.com) ---
On Wed, 2021-06-02 at 20:47 -0700, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=203529
>
> --- Comment #8 from Zhang Rui (rui.zh...@intel.com)
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #10 from secan (secancri...@gmail.com) ---
@Zhang, as you've suggested, I've opened a new bug report with the requested
output and acpidump:
https://bugzilla.kernel.org/show_bug.cgi?id=213323
--
You may reply to this email to add a
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #9 from Zhang Rui (rui.zh...@intel.com) ---
@secan, as you have a different model, please file a separate bug and attach
the acpidump.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #8 from Zhang Rui (rui.zh...@intel.com) ---
The
OperationRegion (WST1, GenericSerialBus, 0x1000, 0x0100)
is under I2C0 device.
Device (I2C0)
{
If ((SMD0 != One))
{
Name (_HID,
https://bugzilla.kernel.org/show_bug.cgi?id=203529
John Darrah (xyl...@gmail.com) changed:
What|Removed |Added
CC||xyl...@gmail.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #6 from secan (secancri...@gmail.com) ---
P.S. The issue is not encountered in Centos 7.x (kernel 3.10.x)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203529
secan (secancri...@gmail.com) changed:
What|Removed |Added
CC||secancri...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=203529
Zhang Rui (rui.zh...@intel.com) changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=203529
Zhang Rui (rui.zh...@intel.com) changed:
What|Removed |Added
CC||rui.zh...@intel.com
69 matches
Mail list logo
