[Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work

[Barry Bulls]

I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working, but the USB 3.0 port does. They appear in lspci and lsusb, but devices connected to them do not work. For example, a flash drive w/ a LED on it lights up and mounts on the 3.0 port but doesn't even light up on the 2.0 ports. There are no messages in dmesg when something is plugged into the 2.0 port. This behavior is the same on ubuntu 12.10 and 13.04.

---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
CasperVersion: 1.331
DistroRelease: Ubuntu 13.04
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Sony Corporation SVT15112CXS
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/13/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1110D4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnInsydeCorp.:bvrR1110D4:bd03/13/2012:svnSonyCorporation:pnSVT15112CXS:pvrC904W34T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVT15112CXS
dmi.product.version: C904W34T
dmi.sys.vendor: Sony Corporation

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1172908/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1172908

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Barry Bulls (bullsbarry)]

apport information

[Sergio Torres (sergiotorresperez)]

This is also happening to me. I've tried Ubuntu, Debian testing, Mageia2, and OpenSuse with the exact same results.
My output of lsusb and lspci is the same as for Barry Bulls, so I'm not uploading it again.

Cheers.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

[Jorge Rivera (gio107)]

I have tested using 3.9.0-030900rc8-generic and it still has the bug.

My computer is a Vaio T Series SVT13125CXS

[Barry Bulls (bullsbarry)]

My computer is the Vaio T Series SVT15112CXS, so this seems like it's potentially a problem across the series.

[Barry Bulls (bullsbarry)]

I just attempted to use the latest 13.10 nightly build and still the same result, no USB 2.0 ports.

[Barry Bulls (bullsbarry)]

What else needs to be done in order to get someone to review this bug?

[Ming Lei (tom-leiming)]

Hi,

Could you provide 'dmesg' just after your plug your usb mass storage
device into the 2.0 port?

Also could you try to plug other devices(hub, uvc camera, ...) into the 2.0
port to see if it works?

From the 'lsusb' log, there are many devices found in the 2.0 bus, so it
is a bit confused that you think the 2.0 port doesn't work.

Thanks,

[Rodrigo (rodealmeida)]

Just confirming that this bug is also affecting me.
Laptop is: Sony SVT13125CGS

[Barry Bulls (bullsbarry)]

Here's the relevant lsusb and dmesg outputs. I'm using a M-Audio FastTrack audio interface. As you can see, the interface is recognized and shows up in lsusb and dmesg when plugged into the USB3.0 port, but is not when plugged into the USB2.0 ports.

BEFORE

ubuntu@ubuntu:~$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:002d Elan Microelectronics Corp.
Bus 001 Device 006: ID 0489:e036 Foxconn / Hon Hai
Bus 001 Device 005: ID 05ca:18c4 Ricoh Co., Ltd

USB 3.0
ubuntu@ubuntu:~$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 0763:2024 Midiman M-Audio Fast Track MKII
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:002d Elan Microelectronics Corp.
Bus 001 Device 006: ID 0489:e036 Foxconn / Hon Hai
Bus 001 Device 005: ID 05ca:18c4 Ricoh Co., Ltd

ubuntu@ubuntu:~$ dmesg
[ 317.613413] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 318.037335] usb 3-1: New USB device found, idVendor=0763, idProduct=2024
[ 318.037346] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 318.037351] usb 3-1: Product: Fast Track
[ 318.037356] usb 3-1: Manufacturer: M-Audio
[ 320.666728] usbcore: registered new interface driver snd-usb-audio

USB2.0
ubuntu@ubuntu:~$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:002d Elan Microelectronics Corp.
Bus 001 Device 006: ID 0489:e036 Foxconn / Hon Hai
Bus 001 Device 005: ID 05ca:18c4 Ricoh Co., Ltd

ubuntu@ubuntu:~$ dmesg
[ 384.022264] usb 3-1: USB disconnect, device number 2

[Sergio Alonso (zerjio)]

Just to confirm that this bug is also affecting me.

[Ming Lei (tom-leiming)]

On Wed, Jun 5, 2013 at 8:42 AM, Barry Bulls <email address hidden> wrote:
>
> ubuntu@ubuntu:~$ dmesg
> [ 384.022264] usb 3-1: USB disconnect, device number 2

Why aren't you so generous to post more logs of 'dmesg' under USB 2.0 case?

Thanks,
--
Ming Lei

[Barry Bulls (bullsbarry)]

The process I went through was to log in and wait until everything was loaded, ran dmesg to verify that it was the same (except for timestamps) as in the original bug report, then cleared it. Then i did the before/after on the USB 3.0 port, then cleared the log, then attached the device to the usb2.0 ports. That single line is the only thing in dmesg and it's the message about disconnecting the device from that port. There are no messages when the device is plugged into the USB2.0 ports. They just don't work at all. However, they work fine under Windows.

