Bug 106681
Summary: | Apple Thunderbolt Ethernet Adapter not Working After Suspend & Resume | ||
---|---|---|---|
Product: | Drivers | Reporter: | Christian Schwarz (me) |
Component: | HotPlug | Assignee: | Greg Kroah-Hartman (greg) |
Status: | NEW --- | ||
Severity: | normal | CC: | hujq, kostas, me, mike |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 4.3.0-rc7 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
The kernel configuration file of my system.
lspci -k output before suspending the system (as in "Steps to Reproduce") lspci -k output after resuming the system (as in "Steps to Reproduce") Log output after normal working plugin and unplug (reference) lspci -k output after resuming the system (as in "Steps to Reproduce") Log output after resuming as in "Steps to Reproduce" Log output of what happens after resuming as in "Workaround 2" |
Description
Christian Schwarz
2015-10-27 10:23:03 UTC
Created attachment 191231 [details]
lspci -k output before suspending the system (as in "Steps to Reproduce")
Created attachment 191241 [details]
lspci -k output after resuming the system (as in "Steps to Reproduce")
Created attachment 191251 [details]
Log output after normal working plugin and unplug (reference)
Created attachment 191261 [details]
lspci -k output after resuming the system (as in "Steps to Reproduce")
Created attachment 191271 [details]
Log output after resuming as in "Steps to Reproduce"
Created attachment 191281 [details]
Log output of what happens after resuming as in "Workaround 2"
The two workaround logs have been merged into one. Sorry for the flood of attachments: this is my first bug report and I could not find an option to add multiple attachments before initial submission. On Tue, Oct 27, 2015 at 10:23:03AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=106681 > > Bug ID: 106681 > Summary: Apple Thunderbolt Ethernet Adapter not Working After > Suspend & Resume Can you send all of this information to the netdev@vger.kernel.org mailing list so the network driver developers can help you out with this? thanks, greg k-h (In reply to Greg Kroah-Hartman from comment #8) > Can you send all of this information to the netdev@vger.kernel.org > mailing list so the network driver developers can help you out with > this? Should I send them a link to this bug or create an e-mail containing the entire bug description + attachments? Can't this bug be moved to the netdev section if this is more appropriate? Thanks for your patience! On Wed, Oct 28, 2015 at 12:36:15AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=106681 > > --- Comment #9 from me@cschwarz.com --- > (In reply to Greg Kroah-Hartman from comment #8) > > Can you send all of this information to the netdev@vger.kernel.org > > mailing list so the network driver developers can help you out with > > this? > > Should I send them a link to this bug or create an e-mail containing the > entire > bug description + attachments? An email please. > Can't this bug be moved to the netdev section if this is more appropriate? The network developers (and most driver subsystems), do not use bugzilla, they use the mailing list instead. thanks, greg k-h |