Steps to reproduce: Boot up computer, wait a few minutes, and it freezes. Fresh install of 12.04 64 bit and 12.10 32 bit also freeze. I've used kernels 3.2, 3.5, 3.8, 3.9, 2.6 and 3.0, Fedora also freezes. Oddly, it DOES NOT FREEZE if I am doing something processor intensive, like ripping a DVD or converting video. So whenever I boot up my computer, I have to immediately start ripping. I have tried to ssh into my computer from my wife's, but it is impossible while frozen note, it IS possible when my computer is not frozen.
Memtest shows no errors after running it all night. fsck shows nothing. Happens in unity 2d and unity 3d, guessing it's not compiz.
Steps to resolve: Hold down the power button.
Also, if I don't log in to x and just go straight to console, I still get freezes. No proprietary drivers either. My computer is kept dust free, it is not overheating. I tried noapic, nomodeset, acpi=off, and acpi_apic_instance=2 did not fix it.
Hitting the function button will toggle the light off and on after the freeze, but only in the first few seconds.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices: **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: joe 1879 F.... pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf5300000 irq 48'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff14,00100003'
Controls : 16
Simple ctrls : 8
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=a1b89f10-2faf-41a1-b79b-6b4a9be132ab
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213)
MachineType: TOSHIBA dynabook TX/66E
MarkForUpload: True
Package: linux (not installed)
PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=6287f357-a116-4714-a16b-65562f25df92 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A linux-firmware 1.79.1
RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: precise running-unity
Uname: Linux 3.5.0-25-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/31/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 2.00
dmi.board.name: SANTA ROSA CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd01/31/2008:svnTOSHIBA:pndynabookTX/66E:pvrPATX66ELP:rvnIntelCorporation:rnSANTAROSACRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: dynabook TX/66E
dmi.product.version: PATX66ELP
dmi.sys.vendor: TOSHIBA
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/ FindRightPackag e. 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/1154006/ +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.]