Latest working kernel version:Unknown
Earliest failing kernel version: 2.6.26
Distribution: Gentoo & Ubuntu
Hardware Environment: Samsung R510
X will not start when ACPI Video is loaded, system freezes (can't ssh) no entrys in messages upon reboot
When ACPI Video isn't compiled in to the kernel X loads fine however when the A/C is removed (or inserted if booted from battery) laptop will freeze
I've tried stock 2.6.26 2.6.27-rc5 2.6.27-rc7 2.6.27-rc5-mm1 the latest linux-next
I've looked at bugs 9614 10448 & 10683 which seem to have similar issues except the A/C one
I tried mm and linux next to try the video_detect code but ACPI Video still doesn't work
Steps to reproduce:
Start X with ACPI Video
When ACPI Video isn't compiled remove A/C
Created attachment 18065 [details]
Created attachment 18066 [details]
lspci -vvxxx output
Created attachment 18067 [details]
Just to clarify the A/C problem happens when X is loaded and when it hasn't been
The laptop survives the power being pulled it's when the A/C is reinserted the problem occurs
I think I've found the problem in my /var/log/messages and I'm attaching the snippet
I'll retest again and take a picture of the syslog on screen when it happens as I'm sure there was mention of an unstable clock
Created attachment 18068 [details]
My laptop only survived the unplugging once out of 4 attempts the screen thene goes blank and it reboots
When it did survive I took the following snapshot
I think that's all the info you'll need, if not let me know
I'm prepaired to switch on debugging and even set up netconsole if required
Created attachment 18070 [details]
Screenshot before crash
so there are two problems here:
1. X can not be loaded when acpi video driver loaded first.
2. X freezes when unplugging AC.
for the first issue,
1. what if you echo 0 >/proc/acpi/video/*/DOS before starting X?
2. after applying the video_detect code, what if boot with "acpi_backlight=vendor"?
for the second issue,
please compile in the ACPI processor driver, and boot with "processor.max_cstate=1".
For the first issue
If ACPI Video is compiled as a module the laptop crashes as soon as it's loaded when it's compiled in it crashed when X is loaded
When doing this the first time the kernel Paniced the rest of the time it behaves as above
Again the kernel can panic, when it doesn't the laptop still crashed in removal of the A/C
> 2.6.26 2.6.27 linux-next mm
> Earliest failing kernel version: 2.6.26
Confusing. Was 2.6.26 OK or not?
2.6.26 had this issue
This was the earliest kernel I tried
Should I try an earlier kernel?
Is there any other info you'd like to try and diagnose this?
Lets focus on one issue in this bug report -- the simpler
and more dramatic issue that when you pull out the A/C,
your system shuts down. Lets move the video/X issue
to another bug report, okay? At the end of the day
the two may be related, but buttons & events should
be easier to debug than video.
The log in comment #5 shows that you are receiving a power button event
and the system is executing a graceful shutdown:
Sep 27 13:42:23 tau acpid: received event "button/power PWRF 00000080 00000001"
Sep 27 13:42:23 tau acpid: notifying client 1841[103:1002]
Sep 27 13:42:23 tau acpid: notifying client 2001[0:0]
Sep 27 13:42:23 tau acpid: client has disconnected
Sep 27 13:42:23 tau acpid: executing action "/etc/acpi/default.sh button/power PWRF 00000080 00000001"
Sep 27 13:42:23 tau init: Switching to runlevel: 0
Lets test your power button...
Please kill acpid and cat /proc/acpi/event
then press the power button, the sleep button, the lid button, and any other buttons you might have and observe what comes out on the screen.
Then switch between AC and DC a few times and report what you see.
grep . /sys/firmware/acpi/interrupts/*
between each physical event to see if you can identify which buttons & switches
map to which low-level ACPI events.
Note that you can clear these stats between tests like so:
# echo 0 > /sys/firmware/acpi/interrupts/sci
I was testing out the the latest patches in Linus's tree and noticed an option
Reserve low 64K of RAM on AMI/Phoenix BIOSen
I activated it and low and behold I can now unplug my laptop without it crashing :D
ACPI video still crashes the machine. So yes 2 bugs - unrelated (probably)
This is a fresh Gentoo install (yes the old kernels still do crash it) but I'll test everything else once I've got a fully installed system
Is there anything else in particular you'd like me to do to figure out the ACPI video problem?
Created attachment 18451 [details]
ACPI output when unplugging and replugging power
This is the ACPI output when I plug and then unplug the power under 2.6.28-rc1
ACPI video still cannot be loaded without rebooting the system
Would you like a separate bug for the ACPI Video issue or are you happy to use this one now the power issue is sorted?
(In reply to comment #14)
> I was testing out the the latest patches in Linus's tree and noticed an
> Reserve low 64K of RAM on AMI/Phoenix BIOSen
> I activated it and low and behold I can now unplug my laptop without it
> crashing :D
do you mean this option fixes the problem for you?
(In reply to comment #16)
> Would you like a separate bug for the ACPI Video issue or are you happy to
> this one now the power issue is sorted?
Yes, we are closing to the rootcause of the shutdown problem.
please open another bug for the video issue.
please verify if the problem is fixed in the latest kernel.
The crash / reboot on AC removal is fixed in the RC kernels
The good news is with this patch and the new ACPI code in the last RC video can be loaded without causing a crash. Now it only crashed with X is loaded
The strange thing is I can load it if I start X first then modprobe the module
What info would you like to help diagnose this?
Oh yes meant to say that the brightness keys don't change the brightness whether the module is loaded or not or if X is loaded or not but I guess this could be a configuration issue
My last laptop changed the brightness no matter what was loaded
close this bug as the problem is fixed in the RC kernels.
For the video issue, it should be "system crashes when starting X with video driver loaded", right? please open another bug.
And please provide this info:
1. in console mode, attach the dmesg output after loading the video driver.
2. attach the result of "grep . /proc/acpi/video/*/*" and "grep /sys/class/backlight/*/*" after loading the video driver.
3. poking these files (if there are any) to try to change the backlight, can you change the backlight successfully? does the system crash?
4. attach the screenshot when system crashes.
New bug created
The only way to fix this for real is to use the boot parm mem=4096M but it mean's 1GB of RAM is unavailable
Other Samsung laptops have been fixed by updating to newer BIOSs however the R510 hasn't had any new releases
How about close one of 11658/12106?
It seems that they are the duplicated bug.
no ,they are different bugs and I asked him to open a new bug for each issue.
Now it seems they can be fixed by the same workaround, but we still need to keep them open until we get the rootcause.
please try this patch and see if it helps
so this patch doesn't help on this issue neither, right?
what about this boot option, "nosmp"?
please attach the output of "cat /proc/meminfo"
Created attachment 23135 [details]
This is /proc/meminfo with the boot parm mem=4g will try without this and also with nosmp as requested
do you know the physical memory size of your laptop?
Created attachment 23136 [details]
No mem parm passed
This is the same info but without mem=4g being passed, this makes my laptop nearly useless with and without the nosmp option
The physical memory size for this laptop is 4g
*** Bug 12106 has been marked as a duplicate of this bug. ***
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009e400 (usable)
BIOS-e820: 000000000009e400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000bd6a1000 (usable)
BIOS-e820: 00000000bd6a1000 - 00000000bd6a7000 (reserved)
BIOS-e820: 00000000bd6a7000 - 00000000bd7b4000 (usable)
BIOS-e820: 00000000bd7b4000 - 00000000bd80f000 (reserved)
BIOS-e820: 00000000bd80f000 - 00000000bd907000 (usable)
BIOS-e820: 00000000bd907000 - 00000000bdb0f000 (reserved)
BIOS-e820: 00000000bdb0f000 - 00000000bdb18000 (usable)
BIOS-e820: 00000000bdb18000 - 00000000bdb1f000 (reserved)
BIOS-e820: 00000000bdb1f000 - 00000000bdb64000 (usable)
BIOS-e820: 00000000bdb64000 - 00000000bdb9f000 (ACPI NVS)
BIOS-e820: 00000000bdb9f000 - 00000000bdc00000 (ACPI data)
BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
You have 4G physical memory on your laptop. but the BIOS e820 table exports 5G avaiable memory.
this explains why mem=4G workarounds the problem for you.
So this is a BIOS bug, and this can only be fixed by BIOS upgrade.
please verify if there is any BIOS upgrade for this laptop.
If not, I think you can raise this problem to samsung.
Still no BIOS upgrade from Samsung, They were made aware of these bugs a very long time ago but insist that only 32bit Vista is supported (which of course works)
Is there any other way to get the other gig of ram working?
I think this laptop will be getting replaced with a new i7 soon anyway but I'd be nice to get everything all working before it's given to someone else to suffer
(In reply to comment #36)
> Still no BIOS upgrade from Samsung, They were made aware of these bugs a very
> long time ago but insist that only 32bit Vista is supported (which of course
> Is there any other way to get the other gig of ram working?
there is no the other gig of ram.
there are 4G in all, but BIOS tells the OS that we have 5G.
so the error occurs when OS tries to access the memory higher than 4G.
> I think this laptop will be getting replaced with a new i7 soon anyway but
> be nice to get everything all working before it's given to someone else to
IMO, before the bug being fixed by BIOS, using "mem=4096M" is an acceptable workaround for now.
When I boot with mem=4g I dont get all my 4gigs of RAM I get 3050020kb ie 3gigs
Is there no way to get all 4 gigs of memory working?
Good news thanks to Windows 7 requiring 64bit to get the Win7 seal of approval Samsung has now put out an updated (and fixed) BIOS!!