Flickering issue and subsequent freeze on a Samsung laptop

Bug #1028736 reported by Alexander Bumgardner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I submitted another report an hour or two ago. I managed to boot into safemode, and while I have the same problem, I am at least now able to submit a report. The brightness bar, appearing in the upper right screen, appears and the screen flickers. My programs will not run, my computer freezes.

Running Ubuntu 12.04 LTS 32-bit on a Samsung laptop, This problem only begun today after an update. I ran a debug process in the terminal, hopefully this provides more info. I have marked this as a possible security threat, although i apologize if that is wrong.

There is no output from minimum recommended output. However, the ubuntu-bug linux report should be attached. Please email me ASAP at <email address hidden>

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-27-generic-pae 3.2.0-27.43
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
Uname: Linux 3.2.0-27-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alcidious 1677 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0600000 irq 45'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,144dc0b6,00100100 HDA:80862805,80860101,00100000'
   Controls : 25
   Simple ctrls : 12
Date: Wed Jul 25 00:53:38 2012
HibernationDevice: RESUME=UUID=fb8dd230-66d9-49a6-a13f-4ecfc1a3b473
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae root=UUID=6a02707e-47a4-4f76-bf5a-904b8cdb1654 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-27-generic-pae N/A
 linux-backports-modules-3.2.0-27-generic-pae N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03FI
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 300V3A/300V4A/300V5A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr03FI:bd07/27/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300V3A/300V4A/300V5A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Alexander Bumgardner (spungotomer42) wrote :
security vulnerability: yes → no
Tyler Hicks (tyhicks)
visibility: private → public
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Alexander Bumgardner, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please capture the oops following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ?

As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: likely-dup likely-dup-bug-1028151
tags: added: regression-update
Revision history for this message
papukaija (papukaija) wrote : Re: Flickering issue on a Samsung laptop

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1028151, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

summary: - 2nd Screen Freeze and Sound Bar bug Report
+ Flickering issue on a Samsung laptop
Revision history for this message
Alexander Bumgardner (spungotomer42) wrote :

I disagree that my bug is a duplicate of 1028151. I tested the kernels, and the new 3.2.30 kernel with the supposed "fix". My laptop is still messed up. The only thing that worked was a test kernel that was a 3.6 one...

Revision history for this message
penalvch (penalvch) wrote :

Alexander Bumgardner, unmarking as duplicate due to your noting the verified Fix Released for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1028151 did not resolve the issue mentioned in this report.

Could you please provide the information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1028736/comments/2 ?

summary: - Flickering issue on a Samsung laptop
+ Flickering issue and subsequent freeze on a Samsung laptop
papukaija (papukaija)
tags: removed: likely-dup likely-dup-bug-1028151
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.