*** Bug 950163 has been marked as a duplicate of this bug. ***

Your expected results look like they come from an actual kernel boot.  Do you have a working kernel with this driver loading, and if so what version is it and can you post the dmesg?

(In reply to comment #2)
> Your expected results look like they come from an actual kernel boot.  Do
> you have a working kernel with this driver loading, and if so what version
> is it and can you post the dmesg?

Sorry Josh, no I don't. I got the expected results from g00gle search. :(

I have the same problem with my SS-4200 running Gentoo Linux.
Last known good kernel: 3.5.7-gentoo
dmesg snippet from 3.5.7-gentoo:
[    2.843974] cpuidle: using governor ladder
[    2.848047] cpuidle: using governor menu
[    2.851958] leds_ss4200: detected 'Intel SS4200-E'
[    2.856722] leds_ss4200: registering PCI driver
[    2.861334] Registered led device: hdd1:blue:sata
[    2.861368] Registered led device: hdd1:amber:sata
[    2.861400] Registered led device: hdd2:blue:sata
[    2.861434] Registered led device: hdd2:amber:sata
[    2.861465] Registered led device: hdd3:blue:sata
[    2.861498] Registered led device: hdd3:amber:sata
[    2.861528] Registered led device: hdd4:blue:sata
[    2.861561] Registered led device: hdd4:amber:sata
[    2.861591] Registered led device: power:blue:power
[    2.861625] Registered led device: power:amber:power
[    2.861864] TCP: cubic registered

Kernel that is definitely broken: 3.7.10-gentoo
Output of broken kernel:
[    2.525122] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
[    2.535102] IP: [<ffffffff81208b3c>] kobject_get+0xc/0x40
[    2.535102] PGD 0 
[    2.535102] Oops: 0000 [#1] SMP 
[    2.535102] Modules linked in:
[    2.535102] CPU 0 
[    2.535102] Pid: 1, comm: swapper/0 Not tainted 3.7.10-gentoo #1 Intel SS4200-E/SS4200-E
[    2.535102] RIP: 0010:[<ffffffff81208b3c>]  [<ffffffff81208b3c>] kobject_get+0xc/0x40
[    2.535102] RSP: 0000:ffff88007d065d48  EFLAGS: 00010202
[    2.535102] RAX: 00000000000000a8 RBX: ffff88007d3acc00 RCX: 0000000000000000
[    2.535102] RDX: 0000000000000000 RSI: ffffffff817187c2 RDI: 00000000000000a8
[    2.535102] RBP: 0000000000000098 R08: 0000000000000000 R09: 000000000000ffff
[    2.535102] R10: ffffffff81209b76 R11: dead000000100100 R12: 0000000000000000
[    2.535102] R13: ffff88007d3ace58 R14: 00000000ffffffea R15: ffff88007d065e40
[    2.535102] FS:  0000000000000000(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
[    2.535102] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[    2.535102] CR2: 00000000000000e0 CR3: 000000000180b000 CR4: 00000000000007f0
[    2.535102] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    2.535102] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    2.535102] Process swapper/0 (pid: 1, threadinfo ffff88007d064000, task ffff88007d068000)
[    2.535102] Stack:
[    2.535102]  ffff88007d0fed90 ffff88007d3accb8 0000000000000296 ffffffff81293814
[    2.535102]  ffffffff816f47e2 ffffffff81294da9 ffff88007d065e40 ffffffff8106c150
[    2.535102]  ffff88007d3acc00 ffff88007d3accb0 0000000000000296 ffffffff8129ed6b
[    2.535102] Call Trace:
[    2.535102]  [<ffffffff81293814>] ? get_device+0x14/0x20
[    2.535102]  [<ffffffff81294da9>] ? device_add+0xb9/0x6c0
[    2.535102]  [<ffffffff8106c150>] ? complete_all+0x40/0x60
[    2.535102]  [<ffffffff8129ed6b>] ? device_pm_sleep_init+0x4b/0x80
[    2.535102]  [<ffffffff812954cb>] ? device_create_vargs+0xfb/0x130
[    2.535102]  [<ffffffff8129552f>] ? device_create+0x2f/0x40
[    2.535102]  [<ffffffff8129804b>] ? driver_register+0xfb/0x140
[    2.535102]  [<ffffffff818b04da>] ? ss4200_led_dmi_callback+0x1a/0x1a
[    2.535102]  [<ffffffff813adb54>] ? led_classdev_register+0x24/0x120
[    2.535102]  [<ffffffff818b05da>] ? nas_gpio_init+0x100/0x1ab
[    2.535102]  [<ffffffff818b04da>] ? ss4200_led_dmi_callback+0x1a/0x1a
[    2.535102]  [<ffffffff810001f9>] ? do_one_initcall+0x39/0x170
[    2.535102]  [<ffffffff8188db49>] ? kernel_init_freeable+0xfc/0x18c
[    2.535102]  [<ffffffff8188d568>] ? do_early_param+0x7d/0x7d
[    2.535102]  [<ffffffff81474f80>] ? rest_init+0x70/0x70
[    2.535102]  [<ffffffff81474f89>] ? kernel_init+0x9/0x100
[    2.535102]  [<ffffffff81494a6c>] ? ret_from_fork+0x7c/0xb0
[    2.535102]  [<ffffffff81474f80>] ? rest_init+0x70/0x70
[    2.535102] Code: 0f 1f 80 00 00 00 00 be 01 00 00 00 4c 89 ef e8 db 13 00 00 0f b6 43 04 e9 77 ff ff ff 66 90 48 83 ec 18 48 85 ff 48 89 f8 74 0b <8b> 57 38 85 d2 74 09 f0 ff 40 38 48 83 c4 18 c3 be 2a 00 00 00 
[    2.535102] RIP  [<ffffffff81208b3c>] kobject_get+0xc/0x40
[    2.535102]  RSP <ffff88007d065d48>
[    2.535102] CR2: 00000000000000e0
[    2.825660] ---[ end trace 123b9cff480be2e4 ]---
[    2.830265] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009

I remember linux-3.6.11-gentoo not having booted as well but I didn't dig into that and as such don't have a log to show

Removing the SS4200-led option from the kernel config, rebuilding the kernel and rebooting makes the device boot up fine again:
nas ~ # uname -a
Linux nas 3.7.10-gentoo #2 SMP Sat Apr 13 18:37:12 CEST 2013 x86_64 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz GenuineIntel GNU/Linux

fc18 boots up with these errors too. No need to rebuild the kernel. It would be nice to get the leds working again though. ;)

I reported this upstream.

Can we do some bisect between 3.5 and 3.7 or 3.6? It should be not very hard find it, since leds subsystem changes almost goes into kernel during merge windows.

So please try 3.5-rc1 and 3.6-rc1 firstly.

Linux 3.5.1 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
leds_ss4200: detected 'Intel SS4200-E'
leds_ss4200: registering PCI driver


Linux 3.6.1 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
[   12.421391] leds_ss4200: detected 'Intel SS4200-E'
[   12.426187] leds_ss4200: registering PCI driver
[   12.430746] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
[   12.431701] IP: [<ffffffff812d00b0>] kobject_get+0x10/0x40
[   12.431701] PGD 0
[   12.431701] Oops: 0000 [#1] SMP
[   12.431701] Modules linked in: leds_ss4200(+) i2c_i801 lpc_ich i2c_core ftdi_sio mfd_core sunrpc serio_raw coretemp microcode pcspkr sata_sil24 usb_storage
[   12.431701] CPU 1
[   12.431701] Pid: 339, comm: systemd-udevd Not tainted 3.6.1 #1 Intel SS4200-E/SS4200-E
[   12.431701] RIP: 0010:[<ffffffff812d00b0>]  [<ffffffff812d00b0>] kobject_get+0x10/0x40
[   12.431701] RSP: 0018:ffff880037567c88  EFLAGS: 00010286
[   12.431701] RAX: 00000000000000a8 RBX: ffff88003722dc00 RCX: 0000000000000000
[   12.491807] RDX: ffff880036d114d0 RSI: ffffffff81a0a26c RDI: 00000000000000a8
[   12.491807] RBP: ffff880037567c98 R08: 0000000000000000 R09: 000000000000ffff
[   12.491807] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88003722dc00
[   12.491807] R13: ffffffff81a1189f R14: ffff88003722de68 R15: ffff88003722dc00
[   12.491807] FS:  00007fc95eb89840(0000) GS:ffff88007fc80000(0000) knlGS:0000000000000000
[   12.491807] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   12.491807] CR2: 00000000000000e0 CR3: 0000000037651000 CR4: 00000000000007e0
[   12.491807] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   12.491807] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   12.491807] Process systemd-udevd (pid: 339, threadinfo ffff880037566000, task ffff8800373516f0)
[   12.491807] Stack:
[   12.491807]  000000000000000f ffff88003722dcb8 ffff880037567ca8 ffffffff813b0087
[   12.491807]  ffff880037567d28 ffffffff813b1b53 ffff88003722dc00 ffff88003722dcb0
[   12.491807]  ffff880037567ce8 ffffffff813c0c4d ffff88003722dcb0 ffff88003722dc00
[   12.491807] Call Trace:
[   12.491807]  [<ffffffff813b0087>] get_device+0x17/0x30
[   12.491807]  [<ffffffff813b1b53>] device_add+0xd3/0x6e0
[   12.491807]  [<ffffffff813c0c4d>] ? pm_runtime_init+0xdd/0xf0
[   12.491807]  [<ffffffff813b217e>] device_register+0x1e/0x30
[   12.491807]  [<ffffffff813b228b>] device_create_vargs+0xfb/0x130
[   12.491807]  [<ffffffff813b22f1>] device_create+0x31/0x40
[   12.491807]  [<ffffffff811f40c6>] ? sysfs_create_file+0x26/0x30
[   12.491807]  [<ffffffff813b54e7>] ? driver_create_file+0x17/0x30
[   12.491807]  [<ffffffff814bf661>] led_classdev_register+0x31/0x100
[   12.491807]  [<ffffffffa008d120>] nas_gpio_init+0x103/0xfe3 [leds_ss4200]
[   12.491807]  [<ffffffffa008d01d>] ? ss4200_led_dmi_callback+0x1d/0x1d [leds_ss4200]
[   12.491807]  [<ffffffff8100212a>] do_one_initcall+0x12a/0x180
[   12.491807]  [<ffffffff810bd846>] sys_init_module+0x10d6/0x2080
[   12.491807]  [<ffffffff812ed1a0>] ? ddebug_proc_open+0xd0/0xd0
[   12.491807]  [<ffffffff81616ca9>] system_call_fastpath+0x16/0x1b
[   12.491807] Code: 48 c7 c7 a0 c3 cc 81 31 c0 e8 8d be 01 00 eb d0 66 66 2e 0f 1f 84 00 00 00 00 00 48 85 ff 48 89 f8 74 14 55 48 89 e5 48 83 ec 10 <8b> 57 38 85 d2 74 07 f0 ff 40 38 c9 f3 c3 be 2a 00 00 00 48 c7
[   12.491807] RIP  [<ffffffff812d00b0>] kobject_get+0x10/0x40
[   12.491807]  RSP <ffff880037567c88>
[   12.491807] CR2: 00000000000000e0

Could you please revert following to patches on top of 3.6.1 or 3.6-rc1 and try again?

a0193cb leds: use led_set_brightness in led_trigger_event
19cd67e leds: Rename led_brightness_set() to led_set_brightness()
0da3e65 leds: Rename led_set_brightness() to __led_set_brightness()
5e41728 leds: add oneshot trigger
4378648 leds: fix led_brightness_set when soft-blinking
3740e49 ledtrig-ide-disk: use generic one-shot blink api
5bb629c leds: add oneshot blink functions
eb20262 led-triggers: rename *trigger to *trig for unified naming scheme

Thanks,
-Bryan

Here are my results of reverting patches one by one:

a0193cb was not applied / already reverted in 3.6.1
19cd67e reverted: build failure
0da3e65 reverted: build okay. boot failed
5e41728 reverted (with offset): build okay, boot failed
4378648 reverted: build okay. boot failed
3740e49 reverted: build okay. boot failed
5bb629c reverting failed: 
miramis linux-3.6.1 # patch -p1 -R --dry-run < ../led-patches/5bb629c.diff 
patching file drivers/leds/led-class.c
patching file drivers/leds/led-core.c
Hunk #2 FAILED at 61.
1 out of 3 hunks FAILED -- saving rejects to file drivers/leds/led-core.c.rej
patching file drivers/leds/led-triggers.c
Unreversed patch detected!  Ignore -R? [n]

I stopped at that point

Thanks for the testing, So could you please just reset the whole tree to eb20262 led-triggers: rename *trigger to *trig for unified naming scheme? And try again?

-Bryan

What I did out of personal interest (I don't know if this is new info or has been known already):
3.5-rc1: okay
3.6-rc1: okay
3.6-rc2: okay
3.6-rc3: okay
3.6-rc4: okay
3.6-rc5: okay
3.6-rc6: failed

In the ChangeLog (from https://lkml.org/lkml/2012/9/16/102 ) there's nothing matching " trig" or " led" or "4200" so I wouldn't know what exactly causes the issue here :/

And whole tree at eb20262 results in a bootable and working system

I don't think that it really makes any difference but nevertheless:
The SS4200 needs a patch for the ICH7 ATA driver to detect the IDE drive correctly. I had it applied when compiling the kernel. Patch can be found here:
http://forum.wegotserved.com/index.php?/topic/16256-fedora-13-on-ss4200-with-full-speed-pata-drive-and-4-sata-drives/

Sorry for the delay.

So is that possible for you to dig deeper. It should be easy for you find the suspected commit between 3.6-rc5 and 3.6-rc6. I don't have the hardware to do that.

Thanks,
-Bryan

If you could give me detailed instructions what to look for and what to do then I will look into this. Otherwise it will not get fixed. :(
3.10 has the same problem still in the code...

So it's basically a bisect job. 

You need revert the whole git tree back to a certain point between 3.6-rc5 and 3.6-rc6. Let's say we roll back to in the middle of it. There are 360 patches in this cycle, so probably you can try to roll back to (3.6-rc5 + 180) and test it on the hardware to see if it works. If it works, that means bad commit is between 3.6-rc5+180 and 3.6-rc6. if it doesn't, then bad one should be introduced before 3.5-rc5 and 3.5-rc5+180. It's kind of binary search. Then finally you will find the bad commit introduce this regression.

I suspect it's related to ACPI changes probably we can start try the kernel without those ACPI commits.

Thanks,
-Bryan

[   11.582612] leds_ss4200: detected 'Intel SS4200-E'
[   11.587399] leds_ss4200: registering PCI driver
[   11.592008] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
[   11.593001] IP: [<ffffffff812e85bd>] kobject_get+0xd/0x50
[   11.593001] PGD 0
[   11.593001] Oops: 0002 [#1] SMP
[   11.593001] Modules linked in: leds_ss4200(+) acpi_cpufreq(-) mperf nfs_acl coretemp lockd lpc_ich mfd_core ftdi_sio i2c_i801 i2c_core pps_core serio_raw microcode sunrpc sata_sil24
[   11.593001] CPU: 0 PID: 314 Comm: systemd-udevd Not tainted 3.10.10-200.fc19.x86_64 #1
[   11.593001] Hardware name: Intel SS4200-E/SS4200-E, BIOS V090L   12/19/2007
[   11.593001] task: ffff88003721eac0 ti: ffff88007b9e0000 task.ti: ffff88007b9e0000
[   11.593001] RIP: 0010:[<ffffffff812e85bd>]  [<ffffffff812e85bd>] kobject_get+0xd/0x50
[   11.593001] RSP: 0018:ffff88007b9e1c20  EFLAGS: 00010202
[   11.593001] RAX: 00000000000000a8 RBX: ffff880037212c10 RCX: 0000000000000000
[   11.593001] RDX: 0000000000000001 RSI: ffffffff81a312b4 RDI: 00000000000000a8
[   11.593001] RBP: ffff88007b9e1c80 R08: 0000000000000000 R09: 000000000000ffff
[   11.593001] R10: ffffffff813d8f13 R11: 0000000000000000 R12: 0000000000000000
[   11.593001] R13: 0000000000000000 R14: ffff880037212c00 R15: 0000000000000000
[   11.593001] FS:  00007f44de5f7880(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000
[   11.593001] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   11.593001] CR2: 00000000000000e0 CR3: 000000007b83a000 CR4: 00000000000007f0
[   11.593001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   11.593001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   11.593001] Stack:
[   11.593001]  ffffffff813d9058 ffffffff8108a927 ffff880037212c00 ffff880037212c00
[   11.593001]  0000000000000000 ffff88007b9e1cd8 00000000a98af434 ffff880037212c00
[   11.593001]  0000000000000000 ffff88007b9e1cd8 ffff880037212c10 0000000000000000
[   11.593001] Call Trace:
[   11.593001]  [<ffffffff813d9058>] ? device_add+0xe8/0x720
[   11.593001]  [<ffffffff8108a927>] ? complete_all+0x47/0x50
[   11.593001]  [<ffffffff813d9898>] device_create_vargs+0xd8/0x100
[   11.593001]  [<ffffffff813d98f4>] device_create+0x34/0x40
[   11.593001]  [<ffffffff812e9a9b>] ? kobject_uevent+0xb/0x10
[   11.593001]  [<ffffffff813dcbbb>] ? driver_register+0x10b/0x150
[   11.593001]  [<ffffffff814ea532>] led_classdev_register+0x32/0x140
[   11.593001]  [<ffffffffa00ad129>] nas_gpio_init+0x10c/0xfe3 [leds_ss4200]
[   11.593001]  [<ffffffffa00ad01d>] ? ss4200_led_dmi_callback+0x1d/0x1d [leds_ss4200]
[   11.593001]  [<ffffffff810020e2>] do_one_initcall+0xe2/0x190
[   11.593001]  [<ffffffff810bf8b5>] load_module+0x1bb5/0x2650
[   11.593001]  [<ffffffff81305d00>] ? ddebug_proc_write+0xf0/0xf0
[   11.593001]  [<ffffffff810c04e6>] SyS_finit_module+0x86/0xb0
[   11.593001]  [<ffffffff81647c59>] system_call_fastpath+0x16/0x1b
[   11.593001] Code: 81 48 c7 c7 10 c3 cd 81 31 c0 e8 df c2 01 00 eb ca 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 85 ff 48 89 f8 74 12 ba 01 00 00 00 <f0> 0f c1 57 38 83 c2 01 83 fa 01 7e 01 c3 80 3d e2 6b 9e 00 00
[   11.593001] RIP  [<ffffffff812e85bd>] kobject_get+0xd/0x50
[   11.593001]  RSP <ffff88007b9e1c20>
[   11.593001] CR2: 00000000000000e0
[   11.873844] ---[ end trace d2fda13d35a71115 ]---

[   11.416109] ACPI Warning: 0x00000000000004b0-0x00000000000004bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20130328/utaddress-251)
[   11.428889] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   11.439046] ACPI Warning: 0x0000000000000480-0x00000000000004af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPIO 1 (20130328/utaddress-251)
[   11.451829] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   11.461974] lpc_ich: Resource conflict(s) found affecting gpio_ich

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  

It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo.  Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue.  As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution

If you experience different issues, please open a new bug report for those.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days