Gigabyte Spring Peak [F06 BIOS] extremely slow when >4GB RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Gigabyte "Spring Peak" laptop with 8GB RAM installed.
System performance is unusably slow -- even booting just "single" mode. Booting with "mem=4g" cures the problem; "mem=5g" makes the problem return. A similar (identical?) machine with only 4GB RAM does not exhibit the problem.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xda500000 irq 22'
Mixer name : 'Intel G45 DEVCTG'
Components : 'HDA:10ec0269,
Controls : 16
Simple ctrls : 8
Date: Tue May 25 09:16:46 2010
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: GIGABYTE Spring Peak
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
WifiSyslog:
dmi.bios.date: 12/30/2009
dmi.bios.vendor: GIGABYTE
dmi.bios.version: Spring Peak F06
dmi.board.
dmi.board.name: GA-XXXXXXX
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnGIGABYTE
dmi.product.name: Spring Peak
dmi.product.
dmi.sys.vendor: GIGABYTE
summary: |
- system extremely slow when >4GB RAM + Gigabyte Spring Peak [F06 BIOS] extremely slow when >4GB RAM |
dmesg with no special boot options provided, where the super-slow-mode behavior DOES occur: