Bug 152148

what is that 'tstore' module ? Does it work if that hasn't been loaded?

tstore is a file system driver. Like most of the other modules it is unrelated
to the problem. I have now reproduced the problem with as few modules as possible:

ACPI wakeup devices: 
PCI0 MDEM  LAN COM1  LID 
ACPI: (supports S0 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 164k freed
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
Unable to handle kernel NULL pointer dereference at virtual address 00000004
 printing eip:
dc84c823
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: video ext3 jbd
CPU:    0
EIP:    0060:[<dc84c823>]    Not tainted VLI
EFLAGS: 00010246   (2.6.10-1.770_FC2) 
EIP is at acpi_video_device_write_brightness+0x56/0x86 [video]
eax: 00000063   ebx: 00000063   ecx: 00000000   edx: 00000000
esi: dac52520   edi: 00000002   ebp: db10cfac   esp: db10cf78
ds: 007b   es: 007b   ss: 0068
Process bash (pid: 562, threadinfo=db10c000 task=dbd50c10)
Stack: 00003939 dc84fa60 dac37b80 00000002 c0161c26 db10cfac b7f1f000 dac37b80 
       fffffff7 b7f1f000 db10c000 c0161cf0 db10cfac 00000000 00000000 00000000 
       00000001 00000002 c0103473 00000001 b7f1f000 00000002 00000002 b7f1f000 
Call Trace:
 [<c0161c26>] vfs_write+0xb8/0xe4
 [<c0161cf0>] sys_write+0x3c/0x62
 [<c0103473>] syscall_call+0x7/0xb
Code: 98 e3 85 c0 b9 f2 ff ff ff 75 49 c6 04 3c 00 31 c9 31 d2 89 e0 e8 1a da 98
e3 83 f8 64 89 c3 b9 f2 ff ff ff 77 2e 8b 56 1c 31 c9 <3b> 4a 04 7d 22 8b 42 08
3b 1c 88 75 14 89 da 89 f0 e8 92 f8 ff 

Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.

With kernel-2.6.12-1.1447_FC4 this cause a panic.

Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.

Still panics with kernel-2.6.13-1.1526_FC4

echo 50 > brightness

with 2.6.13-1.1532_FC4, on Toshiba Tecra S2 causes shell to close and no change
in LCD brightness

More on my previous comment.  I check /var/log/messages and found an oops.  It
is tainted (nvidia).  Let me know if you would like me to try it again without
the nvidia module.

Oct 30 18:43:47 tecra su(pam_unix)[3079]: session opened for user root by (uid=500)
Oct 30 18:43:55 tecra kernel:  <1>Unable to handle kernel NULL pointer
dereference at virtual address 00000004
Oct 30 18:43:55 tecra kernel:  printing eip:
Oct 30 18:43:55 tecra kernel: f8ac479b
Oct 30 18:43:55 tecra kernel: *pde = 00000000
Oct 30 18:43:55 tecra kernel: Oops: 0000 [#2]
Oct 30 18:43:55 tecra kernel: Modules linked in: nvidia(U) parport_pc lp parport
autofs4 rfcomm l2cap bluetooth sunrpc arc4 ieee80211_crypt_wep ipt_REJECT
ipt_state ip_conntrack iptable_filter ip_tables vfat fat dm_mod video button
battery ac ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core uhci_hcd
ehci_hcd shpchp snd_intel8x0m i2c_i801 i2c_core snd_intel8x0 snd_ac97_codec
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc sk98lin ipw2200
ieee80211 ieee80211_crypt joydev ext3 jbd ata_piix libata sd_mod scsi_mod
Oct 30 18:43:55 tecra kernel: CPU:    0
Oct 30 18:43:55 tecra kernel: EIP:    0060:[<f8ac479b>]    Tainted: P      VLI
Oct 30 18:43:55 tecra kernel: EFLAGS: 00210293   (2.6.13-1.1532_FC4)
Oct 30 18:43:55 tecra kernel: EIP is at
acpi_video_device_write_brightness+0x44/0x84 [video]
Oct 30 18:43:55 tecra kernel: eax: 00000032   ebx: 00000032   ecx: 00000000  
edx: 0000000a
Oct 30 18:43:55 tecra su(pam_unix)[3079]: session closed for user root
Oct 30 18:43:55 tecra kernel: esi: f7479200   edi: b7fad000   ebp: 00000003  
esp: f6a56f70
Oct 30 18:43:55 tecra kernel: ds: 007b   es: 007b   ss: 0068
Oct 30 18:43:55 tecra kernel: Process bash (pid: 3082, threadinfo=f6a56000
task=f05fcaa0)
Oct 30 18:43:55 tecra kernel: Stack: badc0ded 000a3035 f05e6840 00000003
b7fad000 f8ac4757 c01a1017 f6a56fa4
Oct 30 18:43:56 tecra kernel:        f05e6840 fffffff7 b7fad000 f6a56000
c01a117a f6a56fa4 00000000 00000000
Oct 30 18:43:56 tecra kernel:        00000000 00000001 00000003 c0104465
00000001 b7fad000 00000003 00000003
Oct 30 18:43:56 tecra kernel: Call Trace:
Oct 30 18:43:56 tecra kernel:  [<f8ac4757>]
acpi_video_device_write_brightness+0x0/0x84 [video]
Oct 30 18:43:56 tecra kernel:  [<c01a1017>] vfs_write+0xa2/0x15a
Oct 30 18:43:56 tecra kernel:  [<c01a117a>] sys_write+0x41/0x6a
Oct 30 18:43:56 tecra kernel:  [<c0104465>] syscall_call+0x7/0xb
Oct 30 18:43:56 tecra kernel: Code: 41 01 83 f8 04 77 50 89 e0 e8 0a 99 79 c7 85
c0 75 4c c6 04 2c 00 31 c9 31 d2 89 e0 e8 8f 7d 79 c7 89 c3 83 f8 64 77 36 8b 4e
1c <8b> 79 04 31 d2 eb 1d 8b 41 08 3b 1c 90 75 14 89 da 89 f0 e8 0a

The problem is not Fedora Core specific. It also happens on a Dell Inspiron 8200
running Sourcemage with kernel version 2.6.13.

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

Still panics with 2.6.14-1.1637_FC4

this may be fixed in 2.6.15, can you try FC5-T2?

theres also a 2.6.15 update in the updates-testing repo for fc4.

On kernel-2.6.15-1.1824_FC4 I have not been able to reproduce the Oops. Now
writes to /proc/acpi/video/VGA/LCD/brightness just result in EINVAL. I would
have expected it to change the brightness.

This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.

kernel-2.6.14-1.1637_FC4 and earlier crash. 2.6.14-1.1656_FC4 and later just
return EINVAL. Is EINVAL correct behaviour? I would expect it to change the
brightness.

[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

With 2.6.18-1.2200.fc5 I get -EINVAL. I expected the brightness to change.

Why is status still NEEDINFO? I have retested with FC5.

what do you get when you cat that file on that system ?

cat /proc/acpi/video/VGA/LCD/brightness
<not supported>

How am I supposed to interpret that? The kernel does change the brightness when
I press the brightness keys on the keyboard.

Fedora Core 5 is no longer maintained. Is this bug still present in Fedora 7 or
Fedora 8?

Removing NeedsRetesting from whiteboard so we can repurpose it.

I no longer have the machine where I was able to reproduce this bug.

Hmm, I think this bug can be closed now.

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers