Kernel missing cores of Phenom under some USB configurations

Bug #454693 reported by TheJPK
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This is not only affect on 9.10 amd64, error even tested on 9.04 amd64, 8.04.3 LTS amd64, 9.10 i386 and Fedora 11.

When USB 2.0 Controller and High Speed is enabled the startup works correct when only a USB-keyboard is attached, else it is missing the other cores of the Phenom.

When USB-Speed is limited via BIOS to Low/Full-Speed, booting with an attached KVM (Aten CS-1762) works

http://www.aten.com/products/productItem.php?pcid=2005010513171002&psid=20070130114411002&pid=20050118170332002&layerid=subClass3

Currently running:
Description: Ubuntu karmic (development branch)
Release: 9.10

The three dmesgs inside the attachment are under follwoing situations:
- USB 2.0 Controller enabled, only Low/Fullspeed and KVM attached = found all cores
- USB 2.0 Controller enabled, Highspeed and only USB-Keyboard attached = found all cores
- USB 2.0 Controller, Highspeed enabled and KVM attached = only one of four cores

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jpk 2383 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe020000 irq 20'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:10ec0888,12970000,00100001 HDA:10de0002,10de0101,00100000'
   Controls : 40
   Simple ctrls : 20
Date: Sun Oct 18 15:45:34 2009
DistroRelease: Ubuntu 9.10
MachineType: Shuttle Inc SN78S
NonfreeKernelModules: nvidia
Package: linux-generic 2.6.31.14.27
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=UUID=33440978-ae50-4888-8439-840d6ab41eec ro quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux-meta
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2395): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2395): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2507): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2493): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 07/09/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FN78S
dmi.board.vendor: Shuttle Inc
dmi.board.version: V10
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: H7
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/09/2009:svnShuttleInc:pnSN78S:pvrV10:rvnShuttleInc:rnFN78S:rvrV10:cvnShuttleInc:ct3:cvrH7:
dmi.product.name: SN78S
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc

Revision history for this message
TheJPK (jpk) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Brad Figg (brad-figg)
tags: added: kj-triage
Brad Figg (brad-figg)
tags: added: acpi
tags: added: acpi-bad-address
tags: added: acpi-method-return
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: b73a1py79
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.