[FUJITSU FMVS54KR] always boot with minimum backlight brightness

[Nobuto Murata]

It always boot with minimum backlight brightness.

just after the boot:
/sys/class/backlight/acpi_video0/actual_brightness:0
/sys/class/backlight/acpi_video0/brightness:0
/sys/class/backlight/acpi_video0/max_brightness:100
/sys/class/backlight/intel_backlight/actual_brightness:41
/sys/class/backlight/intel_backlight/brightness:3487
/sys/class/backlight/intel_backlight/max_brightness:3487

I can change brightness after boot with hotkeys.

ProblemType: BugDistroRelease: Ubuntu 13.10
Package: linux-image-3.9.0-4-generic 3.9.0-4.9
ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
Uname: Linux 3.9.0-4-generic x86_64
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nobuto 2339 F.... pulseaudio
Date: Tue Jun 11 21:55:10 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e1bbd58c-ba6f-4896-95d9-3bdb60dde26d
InstallationDate: Installed on 2013-04-21 (50 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420)
MachineType: FUJITSU FMVS54KR
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic.efi.signed root=UUID=f0ca756b-8b3f-4cb2-908f-5d8e2273c93e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.9.0-4-generic N/A
 linux-backports-modules-3.9.0-4-generic N/A
 linux-firmware 1.109SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-06-08 (2 days ago)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.06
dmi.board.name: FJNB24F
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
dmi.product.name: FMVS54KR
dmi.sys.vendor: FUJITSU

[Brad Figg (brad-figg)]

This change was made by a bot.

[Nobuto Murata (nobuto)]

On my machine, `cat /sys/class/backlight/intel_backlight/max_brightness` gives "3487".

[Nobuto Murata (nobuto)]

just after the boot:
/sys/class/backlight/acpi_video0/brightness = 0
/sys/class/backlight/intel_backlight/max_brightness = 3487

[Nobuto Murata (nobuto)]

/sys/class/backlight/acpi_video0/actual_brightness:0
/sys/class/backlight/acpi_video0/brightness:0
/sys/class/backlight/acpi_video0/max_brightness:100
/sys/class/backlight/intel_backlight/actual_brightness:41
/sys/class/backlight/intel_backlight/brightness:3487
/sys/class/backlight/intel_backlight/max_brightness:3487

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/

[Nobuto Murata (nobuto)]

tested with:
linux-headers-3.10.0-031000rc5-generic_3.10.0-031000rc5.201306082135_amd64.deb
linux-headers-3.10.0-031000rc5_3.10.0-031000rc5.201306082135_all.deb
linux-image-3.10.0-031000rc5-generic_3.10.0-031000rc5.201306082135_amd64.deb

It's still reproducible.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[Joseph Salisbury (jsalisbury)]

Also, was there a previous release or kernel version that did not exhibit this bug? If so, we can perform a kernel bisect to identify the commit that introduced this regression.

[penalvch (penalvch)]

Nobuto MURATA, could you please provide the full computer model as noted on the sticker?

[Nobuto Murata (nobuto)]

full computer model name:

FUJITSU LIFEBOOK SH54/K (FMVS54KR)

[Nobuto Murata (nobuto)]

I tried lastest mainline build, linux-image-3.12.0-999-generic_3.12.0-999.201310160446, this issue is still reproducible.

  Linux 3.12.0-999-generic #201310160446 SMP Wed Oct 16 08:48:22 UTC 2013 x86_64 x86_64 x86_64

I don't think this issue is a regression, removing the tag.

[penalvch (penalvch)]

Nobuto MURATA, unfortunately, testing the daily folder wouldn't be terribly helpful. Despite this, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/ ?

As well, unless you have tested this against prior releases, one wouldn't know if this is a regression or not.

[Nobuto Murata (nobuto)]

This issue is no longer reproducible with latest trusty kernel.
Linux lifebook 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux