IMHO this bug is valid.
# Steps to reproduce
As root:
apt-get purge nvidia-driver-418 # or any other version
apt-get install clang
update-alternatives --set cc /usr/bin/clang
apt install nvidia-driver-418
insmod /lib/modules/4.15.0-46-generic/updates/dkms/nvidia.ko # adjust for your
kernel
I have followed instructions on https://askubuntu.com/questions/161862
/nec-upd720200-usb-3-0-not-working-on-ubuntu-12-04 . Firmware update did
not change anything: board is recognized, but plugging a device has no
effect, no log in dmesg, nothing. lsusb -t reports no device attached.
--
You
TL;DR: This bug still happens Ubuntu 18.04.
No Windows here so not tried Windows.
lspci | grep -i upd
03:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host
Controller (rev 03)
Have tried to plug in two USB3 hard disks, one mouse. At all times,
lsusb -t shows controller but
@penalvch thank you for your comment. In theory it might indeed be a different
problem.
I practice I cannot test is myself again at the moment, and the information
given by @pereze seems convincing enough, as far as I understand.
@pereze, you wrote:
> Can reproduce it and upload any bug, log
@pereze Thank you for reporting.
> What is needed to change the status from: incomplete to: confirmed?
AFAIK, what is needed is to answer question in comment 26 by @penalvch,
which was:
> gouri, the latest mainline kernel is 4.3-rc6. Is this what you tested
with?
According t
Public bug reported:
# Observed
Package installation failed.
Pop-up appears to offer reporting bug to Ubuntu, as I've done a number of times
before.
# Action: check package file
Checked and redownloaded. File /var/cache/apt/archives/linux-
headers-4.4.0-31_4.4.0-31.50_all.deb was corrupted.
Hello Christopher.
Here's the reference of the kernel that booted yesterday using Xubuntu
live image:
Linux version 4.2.0-16-generic (buildd@lcy01-07) (gcc version 5.2.1
20151003 (Ubuntu 5.2.1-21ubuntu2) ) #19-Ubuntu SMP Thu Oct 8 15:35:06
UTC 2015 (Ubuntu 4.2.0-16.19-generic 4.2.3)
The aim of
Summary: behavior is different in Wily, sometimes not working, sometimes
working but fails on heavy traffic.
Done some test check booting a Asus n551 on Ubuntu 15.10 live (wily
werewolf).
## First test : one-way link only?
First (sanity check / scientific control), tested integrated Ethernet
Thanks William for your comment.
Reading activity following your links, there seems to be differences:
* launchpad (here): problem starts immediately, not on receiving heavy traffic.
Adapter unusable in practice on USB3 (not even for moderate activity), always
ok on USB2. Also, machine feels a
@pawel.jasinski I observed same behavior and independently arrived to
the same conclusion.
I suspend by pressing [fn]-[f1], then close the lid and pick up the
laptop. Then on the other site I resume it from suspend.
Case 1 : If the lid was closed immediately after pressing the key combo,
Oh, I forgot. The laptop involved in previous comment is Asus n55sf.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1287587
Title:
[ASUSTeK Computer Inc. K53SD] suspend/resume failure
Summary: (1) bug also occurs on Trusty 14.04 (2) we need you (yes, you,
affected by the bug) to help cure it
## Bug reproduced on Trusty
Just tested the same hardware again on kernel 3.13.0-30-generic
#55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64
GNU/Linux.
Same behavior as
Hello Christopher,
Thank you for your interest.
gouri, did this problem not occur in a release prior to Saucy?
Short answer: yes, from quantal.
But that too short answer hides important information.
Long answer:
Before Saucy (13.10), the machine ran 12.10 (quantal).
There was not this exact
Hello Joseph,
## Mainline kernel: tested from Saucy, inconclusive so far
I tested mainline 3.15.0-031500rc5-generic for about 2 days.
On that kernel, the machine ran hot due to nVidia optimus chip not
turned off by bumblebee.
The problem did not appear, but it does not prove that it's fixed as
Public bug reported:
# Summary
On an Asus n55sf laptop running 64-bit Ubuntu, USB ports gradually fail
more and more until none of them works.
# Expected
* USB devices work at all times.
* Plugging optical mouse shows light under the mouse, the mouse works.
* Plugging USB memory, hard drive,
* Check BIOS version. Reference
http://www.asus.com/Notebooks_Ultrabooks/N55SF/HelpDesk_Download/
BIOS used is version 207, already the latest available from
manufacturer. Nothing to do here.
* Test with latest upstream kernel as per the sentence Would it be
possible for you to test the latest
Posted to linux-usb list with cc to Freddy Xin (who introduced the
driver to the list).
URL of upstream thread :
http://thread.gmane.org/gmane.linux.usb.general/102382
Driver appears to have been introduced on January 2013 in that thread:
http://thread.gmane.org/gmane.linux.kernel/1420310
--
Could you please report this problem through the appropriate channel by
following the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Thank you for your understanding.
Thank you Christopher for your feedback.
I've read the instructions, they are clear and I'm
Hello Christopher,
1) Could you please plug your ASIX device in, execute the following in a
terminal and post it to this report:
usb-devices
Please see attached file
usb-devices_output_with_0b95_1790_ASIX_Electronics_Corp_USB2_port.txt
Currently, other than the device, only a mouse is
Kernel log. All 8 attempts were on one of the USB3 port on the left, not
on any of the USB2 ports on the right, notice the first worked with
mention:
Jan 22 13:02:50 n55sf-l kernel: [ 152.219714] usb 3-2: new high-speed
USB device number 2 using xhci_hcd
which indicates USB2 speed not USB3.
gouri, thank you for providing the requested information. Could you
please test the latest mainline kernel (not 3.12-rc7) via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ and advise
if this is reproducible?
Hello again Christopher,
* Short answer
Reproduced with 3.13.0 from URL
Hello @jsalisbury,
Thank you for your reply.
For old releases I booted old versions of Ubuntu that I used before upgrading
to 13.10 and are still lying
For new kernel, I followed your link and used URL
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc7-saucy/
Here's the summary of my
Oops, finger slip caused posting too early.
On upstream kernel 3.12.0-031200rc7-generic #201310271935 bug **still
occurs** with same characteristics including probability of happening on
any test (about 75% probability).
12.10 kernel was
Linux version 3.5.0-42-generic (buildd@lamiak) (gcc
According to https://launchpad.net/ax88179 the driver is in mainline
kernel since 3.9 which explains why older Ubuntu releases did not
recognize the device.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
dmesg of one attempt
** Attachment added: dmesg of one attempt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269883/+attachment/3950209/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: dmesg of another attempt, also reproducing the bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269883/+attachment/3950210/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Still happens on 3.5.0-41-generic.
I have recently observed a variant (and the symptoms are active now on the
laptop I'm writing with).
When bug happens, plugging a device on one of the two USB3 ports powers the
device but Linux does not detect anything (nothing in dmesg).
Plugging the same
Also, I don't use or have any USB3 devices.
I do use USB2 devices (external hard drive enclosures, Samsung Galaxy Nexus)
and USB 1.1 devices (mouse) -- checked with lsusb -v and bcdUSB field.
So to summarize :
* the tested crash scenario is plugging a USB2 device in a USB*3* port
* the tested
28 matches
Mail list logo
