Vaio VGN-SZ3XWP docking station cant hot dock/undock.

Bug #163211 reported by Chris Scutcher on 2007-11-16
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Undecided
Unassigned

Bug Description

Just bought the Sony docking station for the Vaio VGN-SZ3XWP . The docking station contains a PCI-Express Yukon (using sky2 module) Gigabit Ethernet Card additional to the onboard Yukon Ethernet card and Wifi. When cold docking the card is detected fine and reverts back to normal when cold undocked. However when hotdocking the PCI card isn't detected.

Have tried to hack around the problem with the following method;
0) Start laptop undocked. Dock. lspci is missing dock network card, however scanpci finds it. Simple reloading the sky2 module doesn't detect card (as I assume its looking at the same thing as lspci)
1) load fakephp kernel module.
2) "echo 1 -n > /sys/bus/pci/slots/anyoledevice/power" to force PCI to rescan bus
3) lspci now displays docking station network card
4) sky2 module refuses to enable the PCI card complaining that;
PCI not enabled due to 0 resources collisions.
I figure this is probably due IRQ conflict, and /proc/pci reports that the docking station network card is on IRQ 0... which would obviously kick up a stink
5) I hit a proverbial brick wall at this point, as I cant seem to work out a way to change the IRQ for the card, except for hacking the driver, which I dont really feel qualified to do.

Hot undocking can result in a kernel panic if failing to rmmod sky2 first, but after undocking then redocking the dock network card fails to be detected (see above)

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I assume you are using the latest 7.10 Gutsy Gibbon release? I have classified this bug as a bug in linux-source-2.6.22.

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Chris Scutcher (chris-scutcher) wrote :

Yes I am using Gutsy Gibbon . 2.6.22-14-generic kernel.

Ill give your suggestion a shot this weekend and see what happens.

I'll let you know.

Cheers
Chris

Changed in linux-source-2.6.22:
status: New → Incomplete
S V N Vishwanathan (vishketan) wrote :

This bug seems to be related to https://bugs.launchpad.net/ubuntu/+bug/194617

Also, the Hardy Heron Alpha series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD rather than manually installing. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

S V N Vishwanathan (vishketan) wrote :

I tried with the latest release 8.04 alpha 5 and the bug still exists. Pls see Bug 194617 for details.

vishy

Chris Scutcher (chris-scutcher) wrote :

In latest release this bug seems to be partially fixed. Providing you don't bring the interface up it doesn't kernel panic, but if it comes up and you undock it... kernel panic

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Chris Scutcher (chris-scutcher) wrote :

Just tested using the Alpha 5 LiveCD. Was only a quick test (can't run the unstable version permanently at the moment) but the bug still exists.
Same as with the current release if the link is up and you undock... kernel panic! Shame

Hi,
The rc3 version of 2.6.27-1 solves the docking problem for me. The
distro is still hardy.
But the kernel comes with other problems... wireless doesn't work
after a suspend.

On Sun, Sep 7, 2008 at 11:48 AM, Chris Scutcher
<email address hidden> wrote:
> Just tested using the Alpha 5 LiveCD. Was only a quick test (can't run the unstable version permanently at the moment) but the bug still exists.
> Same as with the current release if the link is up and you undock... kernel panic! Shame
>
> --
> Vaio VGN-SZ3XWP docking station cant hot dock/undock.
> https://bugs.launchpad.net/bugs/163211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I'll give that a shot and see if it helps.

Duane Hinnen (duanedesign) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Aidan Fitzpatrick (afit) wrote :

Thanks duanedesign. This is still a problem for me with my Sony VGN-SZ3XWP in Sony docking station.

Jaunty 9.04, up to date as of today:

k@stumpy:~$ uname -ar
Linux stumpy 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009 i686 GNU/Linux

k@stumpy:~$ dpkg -l | grep kernel | grep 2.6.28-11
ii linux-headers-2.6.28-11 2.6.28-11.40 Header files related to Linux kernel version 2.6.28
ii linux-headers-2.6.28-11-generic 2.6.28-11.40 Linux kernel headers for version 2.6.28 on x86/x86_64
ii linux-image-2.6.28-11-generic 2.6.28-11.40 Linux kernel image for version 2.6.28 on x86/x86_64
ii linux-restricted-modules-2.6.28-11-generic 2.6.28-11.15 Non-free Linux kernel modules for version 2.6.28 on x86/x86_64

Where I refer to "undock script" below I mean this two-liner adapted from Chris' original bug report:
sudo modprobe acpiphp
sudo echo 0 > /sys/bus/pci/slot/4/power

Behaviour

1. Removing power from docking station, or pulling out laptop without undock preparation

Hard hang of laptop with flashing status lights requiring battery removal.

2. Pressing undock button on docking station, then removing laptop.

Hard hang of laptop with flashing status lights requiring battery removal.

3. Don't press undock button, run undock script, then removing laptop.

Wired networks disabled. Laptop undocks. When re-docked, running "sudo echo 1 > /sys/bus/pci/slot/4/power" seems to reenable wired network 50% of the time.

What happens if you press the undock button on the laptop?

The dock light will go off (yay!) and wireless will be immediately disabled (boo! why would I want to turn off wireless when undocking?). Wireless will not reenable when docked (ack, reboot required?). Nothing else seems to get turned off... and it doesn't alter affect scenarios 1 - 3.

The only way to undock the laptop is with the script I provided above, and re-docking is unreliable.

Aidan Fitzpatrick (afit) wrote :

FWIW it wasn't working for me in 8.10 prior to upgrade a fortnight ago, either.

Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 163211

Changed in linux-source-2.6.22 (Ubuntu):
status: Incomplete → Won't Fix
Duane Hinnen (duanedesign) wrote :

Aidan confirmed this issue still exists with Jaunty. Therefore I changed the Status to New.

Thank you Aidan for updating this bug with new information.

Changed in linux (Ubuntu):
status: Incomplete → New
Sergio Zanchetta (primes2h) wrote :

Aidan didn't test the final release of Jaunty.
It would be helpful if you could test it and confirm if this issue remains.
Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 163211

Changed in linux (Ubuntu):
status: New → Incomplete
Sergio Zanchetta (primes2h) wrote :

To be clear, Jaunty was released on 23th of April.

Aidan Fitzpatrick (afit) wrote :

Sergio, thanks for your comments.

I have just tried the laptop again in scenario #2 with the release 9.04 as described, and it appeared to undock and redock without incident. I don't have the time to work through each of the scenarios at the moment, but I will get back to this bug when I do.

I'll leave it as "incomplete", but would be interested to hear from others with this equipment.

Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers