Summary: | Kernel panic when writing to /proc/acpi/video/GFX0/LCD/brightness | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stan Behrens <bugs.gentoo.org> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stan Behrens
2005-04-20 07:56:36 UTC
Ok, here's how you can help me track this down: Make sure you haven't made any changes to your kernel compilation *without* rebooting into it (i.e. if you have changed stuff in /usr/src/linux, compile it and copy over the new bzImage, reboot, etc). If you have time, it would be useful trying to reproduce this on vanilla-sources-2.6.12_rc3. So, you could install and compile that now, and reboot into it. The interesting line in the oops is this one: EIP is at acpi_video_device_write_brightness+0x69/0x96 Reproduce the oops and check the function and offset again. The interesting part is before the / in the above message, i.e. "acpi_video_device_write_brightness+0x69". It's important that we know the up-to-date offset (0x69 above) of the error. Go into your kernel sources directory, and enable CONFIG_DEBUG_INFO: # cd /usr/src/linux # make menuconfig Kernel hacking ---> [*] Kernel debugging [*] Compile the kernel with debug info Save and exit. Don't recompile *anything*, other than running: # rm drivers/acpi/video.o # make drivers/acpi/video.o Now run gdb on that object (you might need to emerge gdb) # gdb drivers/acpi/video.o At the gdb prompt, run: # list *acpi_video_device_write_brightness+0x69 Note the * prefix, and use the correct offset address if it has changed from 0x69 Please post the full output of the above command to this bug. If thats too much work you could just report it to http://bugzilla.kernel.org - there may be an obvious fix. Please reopen when you are able to take up one of the above suggestions. You should also test 2.6.12-rc5 to see if the issue has already been fixed. |