[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
Just wanted to add here that I think I've found an even simpler workaround. It looks like passing pci=bios as a kernel parameter consistently allows the GPU to load, regardless of kernel version or power source. I haven't tested it a whole lot, but so far it has worked 100%. -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Triaged Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1120J7 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:bvnPhoenixTechnologiesLTD:bvrR1120J7:bd07/04/2007:svnSonyCorporation:pnVGN-FZ260E:pvrFC01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
It's been a while, but I've found the time to dig much deeper into this and familiarize myself with the kernel code some. Actually, I feel comfortable with the idea of directly contacting the appropriate mailing list now so this is more to keep the record up-to-date than a request for more triage. Anyways, after just walking through the kernel code, I first realized that the first sign of the bug (the 30ms gap) was occurring somewhere within the function pci_scan_child_bus (in drivers/pci/probe.c), between when it invokes the function pci_scan_slot (also in drivers/pci/probe.c) and the function pcibios_fixup_bus (in my case, under arch/x86/pci/common.c) From there, I began adding dev_info statements around function calls that would be executed in between, then looked between whichever 2 messages the gap occurred between to further narrow down the problem. After a few rounds of this, I found the delay consistently appearing within the function pcie_aspm_configure_common_clock (in drivers/pci/pcie/aspm.c) After a little research about what the PCIe common clock is about, it actually explains several aspects of this bug. Booting the computer from battery power would influence the power state of the device, which is what ASPM is all about. And it turns out the discrepancy of 24ms between a good boot and a bad boot is precisely the length of time the PCIe standard defines as a timeout for link training. Unfortunately, I don't know how, or even if, the two commits I found earlier directly tie into this. It seems there's a really weird race condition or resource fight going on. I'm not exactly sure how to fix the problem clearly either because just adding the overhead of dev_info statements to the function makes the bug go away (so I can technically fix the bug, but that's just a total hack). The one other little cliue I found was that the delay went away completely when I put dev_info statements in every possible branch of the function's logic. When I only added dev_info to the ifs corresponding to a problem though, a slight delay appeared (bumping the total time in the function to around 10ms), but still not enough for link training to timeout (so my GPU always loaded). I plan on mailing the list for the PCI subsystem of the kernel soon, but I'm stumped about how exactly to proceed so if you have any debugging suggestions, I'd be happy to hear them. Thanks again. -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Triaged Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion:
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
Hmm... so I've just finished a first set of tests with reverting that commit, and I definitely have results, though they aren't as cut-and-dry as I hoped. When I reverted the commit, there were merge conflicts in: drivers/acpi/scan.c drivers/dma/acpi-dma.c Since I really have no clue how these files work, I used git mergetool to try simple ways of resolving the conflicts. I tried completely reverting both files to the older version and leaving them as they are at the tip of the master branch. In both of those cases, the kernel failed to build, with make throwing an error when it reached the appropriate file, then completely stopping soon after with a [deb-pkg] error. What's interesting is that when I kept acpi/scan.c in its up-to- date form but entirely reverted /dma/acpi-dma.c, the kernel built successfully. Unfortunately, when I tried testing it, that kernel build froze during boot, and when I logged in with a stable kernel to check the dmesg logs, the bug was still there. I would need to actually take the plunge and spend a while learning how the code works before I could resolve the conflict more precisely. However, I noticed the build process created a debug package this time; is there some debug setting that I could enable that would shed light on anything? -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Incomplete Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
** Changed in: linux (Ubuntu) Status: Incomplete = Triaged -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Triaged Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1120J7 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:bvnPhoenixTechnologiesLTD:bvrR1120J7:bd07/04/2007:svnSonyCorporation:pnVGN-FZ260E:pvrFC01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ260E dmi.product.version: FC01 dmi.sys.vendor: Sony Corporation --- AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
Kyle Auble, thank you for your commit bisection work. One thing that would be helpful is if we just revert the noted commit in the latest mainline and see if it continues to occur via a terminal, reboot, and testing the new kernel: git config --global user.email y...@example.com git config --global user.name Your Name cd $HOME git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git revert ee8209fd026b074bb8eb75bece516a338a281b1b git add . git commit cp /boot/config-`uname -r` .config yes '' | make oldconfig make clean make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-customrevert cd .. sudo dpkg -i *.deb git fetch origin;git fetch origin master;git reset --hard FETCH_HEAD ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Incomplete Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
So after another couple of months, I've managed to do more testing, and I may have found something useful. First off, two fresh, stable versions of the Ubuntu kernel have shown the bug: v3.2.0-56 (64-bit) and v3.5.0-44 (32-bit). Also, the most recent package from the Ubuntu mainline kernel PPA, v3.13.0-rc3 (built Dec. 6), showed the bug and failed to boot. I confirmed the bug by looking at the old dmesg log after rebooting into a working kernel. On the positive side, after a little more free-time and thinking about the problem, I can give you a commit that may be canceling out the effect from Xiao Guangrong's earlier patch. Instead of using git-bisect, I narrowed down the problem to a small range from previous tests, then manually checked the merges in the mainline kernel's history. After tracing the regression to a simple merge, I rebased the short side branch leading to it onto the preceding, bug-free commit. I don't know if this method would give false results, but I figured since the merge itself involved no extra changes and the rebase didn't cause any conflicts, it should be useful. The patch where the bug reappeared for me was: ee8209fd026b074bb8eb75bece516a338a281b1b by Andy Shevchenko Hope this helps some, and let me know if there's anything else I could try. -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Confirmed Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
** Tags removed: kernel-request-3.11.0-7.14 ** Tags added: bot-stop-nagging ** Changed in: linux (Ubuntu) Status: Confirmed = Triaged -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Triaged Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1120J7 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:bvnPhoenixTechnologiesLTD:bvrR1120J7:bd07/04/2007:svnSonyCorporation:pnVGN-FZ260E:pvrFC01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ260E dmi.product.version: FC01 dmi.sys.vendor: Sony Corporation --- AcpiTables: Error: command ['pkexec',
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request. We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-request-3.11.0-7.14 -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Incomplete Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
I was a little confused about exactly which version of the kernel you wanted to test, but it's a moot point because all of the ones I tried had the bug still. I'm still using Ubuntu 12.04 so sudo apt-get dist-upgrade just keeps me on v3.5.0-40, which definitely has the bug. I also tested v3.11-rc1 (built 7/14) off of the Ubuntu Mainline PPA, v3.11-rc5 (it had the patch by Rafael Wysocki I mentioned previously), and v3.12-rc1 (the latest version). Every single one showed the bug, which I confirmed by checking the dmesg logs after booting up with a stable kernel. Actually, none of those three kernels even made it to the login screen. It's a little unnerving that whatever changes fixed the bug around May this year have been canceled out since then. Seeing the glass half-full though, once I have some free time, I can do a standard bisection to see where the fix was knocked out. That might give us a little more data to work with. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Confirmed Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A
[Kernel-packages] [Bug 1009312] Re: 10de:0426 GPU loads unreliably, possible kernel timeout
** Summary changed: - GPU loads unreliably, possible kernel timeout + 10de:0426 GPU loads unreliably, possible kernel timeout ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1009312 Title: 10de:0426 GPU loads unreliably, possible kernel timeout Status in “linux” package in Ubuntu: Confirmed Bug description: Reverse upstream kernel commit bisecting revealed a fix via commit d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong. WORKAROUND: If I boot my computer from battery power alone without AC, my GPU the Ubuntu splash screen load on startup. I've been running Ubuntu 12.04 for a few weeks now, I really like it, but from the beginning, I had the issue where the proprietary nvidia driver installs but fails to load (confirmed from the commandline, jockey, and the nvidia-dashboard). Over time, I've noticed that sometimes when I power on, the driver does load and I can enter a full unity session without problems, but other times, I fall back onto the VESA driver and a unity 2d session. On a whim, I finally copied logs from both successful and unsuccessful boots, cut out the times, ran a diff on them, and noticed a pattern in the kernel messages. I'm filing this bug after a successful boot so I've also attached copies of dmesg, Xorg, jockey logs from an unsuccessful boot. The first thing I saw in the logs was a timing discrepancy between the two boots, most of which is due to GPE storms. I've checked other logs and there's not a clear relation, I've had successful boots with them and unsuccessful ones without them. I do still wonder if they may be involved because it seems I'm a little luckier if I turn off and unplug any peripherals before booting. But around line 325 in my dmesg logs, at the last step that mentions my GPU (pci device :01:00.0), there is consistently at most a 6 ms delay for successful boots, but a 30 ms one for unsuccessful ones. Also, on all dmesg logs from successful boots, around line 610, the message Boot video device is recorded for the PCI number of my GPU, but for every fallback, the message never appears. That's why I'm thinking it's a kernel issue because the earliest mention of a specific driver module doesn't occur until later in the log. I'm currently using fully updated versions of nvidia driver 295.49. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.39 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyle 1790 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 48' Mixer name : 'SigmaTel STAC9872AK' Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,0010' Controls : 18 Simple ctrls : 9 Date: Tue Jun 5 22:44:22 2012 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1b676222-44c7-453c-a522-06b6fd5d66f4 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Sony Corporation VGN-FZ260E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic-pae root=UUID=e330e46a-b426-439f-8037-c1069cc693ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1120J7 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:bvnPhoenixTechnologiesLTD:bvrR1120J7:bd07/04/2007:svnSonyCorporation:pnVGN-FZ260E:pvrFC01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ260E dmi.product.version: FC01 dmi.sys.vendor: Sony