[jorge (xxopxe)]

Y confirm the post #31. Plugging and unplugging a pendrive in the USB2 port shows nothing in dmesg. The same pendrive works correctly on the USB3 port.
The same with a wireless mouse, other two pendrives, and two different webcams.

[Ming Lei (tom-leiming)]

On Tue, Jun 11, 2013 at 12:44 AM, Barry Bulls
<email address hidden> wrote:
> The process I went through was to log in and wait until everything was
> loaded, ran dmesg to verify that it was the same (except for timestamps)
> as in the original bug report, then cleared it. Then i did the
> before/after on the USB 3.0 port, then cleared the log, then attached
> the device to the usb2.0 ports. That single line is the only thing in
> dmesg and it's the message about disconnecting the device from that
> port. There are no messages when the device is plugged into the USB2.0
> ports. They just don't work at all. However, they work fine under
> Windows.

Sorry, it is hard to guess what is issue without any 'dmesg' log.

Thanks,
--
Ming Lei

[Barry Bulls (bullsbarry)]

That is the issue. Nothing happens when you plug devices into the USB 2 ports. No changes in the dmesg logs, no change in lsusb output. Nothing. The full dmesg log is attached to the bug.

[ATIpro (somebody2112)]

+1. Nothing happens when you plug devices into the USB 2 port.

I've tried to check if there is any low level activity like usb interrupts or packet transmissions, and found nothing. Port is definitely powered. In preinstalled win8 this port worked fine, and in uefi bios it works too. Problem starts only during kernel boot process. May be usb controller initialization problem? I've checked latest stable kernel 3.9.6, problem is still there. Can you provide list with the information which will be useful to track the issue?

P.S. I've got Sony Vaio SVT1112S1 laptop.

[Ming Lei (tom-leiming)]

Hi Barry and ATIpro,

Could you plug the devices into USB 2.0 port first and run below command
to see if your devices can be found in USB 2.0 bus?

find /sys/bus/usb/devices/*/port*/power/control | while read LINE; do
echo on > ${LINE}; done

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

I've tried that, but it doesn't help. I don't think, that it is a power issue. I have one usb device, which lights one led after being plugged to not working port, but it doesn't light another led after enumeration is completed as it should. It looks like kernel doesn't get an event about apperance of new device.

[Ming Lei (tom-leiming)]

On Sun, Jun 16, 2013 at 11:32 PM, ATIpro <email address hidden> wrote:
> I've tried that, but it doesn't help. I don't think, that it is a power
> issue. I have one usb device, which lights one led after being plugged
> to not working port, but it doesn't light another led after enumeration
> is completed as it should. It looks like kernel doesn't get an event
> about apperance of new device.

AFAIK, no kernel event after plugging device should be caused by

- no power from port which may be cut off after port runtime PM introduced
or
- ehci root hub doesn't work

If you are sure there is no any ehci interrupts(/proc/interrupts)(see #35)
after plugging the device, I guess that there is no power from the port. And
you can connect your cell phone to the port and check if it is capable of
becoming in charging state.

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

Cell phone is charging from this port. It's really hard to say something about events looking at /proc/interrupts. Where should I look?

$ lsusb
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 0489:e036 Foxconn / Hon Hai
Bus 003 Device 004: ID 04f2:b328 Chicony Electronics Co., Ltd

$ ls /sys/bus/usb/devices
1-0:1.0 3-0:1.0 3-1:1.0 3-1.2:1.0 3-1.3 3-1.3:1.1 4-1 usb1 usb3
2-0:1.0 3-1 3-1.2 3-1.2:1.1 3-1.3:1.0 4-0:1.0 4-1:1.0 usb2 usb4

$ cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 19 0 0 0 IO-APIC-edge timer
  1: 40 864 18 11 IO-APIC-edge i8042
  8: 1 0 0 0 IO-APIC-edge rtc0
  9: 16 62 2 8 IO-APIC-fasteoi acpi
 12: 129 1094 66 98 IO-APIC-edge i8042
 16: 2609 24268 1351 1329 IO-APIC-fasteoi ehci_hcd:usb3, ath9k
 23: 13 16 2 6 IO-APIC-fasteoi ehci_hcd:usb4
 40: 2105 50057 1369 1311 PCI-MSI-edge i915
 41: 20 3 0 10 PCI-MSI-edge rtsx_pci
 42: 278 262 167 72 PCI-MSI-edge xhci_hcd
 43: 4562 4693 1233 1701 PCI-MSI-edge ahci
 44: 11 3 0 1 PCI-MSI-edge mei
 45: 105 112 34 34 PCI-MSI-edge snd_hda_intel
 46: 0 0 0 0 PCI-MSI-edge eth0
NMI: 13 16 16 11 Non-maskable interrupts
LOC: 34609 27442 37060 23151 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 13 16 16 11 Performance monitoring interrupts
IWI: 0 0 0 0 IRQ work interrupts
RTR: 2 0 0 0 APIC ICR read retries
RES: 11820 4299 1362 914 Rescheduling interrupts
CAL: 43 47 53 47 Function call interrupts
TLB: 324 236 657 478 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 5 5 5 5 Machine check polls
ERR: 0
MIS: ...

[Ming Lei (tom-leiming)]

On Mon, Jun 17, 2013 at 2:23 PM, ATIpro <email address hidden> wrote:
> Cell phone is charging from this port. It's really hard to say something
> about events looking at /proc/interrupts. Where should I look?
>
> $ lsusb
> Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

> Bus 003 Device 005: ID 0489:e036 Foxconn / Hon Hai
> Bus 003 Device 004: ID 04f2:b328 Chicony Electronics Co., Ltd

The above two devices are attached on USB 2.0 bus, and they have
been recognized well, don't they?

>
> $ ls /sys/bus/usb/devices
> 1-0:1.0 3-0:1.0 3-1:1.0 3-1.2:1.0 3-1.3 3-1.3:1.1 4-1 usb1 usb3
> 2-0:1.0 3-1 3-1.2 3-1.2:1.1 3-1.3:1.0 4-0:1.0 4-1:1.0 usb2 usb4
>
> $ cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3
> 0: 19 0 0 0 IO-APIC-edge timer
> 1: 40 864 18 11 IO-APIC-edge i8042
> 8: 1 0 0 0 IO-APIC-edge rtc0
> 9: 16 62 2 8 IO-APIC-fasteoi acpi
> 12: 129 1094 66 98 IO-APIC-edge i8042
> 16: 2609 24268 1351 1329 IO-APIC-fasteoi ehci_hcd:usb3, ath9k
> 23: 13 16 2 6 IO-APIC-fasteoi ehci_hcd:usb4

There are interrupts from two USB 2.0 buses, and you may try 'rmmod ath9k'
to see if new devices can be recognized on usb3.

Or if you can build kernel by yourself, you can enable 'CONFIG_USB_DEBUG'
& 'CONFIG_DEBUG_DRIVER' and post out 'dmesg' info. If you can't, I'd like to
build one kernel with these debug options for your test.

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

> The above two devices are attached on USB 2.0 bus, and they have
been recognized well, don't they?

Yes, it's internal hardware(bluetooth module and uvc camera). They are working.

> and you may try 'rmmod ath9k' to see if new devices can be recognized on usb3.

I've tried that. But it doesn't help. I see, that there are interrupts on ehci_hcd:usb3 during bluetooth activity. I also see, that numers in line ehci_hcd:usb4 are not changing at all.

> Or if you can build kernel by yourself, you can enable 'CONFIG_USB_DEBUG'
& 'CONFIG_DEBUG_DRIVER' and post out 'dmesg' info.

I'll try to do that, but it will take some time.

[ATIpro (somebody2112)]

For now I have Arch Linux for test in dualboot and have built latest kernel there. Since this issue is distribution independent I hope this won't be a big problem.

[ivan@vaio ~]$ zcat /proc/config.gz | grep CONFIG_USB_DEBUG
CONFIG_USB_DEBUG=y
[ivan@vaio ~]$ zcat /proc/config.gz | grep CONFIG_DEBUG_DRIVER
CONFIG_DEBUG_DRIVER=y

After boot I've plugged usb 2.0 flash drive to working usb 3.0 port, then removed it. After that I've plugged there usb 3.0 flash drive and removed it. Here is full dmesg. Still no noticeable activity on external usb 2.0 port.

[jorge (xxopxe)]

Just in case, I confirm the charging behaviour. I plugged a MP3 player to the USB2 port and it started charging, but there is nothing in dmesg.

[Ming Lei (tom-leiming)]

Hi ATIpro,

On Tue, Jun 18, 2013 at 1:27 AM, ATIpro <email address hidden> wrote:
> For now I have Arch Linux for test in dualboot and have built latest
> kernel there. Since this issue is distribution independent I hope this
> won't be a big problem.
>
> [ivan@vaio ~]$ zcat /proc/config.gz | grep CONFIG_USB_DEBUG
> CONFIG_USB_DEBUG=y
> [ivan@vaio ~]$ zcat /proc/config.gz | grep CONFIG_DEBUG_DRIVER
> CONFIG_DEBUG_DRIVER=y
>
> After boot I've plugged usb 2.0 flash drive to working usb 3.0 port,
> then removed it. After that I've plugged there usb 3.0 flash drive and
> removed it. Here is full dmesg. Still no noticeable activity on external
> usb 2.0 port.

The 'dmesg' is very clear, but looks still no bad things found, we
can see USB1/USB4 are USB2.0 bus, and built-in devices are
recognized in USB1 bus, but I am not sure the external USB 2.0 ports
belong to which bus(1 or 4).

Could you do the below tests so that we can see if USB4 bus can be
wakeup? If not, the problem should be that something is wrong with
port routing setting.

- plug one device into USB 2.0 port

- run the below scripts and post out the 'dmesg' info:

#!/bin/sh
find /sys/bus/usb/devices/*/power/control | while read LINE; do
echo on > ${LINE}; done

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

> run the below scripts and post out the 'dmesg' info

here you go

[Ming Lei (tom-leiming)]

On Tue, Jun 18, 2013 at 6:08 PM, ATIpro <email address hidden> wrote:
>> run the below scripts and post out the 'dmesg' info
>
> here you go

The 2.0 bus can be waken up but still can't find external devices connected,
so looks like some x86 specific setting disables the two ports.

I have no idea on the bug, and reported it on linux-usb list already.

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

> I have no idea on the bug, and reported it on linux-usb list already.

This issue exist in Debian 6 with kernel 2.6.32. I haven't tested older kernels, but I can do that if it helps.
Bios (UEFI) of this laptop is very limited in terms of configuration, there is no usb configuration at all. This problem exists both in legacy and native uefi modes.
During bios initialization this port works. So I can plug there flash drive with live linux distribution and successfully see GRUB/Syslinux/etc from it. But during running initramfs LED on flash drive stops glowing and after timeout I see Busybox line with error about missing root partition.

[Ming Lei (tom-leiming)]

On Thu, Jun 20, 2013 at 4:10 AM, ATIpro <email address hidden> wrote:
>> I have no idea on the bug, and reported it on linux-usb list already.
>
> This issue exist in Debian 6 with kernel 2.6.32. I haven't tested older kernels, but I can do that if it helps.
> Bios (UEFI) of this laptop is very limited in terms of configuration, there is no usb configuration at all. This problem exists both in legacy and native uefi modes.
> During bios initialization this port works. So I can plug there flash drive with live linux distribution and successfully see GRUB/Syslinux/etc from it. But during running initramfs LED on flash drive stops glowing and after timeout I see Busybox line with error about missing root partition.

Yes, upstream guy thought it might be caused by BIOS, see

     http://marc.info/?t=137160415400003&r=1&w=2

Could you try to upgrade to a newer BIOS version?

Or have you done the tests below?

- plug one 2.0 devices to 2.0 port, then power on machine to see
if they can be found in 2.0 bus

If not, I suggest you to give it a try.

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

At the moment I don't have preinstalled windows. Without it I don't see any way to upgrade bios, because I can't find any downloadable firmware updates.
Sony's consumer support answered that they support only windows. If usb port works there everything is fine and they are not interested in fixing linux issues.

[ATIpro (somebody2112)]

I've installed windows and updated bios.

So, before upgrade it was
> [ 0.000000] DMI: Sony Corporation SVT1112S1RS/VAIO, BIOS R0140D4 08/23/2012
and now
> [ 0.000000] DMI: Sony Corporation SVT1112S1RS/VAIO, BIOS R0150D4 03/13/2013

But really nothing changed. Port still don't work.

I've also checked that this port works fine in pure windows 7 without any Sony drivers. So it's not a wired hardware issue, it's a bug in linux kernel. I'll try to test other operating systems like freebsd, may be port will work there.

[ATIpro (somebody2112)]

This port works fine in PC-BSD. Here is dmesg from there.

[Ming Lei (tom-leiming)]

Hi ATIpro,

Below is suggestion from upstream linux-usb list:

> It could also be that the BIOS is completely ignoring the writes to the
> port registers as well. Can the reporters recompile with
> CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING turned on?
> That will tell me which ports are being switched over.

Could you do the test and post the log in LP?

Thanks,
--
Ming Lei

[ATIpro (somebody2112)]

> Could you do the test and post the log in LP?

I've rebuilt kernel with CONFIG_DEBUG_DRIVER, CONFIG_USB_DEBUG and CONFIG_USB_XHCI_HCD_DEBUGGING. Just boot information is enough, or I need to make some extra actions to make dmesg more informative?

[Ryan Linnane (ryanflinnane)]

I have the same issues and results over here with my sony T series (running fedora). I've been banging my head against a wall for hours.

When plugged into the WORKING 3.0 port, the device is shown as being on the same bus # as the 2.0 port. Could it be a problem with the controller?

[Barry Bulls (bullsbarry)]

I'm not sure it would be an issue with the controller itself, as everything "Just Works" on Windows.

[Chris Puckett (9e9o1ko8b2f5xpiibgscjzlh-18kvw-0zxvj9hhx1hzo5xiyhxz186c)]

I am having the same issue. The device works fine in the USB 3.0 port but does not on the 2.0 ports.
It has and LED that is active for a few seconds when first plugged in to the 2.0 port then it just goes off.

This works fine when booted to Windows 8

[Chris Horne (chorne-s)]

Same problem on my SVT13122CXS/VAIO Ultrabook.
Using Linux Mint 15/Raring/Wheezy
Dmesg doesn't even have a clue that something is there, but will charge a cellphone.. So I pretty much have nothing more than a 5 volt port on my laptop :(

[Barry Bulls (bullsbarry)]

The thread on the linux-usb list seems to have gone cold on this, is there any other communication with upstream on this bug?

[penalvch (penalvch)]

Barry Bulls, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[FlashBuster (flashbuster)]

Hi folks,

a friend has the exact same issue and this issue persists also with the latest linux mainline PPA version 3.11.rc3 amd64.

Please help fixing this..

Cheers

[penalvch (penalvch)]

FlashBuster, if your friend has a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like them to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[FlashBuster (flashbuster)]

Well, anyway, this bug was reproduced on the latest kernel from the mainline PPA...

[salva84 (salva-ms)]

any news on this? is also happening to me...

[penalvch (penalvch)]

salva84, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[salva84 (salva-ms)]

Thank you Christoffer,

this is what I get with that command on mint 15

mint@mint ~ $ ubuntu-bug linux

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
................................

*** Problem in linux-image-3.8.0-19-generic

The problem cannot be reported:

This is not an official LinuxMint package. Please remove any third party package and try again.

Press any key to continue...

No pending crash reports. Try --help for more information.
mint@mint ~ $

Anyway I saw this error happens on all distributions in Vaio T13 and no solution has been proposed.... :(

[Barry Bulls (bullsbarry)]

I'm unable to test this as I no longer am running Ubuntu natively on this machine but in a virtual machine, which works perfectly. I would still prefer to use Ubuntu as the host, so it would be great if this bug could be tracked down and fixed. It seems there are many people experiencing the same issue.

[penalvch (penalvch)]

Barry Bulls, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/66 regarding you not being able to test this anymore. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Barry Bulls (bullsbarry)]

This is ridiculous. There are a half dozen people on this issue who
are able to reproduce and test, but you're going to close it because I
can't test further?

On Aug 9, 2013, at 7:41 PM, "Christopher M. Penalver"
<email address hidden> wrote:

> Barry Bulls, this bug report is being closed due to your last comment
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/66
> regarding you not being able to test this anymore. For future reference
> you can manage the status of your own bugs by clicking on the current
> status in the yellow line and then choosing a new status in the revealed
> drop down box. You can learn more about bug statuses at
> https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
> to report this bug and helping to make Ubuntu better. Please submit any
> future bugs you may find.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172908
>
> Title:
> [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
>
> Status in “linux” package in Ubuntu:
> Invalid
>
> Bug description:
> I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working,
> but the USB 3.0 port does. They appear in lspci and lsusb, but devices
> connected to them do not work. For example, a flash drive w/ a LED on
> it lights up and mounts on the 3.0 port but doesn't even light up on
> the 2.0 ports. There are no messages in dmesg when something is
> plugged into the 2.0 port. This behavior is the same on ubuntu 12.10
> and 13.04.
>
>
> ---
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
> CasperVersion: 1.331
> DistroRelease: Ubuntu 13.04
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MachineType: Sony Corporation SVT15112CXS
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
> RelatedPackageVersions:
> linux-restricted-modules-3.8.0-19-generic N/A
> linux-backports-modules-3.8.0-19-generic N/A
> linux-firmware 1.106
> Tags: raring
> Uname: Linux 3.8.0-19-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> dmi.bios.date: 03/13/2012
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: R1110D4
> dmi.board.asset.tag: N/A
> dmi.board.name: VAIO
> dmi.board.vendor: Sony Corporation
> dmi.board.version: N/A
> dmi.chassis.asset.tag: N/A
> dmi.chassis.type: 10
> dmi.chassis.vendor: Sony Corporation
> dmi.chassis.version: N/A
> dmi.modalias: dmi:bvnInsydeCorp.:bvrR1110D4:bd03/13/2012:svnSonyCorporation:pnSVT15112CXS:pvrC904W34T:rvnSonyCorpora...

[Phil Wyett (u-k-i-t)]

This bug is absolutely valid and should not be closed or invalidated as it affects many and is easily cross referenced to the same isssue in another distro.

[ATIpro (somebody2112)]

> This is ridiculous.

+1. This report contains many information about a bug and many people having this issue are subscribed to it. There is no reason to open another one.

[penalvch (penalvch)]

Phil Wyatt / ATIpro, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[FlashBuster (flashbuster)]

Why would you deliberately make this whole process a pain in the a** for us Ubuntu users and force people to create duplicate bugs?! I've never seen a bugtracker where people are actively encouraged to create duplicate bugs.
Is there somewhere a guideline to read after the reason for that, atleast? Just actively invalidating the bug without telling the reason is kind of strange... Why is this bugreport invalid?
The bug says "I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working". Obviously EVERY owner of this laptop and obviously it's some bug in the kernel USB system, is it not?
Then again, how likely is it that Canonical fixes a Kernel bug.. might as well install Fedora. RedHat atleast has a reputation for kernel development.

[Phil Wyett (u-k-i-t)]

Re: #71

Fine. Someone please report this bug as specified by the post I reference above.

We'll see about discussing this type of bug invalidation maybe with the community council.

[Dariusz Duraj (dariusz-duraj)]

I can confirm this bug on a Sony Vaio T13 Ultrabook.
I tested Ubuntu 13.04 and Opensuse 12.3
Windows 7 and 8 are fine.

[penalvch (penalvch)]

Dariusz Duraj, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Barry Bulls (bullsbarry)]

So what you're saying is that they all need to open duplicate reports
since I can no longer work on the issue, even though they can?

On Aug 10, 2013, at 9:25 AM, "Christopher M. Penalver"
<email address hidden> wrote:

> Dariusz Duraj, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
> ubuntu-bug linux
>
> For more on this, please see the Ubuntu Kernel team article:
> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
>
> the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
> https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
>
> and Ubuntu Community article:
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
>
> When opening up the new report, please feel free to subscribe me to it.
>
> Please note, not filing a new report would delay your problem being
> addressed as quickly as possible.
>
> Thank you for your understanding.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172908
>
> Title:
> [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
>
> Status in The Linux Kernel:
> Invalid
> Status in “linux” package in Ubuntu:
> Invalid
>
> Bug description:
> I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working,
> but the USB 3.0 port does. They appear in lspci and lsusb, but devices
> connected to them do not work. For example, a flash drive w/ a LED on
> it lights up and mounts on the 3.0 port but doesn't even light up on
> the 2.0 ports. There are no messages in dmesg when something is
> plugged into the 2.0 port. This behavior is the same on ubuntu 12.10
> and 13.04.
>
>
> ---
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
> CasperVersion: 1.331
> DistroRelease: Ubuntu 13.04
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MachineType: Sony Corporation SVT15112CXS
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
> RelatedPackageVersions:
> linux-restricted-modules-3.8.0-19-generic N/A
> linux-backports-modules-3.8.0-19-generic N/A
> linux-firmware 1.106
> Tags: raring
> Uname: Linux 3.8.0-19-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> dmi.bios.date: 03/13/2012
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: R1110D4
> dmi.board.asset.tag: N/A
> dmi.board.name: VAIO
> dmi.board.vendor: Sony Corporation
> dmi.board.version: N/A
> dmi.chassis.asset.tag: N/A
> dmi.chassis.type:...

[Dariusz Duraj (dariusz-duraj)]

Hallo Christopher,

you are right-it is not Ubuntu`s job to fix Kernel issues!

best regards!

dariusz

[Claudio Moretti (flyingstar16)]

The bug is still confirmed, as different users have reported it and comfirmed they are experiencing it.

Leaving "Invalid" on the Linux project, as bugs are tracked through the "linux" package in Ubuntu.

Dariusz Duraj, it does not matter. The kernel still has a bug, and here's the right place to file the bug report. Also, the kernel is not the "vanilla" from kernel.org, it's beed modified and compiled on the Ubuntu project servers, so it may be a problem related to that.

[penalvch (penalvch)]

Claudio Moretti, that is not how it works. As previously documented in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/75 , among others, one would need to file a new report. If you have any further questions, you may contact me directly, the Ubuntu Kernel Team, and/or the Ubuntu Bug Control team.

Thank you for your understanding.

[Barry Bulls (bullsbarry)]

Can you explain how it works then? This is a big that has been
confirmed to be affecting many people. Are you saying they all need to
file separate bug report in order for this to get any attention? I was
under the impression that it was better to have one issue for the same
bug rather than many issues duplicating it. If you're saying that I
have to break my primary work environment in order for this issue to
be resolved at an unknown time in the future, then maybe this isn't
the distribution for me.

On Aug 10, 2013, at 12:55 PM, "Christopher M. Penalver"
<email address hidden> wrote:

> Claudio Moretti, that is not how it works. As previously documented in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/75
> , among others, one would need to file a new report. If you have any
> further questions, you may contact me directly, the Ubuntu Kernel Team,
> and/or the Ubuntu Bug Control team.
>
> Thank you for your understanding.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172908
>
> Title:
> [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
>
> Status in The Linux Kernel:
> Invalid
> Status in “linux” package in Ubuntu:
> Invalid
>
> Bug description:
> I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working,
> but the USB 3.0 port does. They appear in lspci and lsusb, but devices
> connected to them do not work. For example, a flash drive w/ a LED on
> it lights up and mounts on the 3.0 port but doesn't even light up on
> the 2.0 ports. There are no messages in dmesg when something is
> plugged into the 2.0 port. This behavior is the same on ubuntu 12.10
> and 13.04.
>
>
> ---
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
> CasperVersion: 1.331
> DistroRelease: Ubuntu 13.04
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MachineType: Sony Corporation SVT15112CXS
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
> RelatedPackageVersions:
> linux-restricted-modules-3.8.0-19-generic N/A
> linux-backports-modules-3.8.0-19-generic N/A
> linux-firmware 1.106
> Tags: raring
> Uname: Linux 3.8.0-19-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> dmi.bios.date: 03/13/2012
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: R1110D4
> dmi.board.asset.tag: N/A
> dmi.board.name: VAIO
> dmi.board.vendor: Sony Corporation
> dmi.board.version: N/A
> dmi.chassis.asset.tag: N/A
> dmi.chassis.type: 10
> dmi.chassis.vendor: Sony Cor...

[Claudio Moretti (flyingstar16)]

Christopher M. Penalver, not to be insistent, but I am part of the BugSquad and so far nobody said anything about closing a bug just because one of the affected users is not able to reproduce it.

The issue IS reproducible; if not by the original reporter, by 9 other people that have marked this bug as "it affects me".

If nobody comes forward to provide information related to this bug, after 60 days the bug will be automatically marked as "Invalid", but not before.

Nearly all the commenters are against closing this bug; what you are asking them to do is overflow Launchpad with duplicate bug reports: this would lead to a massive invalidation due to bug duplication and to extreme complications in handling the bug, because of infinite copies of the bug report in the system.

This is how it works; please, do not change the status again.

[Barry Bulls (bullsbarry)]

I'm seriously interested. Do I need to break my laptop in order for this bug to be valid?

[Combat (combatb2)]

I have added another bug report (Bug #1210858) - but this is essentially the same issue!

[penalvch (penalvch)]

Barry Bulls, still Invalid as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/67 . Please feel free to provide the information previously requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/59 and then change this to Status Confirmed.

Thank you for your understanding.

[Barry Bulls (bullsbarry)]

What if one of the many others affected by this bug are able to
provide the information requested? It just seems foolish to have them
open new bugs for the same issue.

On Aug 10, 2013, at 4:50 PM, "Christopher M. Penalver"
<email address hidden> wrote:

> Barry Bulls, still Invalid as per
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/67
> . Please feel free to provide the information previously requested of
> you in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908/comments/59
> and then change this to Status Confirmed.
>
> Thank you for your understanding.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172908
>
> Title:
> [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
>
> Status in The Linux Kernel:
> Invalid
> Status in “linux” package in Ubuntu:
> Invalid
>
> Bug description:
> I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working,
> but the USB 3.0 port does. They appear in lspci and lsusb, but devices
> connected to them do not work. For example, a flash drive w/ a LED on
> it lights up and mounts on the 3.0 port but doesn't even light up on
> the 2.0 ports. There are no messages in dmesg when something is
> plugged into the 2.0 port. This behavior is the same on ubuntu 12.10
> and 13.04.
>
>
> ---
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
> CasperVersion: 1.331
> DistroRelease: Ubuntu 13.04
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MachineType: Sony Corporation SVT15112CXS
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
> RelatedPackageVersions:
> linux-restricted-modules-3.8.0-19-generic N/A
> linux-backports-modules-3.8.0-19-generic N/A
> linux-firmware 1.106
> Tags: raring
> Uname: Linux 3.8.0-19-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> dmi.bios.date: 03/13/2012
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: R1110D4
> dmi.board.asset.tag: N/A
> dmi.board.name: VAIO
> dmi.board.vendor: Sony Corporation
> dmi.board.version: N/A
> dmi.chassis.asset.tag: N/A
> dmi.chassis.type: 10
> dmi.chassis.vendor: Sony Corporation
> dmi.chassis.version: N/A
> dmi.modalias: dmi:bvnInsydeCorp.:bvrR1110D4:bd03/13/2012:svnSonyCorporation:pnSVT15112CXS:pvrC904W34T:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
> dmi.product.name: SVT15112CXS
> dmi.product.version: C904W34T
> dmi.sys.vendor: Sony Corporation
>
> To manage notifications about this bug go to:
...

[Brian Murray (brian-murray)]

While Christopher has not said it in this bug report, kernel bugs are frequently hardware specific and while it may seem that everyone has the same hardware this is is difficult to tell without getting detailed information about the hardware from each user experiencing the bug report. The easiest way to get this detailed information is to have each individual report a separate bug report using 'ubuntu-bug linux' from their system. Then it is easier to ensure that each bug is fixed, by examining the hardware of each system affected, by whatever fix is found.

[Barry Bulls (bullsbarry)]

If we could've gotten this explanation at the beginning of the conversation
this wouldn't have been nearly as frustrating of an experience. However, I
would point out that in this case the laptops are all in the same series
and the hardware appears to differ only in the details of screen size and
number of physical ports. The annoying thing for some users, I'm sure, is
that while I'm relatively lucky in that my 15 inch notebook has 3 usb
ports, one of which works, there are smaller versions of the same notebook
that do not have any usb 3 ports, so none of them work.

On Mon, Aug 12, 2013 at 3:02 PM, Brian Murray <email address hidden> wrote:

> While Christopher has not said it in this bug report, kernel bugs are
> frequently hardware specific and while it may seem that everyone has the
> same hardware this is is difficult to tell without getting detailed
> information about the hardware from each user experiencing the bug
> report. The easiest way to get this detailed information is to have
> each individual report a separate bug report using 'ubuntu-bug linux'
> from their system. Then it is easier to ensure that each bug is fixed,
> by examining the hardware of each system affected, by whatever fix is
> found.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172908
>
> Title:
> [Vaio T Series SVT15112CXS] USB 2.0 Ports Don't Work
>
> Status in The Linux Kernel:
> Invalid
> Status in “linux” package in Ubuntu:
> Invalid
>
> Bug description:
> I have a Sony Vaio T-Series laptop. The usb 2.0 ports are not working,
> but the USB 3.0 port does. They appear in lspci and lsusb, but devices
> connected to them do not work. For example, a flash drive w/ a LED on
> it lights up and mounts on the 3.0 port but doesn't even light up on
> the 2.0 ports. There are no messages in dmesg when something is
> plugged into the 2.0 port. This behavior is the same on ubuntu 12.10
> and 13.04.
>
>
> ---
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3244 F.... pulseaudio
> CasperVersion: 1.331
> DistroRelease: Ubuntu 13.04
> LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
> MachineType: Sony Corporation SVT15112CXS
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/username.seed boot=casper quiet splash --
> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
> RelatedPackageVersions:
> linux-restricted-modules-3.8.0-19-generic N/A
> linux-backports-modules-3.8.0-19-generic N/A
> linux-firmware 1.106
> Tags: raring
> Uname: Linux 3.8.0-19-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> dmi.bios.date: 03/13/2012
> dmi.bios.vendor: Insyde Corp.
>...

[Chris Puckett (9e9o1ko8b2f5xpiibgscjzlh-18kvw-0zxvj9hhx1hzo5xiyhxz186c)]

This is happening with my Tseries model no SVT151A11L

What can I provide that may help?

[Barry Bulls (bullsbarry)]

Unfortunately this bug has been marked as invalid because I'm no longer running Ubuntu on my laptop (as it's my primary workstation and can't deal with these issues), but am now running it in a VM. However, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210858 is still valid and is a duplicate of this issue.

[penalvch (penalvch)]

Chris Puckett, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[penalvch (penalvch)]

Barry Bulls, as far as Launchpad is concerned, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210858 is not a duplicate as this bug report is Invalid.

[Mauricio Edgardo Arévalo Ruiz (ed-arevalo-ruiz)]

I'm having the same problem in my desktop, I'm using a GIGABYTE GA-970A-D3 motherboard, usb 3.0 working but not usb 2.0, I only have 2 3.0 usb ports, only enough to use my keyboard and mouse. I'm being forced to use windows because under windows all ports work fine, but it seems Ubuntu team does not even have idea of what is going on with this bug, since you can see the lack of interest from the team to fix it. Maybe someone here has tried another Linux based operating system that works, I would like to try it

[penalvch (penalvch)]

Mauricio Edgardo Arévalo Ruiz, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Mauricio Edgardo Arévalo Ruiz (ed-arevalo-ruiz)]

Sorry, I'm being forced to use windows, since I only have 2 working ports which are only enough to use my keyboard and mouse , Ubuntu is useless to me right now, until the bug is fixed I will not install Ubuntu

[Mauricio Edgardo Arévalo Ruiz (ed-arevalo-ruiz)]

Hello, I fix this problem in my desktop, I use an AMD Processor and I found that Enabling the option IOMMU, all ports work fine, For those who have a BIOS with that option try to enable it

[jorge (xxopxe)]

Just a heads-up, this bug was opened again:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1316897

and it was sent upstream to linux-people:

http://thread.gmane.org/gmane.linux.usb.general/108173

[penalvch (penalvch)]

jorge, no this bug was not opened again as this is a different model Sony VAIO. Bugs are not lumped together in a dog pile by symptom, but on a per specific hardware model, per symptom, and per reporter basis. As this bug is closed, no further comments are helpful here.

[jorge (xxopxe)]

Ok, it was just a note to people that may beinterested here, or arrived to this bug report from google.

Sorry for using the "bug was opened again", did not mean bug as defined in your launchpad's database schema. As we users use the word "bug", this is the same bug.