From: Jiang Liu <liuj97@gmail.com>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: Jiang Liu <jiang.liu@huawei.com>,
alexdeucher@gmail.com, "Rafael J . Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yijing Wang <wangyijing@huawei.com>,
linux-acpi@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUGFIX v2 0/4] fix bug 56531, 59501 and 59581
Date: Mon, 17 Jun 2013 01:33:57 +0800 [thread overview]
Message-ID: <51BDF705.5090904@gmail.com> (raw)
In-Reply-To: <CAN_LGv1itN=ADE-3LNCoBJFXmpWZffhQb6NQuoBzvONkX3brug@mail.gmail.com>
On 06/15/2013 02:42 PM, Alexander E. Patrakov wrote:
> 2013/6/15 Jiang Liu <jiang.liu@huawei.com>:
>> Alexander E. Patrakov <patrakov@gmail.com> reports two bugs related to
>> dock station support on Sony VAIO VPCZ23A4R. Actually there are at least
>> four bugs related to Sony VAIO VPCZ23A4R dock support.
>> 1) can't correctly detect hotplug slot for dock state
>> 2) resource leak on undocking
>> 3) resource allocation failure for dock devices
>> 4) one bug in intel_snd_hda driver
> 5) one or two bugs in radeon driver
>
> As for the subject - only a hotplug-related part of bug 59581 is fixed.
>
>> Hi Alexander, could you please help to test the whole patchset?
>> Really get sleepy, it's already 3 oclock now, so please forgive me
>> if there any stupid mistakes.
>
> I have tested this patchset on top of 3.10-rc5 using the following two
> testcases.
>
> 1. Boot docked with radeon blacklisted. Switch to text-based virtual
> console, undock, dock, modprobe radeon, rmmod radeon, undock, dock,
> modprobe radeon again. Tested in this sequence because Alex Deucher
> told me in bug 59681 to rmmod radeon before undocking.
>
> 2. Boot undocked, with radeon not blacklisted. Stay in X. Dock,
> undock, dock, undock, dock.
>
> Both cases work, and exhibit similar backtraces in dmesg. So I am
> attaching a dmesg only from the first testcase. Please look for "INFO:
> trying to register non-static key" and for "*ERROR* Memory manager not
> clean. Delaying takedown". I understand that the second trace is
> unrelated to this patchset, but would like you to fix the first.
Hi Alexander,
Great thanks for your testing!
I have investigated the first issue but still have no idea about it.
According to source code, everything should be OK.
The r8169 driver has invoked INIT_WORK(&tp->wk.work, rtl_task) to
initialize the work item, so it shouldn't trigger the warning.
Have you found this issue in other test cases?
Regards!
Gerry
>
> Note that the snd_hda_intel bug somehow didn't manifest itself today,
> probably because the TV that is connected to the HDMI output of the
> radeon card was off and because Xorg never really tried to use the
> card.
>
> --
> Alexander E. Patrakov
>
next prev parent reply other threads:[~2013-06-16 17:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 19:27 [BUGFIX v2 0/4] fix bug 56531, 59501 and 59581 Jiang Liu
2013-06-14 19:27 ` [BUGFIX v2 1/4] ACPI, DOCK: initialize dock subsystem before scanning PCI root buses Jiang Liu
2013-06-15 6:51 ` Yinghai Lu
2013-06-15 10:05 ` Jiang Liu
2013-06-15 20:03 ` Rafael J. Wysocki
2013-06-14 19:27 ` [BUGFIX v2 2/4] ACPI, DOCK: resolve possible deadlock scenarios Jiang Liu
2013-06-14 22:21 ` Rafael J. Wysocki
2013-06-15 1:44 ` Jiang Liu
2013-06-15 20:17 ` Rafael J. Wysocki
2013-06-15 21:20 ` Rafael J. Wysocki
2013-06-15 22:54 ` Rafael J. Wysocki
2013-06-16 17:12 ` Jiang Liu
2013-06-17 11:40 ` Rafael J. Wysocki
2013-06-18 16:03 ` Jiang Liu
2013-06-18 21:25 ` Rafael J. Wysocki
2013-06-16 17:01 ` Jiang Liu
2013-06-17 11:39 ` Rafael J. Wysocki
2013-06-17 12:54 ` Rafael J. Wysocki
2013-06-18 15:36 ` Jiang Liu
2013-06-18 21:12 ` Rafael J. Wysocki
2013-06-16 16:27 ` Jiang Liu
2013-06-14 19:28 ` [BUGFIX v2 3/4] PCI, ACPI: fix device destroying order issue when handling dock notification Jiang Liu
2013-06-15 6:50 ` Yinghai Lu
2013-06-14 19:28 ` [BUGFIX v2 4/4] ACPIPHP: fix bug 56531 Sony VAIO VPCZ23A4R: can't assign mem/io after docking Jiang Liu
2013-06-14 21:03 ` Yinghai Lu
2013-06-17 11:57 ` Rafael J. Wysocki
2013-06-15 6:42 ` [BUGFIX v2 0/4] fix bug 56531, 59501 and 59581 Alexander E. Patrakov
2013-06-15 7:25 ` Alexander E. Patrakov
2013-06-18 21:35 ` Rafael J. Wysocki
2013-06-19 5:18 ` Alexander E. Patrakov
2013-06-20 19:06 ` Rafael J. Wysocki
2013-06-21 4:36 ` Alexander E. Patrakov
2013-06-21 4:37 ` Alexander E. Patrakov
2013-06-21 13:06 ` Rafael J. Wysocki
2013-06-21 12:47 ` Rafael J. Wysocki
2013-06-21 13:02 ` Alexander E. Patrakov
2013-06-21 16:54 ` Jiang Liu
2013-06-22 0:13 ` Rafael J. Wysocki
2013-06-22 2:47 ` Jiang Liu
2013-06-22 19:59 ` Rafael J. Wysocki
2013-06-23 15:57 ` Jiang Liu
2013-06-23 21:51 ` Rafael J. Wysocki
2013-06-23 21:52 ` Rafael J. Wysocki
2013-06-16 17:33 ` Jiang Liu [this message]
2013-06-17 3:27 ` Alexander E. Patrakov
2013-06-17 17:07 ` Alexander E. Patrakov
2013-06-18 15:13 ` Jiang Liu
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=51BDF705.5090904@gmail.com \
--to=liuj97@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiang.liu@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=patrakov@gmail.com \
--cc=rjw@sisk.pl \
--cc=wangyijing@huawei.com \
--cc=yinghai@kernel.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).