mactel-support team mailing list archive

[Mario Schwalbe <schwalbe@xxxxxxxxxxxxxxxxx>]

Uploaded new fixed version. You might also use the nvidia-bl-dkms
package. Unfortunately, it's known to not work on a MacBookPro5,1. But
I'd like to get reports for those most recent machines.

-- 
mbp-nvidia-bl-dkms does not work with karmic when using kernel 2.6.31-1-generic x86_64
https://bugs.launchpad.net/bugs/395045
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.

Status in Mactel Support: New

Bug description:
I have a MacBookPro 5.2 running karmic. I'm using the standard kernel package 2.6.31-1-generic x86_64 and mbp-nvidia-bl-dkms 0.21~jaunty

When I try to load mbp_nvidia_bl I get, in dmesg:

[  499.028436] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
[  499.028445] IP: [<ffffffff8129dfa8>] backlight_store_brightness+0xa8/0xd0
[  499.028456] PGD 14617b067 PUD 14a4ef067 PMD 0 
[  499.028461] Oops: 0000 [#2] SMP 
[  499.028465] last sysfs file: /sys/devices/virtual/backlight/mbp_backlight/brightness
[  499.028469] CPU 0 
[  499.028472] Modules linked in: mbp_nvidia_bl(+) nvidia(P) binfmt_misc ppdev bridge stp bnep nvidia_bl applesmc input_polldev coretemp hid_apple usbhid lp parport snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss b43 snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer mac80211 snd_seq_device uvcvideo snd cfg80211 videodev v4l1_compat v4l2_compat_ioctl32 soundcore snd_page_alloc joydev bcm5974 i2c_nforce2 btusb led_class pcspkr ssb ohci1394 ieee1394 forcedeth fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit video output intel_agp
[  499.028528] Pid: 5125, comm: bash Tainted: P      D    2.6.31-1-generic #14-Ubuntu MacBookPro5,2
[  499.028531] RIP: 0010:[<ffffffff8129dfa8>]  [<ffffffff8129dfa8>] backlight_store_brightness+0xa8/0xd0
[  499.028537] RSP: 0018:ffff88014a5e3e48  EFLAGS: 00010202
[  499.028540] RAX: 0000000000000038 RBX: ffff880149dfd678 RCX: 000000000000000a
[  499.028543] RDX: 0000000000000000 RSI: ffff88014a5e3e10 RDI: ffff880149dfd618
[  499.028546] RBP: ffff88014a5e3e88 R08: 0000000000000028 R09: 000000000000000a
[  499.028549] R10: 0000000000000000 R11: 0000000000000069 R12: 0000000000000002
[  499.028552] R13: ffff880149dfd638 R14: ffff880149dfd618 R15: ffff880149dfd600
[  499.028556] FS:  00007f17c1d3f6f0(0000) GS:ffff880028029000(0000) knlGS:0000000000000000
[  499.028559] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  499.028562] CR2: 0000000000000040 CR3: 000000014a5cc000 CR4: 00000000000406b0
[  499.028565] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  499.028568] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  499.028571] Process bash (pid: 5125, threadinfo ffff88014a5e2000, task ffff8801461bc410)
[  499.028574] Stack:
[  499.028575]  0000000000000000 0000000000000001 ffff88014a5e3e88 ffff88014a4f7980
[  499.028580] <0> ffff88014a5e3f48 ffff880149436500 ffffffff8178e6d0 ffff880149dfd688
[  499.028585] <0> ffff88014a5e3e98 ffffffff8130f79b ffff88014a5e3ee8 ffffffff8117a290
[  499.028591] Call Trace:
[  499.028597]  [<ffffffff8130f79b>] dev_attr_store+0x1b/0x20
[  499.028603]  [<ffffffff8117a290>] sysfs_write_file+0xe0/0x160
[  499.028609]  [<ffffffff81114ee8>] vfs_write+0xb8/0x1a0
[  499.028613]  [<ffffffff8111599c>] sys_write+0x4c/0x80
[  499.028619]  [<ffffffff81011fc2>] system_call_fastpath+0x16/0x1b
[  499.028621] Code: 12 4c 89 ef e8 ba 48 27 00 eb af 0f 1f 84 00 00 00 00 00 4d 8d 77 18 89 43 88 4c 89 f7 e8 41 4b 27 00 48 8b 43 e0 48 85 c0 74 0e <48> 8b 40 08 48 85 c0 74 05 4c 89 ff ff d0 4c 89 f7 4d 63 f4 e8 
[  499.028664] RIP  [<ffffffff8129dfa8>] backlight_store_brightness+0xa8/0xd0
[  499.028669]  RSP <ffff88014a5e3e48>
[  499.028671] CR2: 0000000000000040
[  499.028674] ---[ end trace 8e85fef35d483d20 ]---

If I boot using kernel 2.6.28-13-generic instead, no problem happens and I can control the LCD brightness normally.