Bug 950163 - leds_ss4200 driver crashes on kernel load
Summary: leds_ss4200 driver crashes on kernel load
Keywords:
Status: CLOSED DUPLICATE of bug 950160
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-09 18:46 UTC by BReaK da iCE
Modified: 2013-04-10 16:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 16:20:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description BReaK da iCE 2013-04-09 18:46:36 UTC
Description of problem:

leds_ss4200 driver fails to load on boot

Version-Release number of selected component (if applicable):

Linux 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

Every time

Steps to Reproduce:
1. Boot machine
  
Actual results:

Apr  9 10:28:11 nas kernel: [   11.305278] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr  9 10:28:11 nas kernel: [   11.315424] lpc_ich: Resource conflict(s) found affecting gpio_ich
Apr  9 10:28:11 nas kernel: [   11.327331] leds_ss4200: detected 'Intel SS4200-E'
Apr  9 10:28:11 nas kernel: [   11.332120] leds_ss4200: registering PCI driver
Apr  9 10:28:11 nas kernel: [   11.336678] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e0
Apr  9 10:28:11 nas kernel: [   11.337636] IP: [<ffffffff812f7d10>] kobject_get+0x10/0x40
Apr  9 10:28:11 nas kernel: [   11.337636] PGD 0
Apr  9 10:28:11 nas kernel: [   11.337636] Oops: 0000 [#1] SMP
Apr  9 10:28:11 nas kernel: [   11.337636] Modules linked in: leds_ss4200(+) lpc_ich mfd_core i2c_i801 coretemp i2c_core serio_raw ftdi_sio microcode e1000e nfsd auth_rpcgss nfs_acl lockd sunrpc raid456 async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx sata_sil24 usb_storage
Apr  9 10:28:11 nas kernel: [   11.369200] CPU 1
Apr  9 10:28:11 nas kernel: [   11.369200] Pid: 383, comm: systemd-udevd Not tainted 3.8.5-201.fc18.x86_64 #1 Intel SS4200-E/SS4200-E
Apr  9 10:28:11 nas kernel: [   11.369200] RIP: 0010:[<ffffffff812f7d10>]  [<ffffffff812f7d10>] kobject_get+0x10/0x40
Apr  9 10:28:11 nas kernel: [   11.369200] RSP: 0018:ffff88007bff5bf8  EFLAGS: 00010282
Apr  9 10:28:11 nas kernel: [   11.369200] RAX: 00000000000000a8 RBX: ffff880079210c00 RCX: 0000000000000000
Apr  9 10:28:11 nas kernel: [   11.369200] RDX: ffff8800797e2400 RSI: ffffffff81a212b4 RDI: 00000000000000a8
Apr  9 10:28:11 nas kernel: [   11.369200] RBP: ffff88007bff5c08 R08: 0000000000000000 R09: 000000000000ffff
Apr  9 10:28:11 nas kernel: [   11.369200] R10: ffff88007d001308 R11: 0000000000000000 R12: ffff880079210c00
Apr  9 10:28:11 nas kernel: [   11.369200] R13: ffffffff81a28a8b R14: ffff880079210e60 R15: ffff880079210c00
Apr  9 10:28:11 nas kernel: [   11.369200] FS:  00007f147e4ab840(0000) GS:ffff88007fc80000(0000) knlGS:0000000000000000
Apr  9 10:28:11 nas kernel: [   11.369200] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr  9 10:28:11 nas kernel: [   11.369200] CR2: 00000000000000e0 CR3: 000000007892b000 CR4: 00000000000007e0
Apr  9 10:28:11 nas kernel: [   11.369200] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr  9 10:28:11 nas kernel: [   11.369200] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr  9 10:28:11 nas kernel: [   11.369200] Process systemd-udevd (pid: 383, threadinfo ffff88007bff4000, task ffff880036f90000)
Apr  9 10:28:11 nas kernel: [   11.369200] Stack:
Apr  9 10:28:11 nas kernel: [   11.369200]  000000000000000f ffff880079210cb8 ffff88007bff5c18 ffffffff813e65a7
Apr  9 10:28:11 nas kernel: [   11.369200]  ffff88007bff5c98 ffffffff813e7ef3 ffff88007bff5c58 ffffffff8108ec02
Apr  9 10:28:11 nas kernel: [   11.369200]  ffffffff81a28a8b ffff880079210c00 ffff880079210c00 ffffffff81a28a8b
Apr  9 10:28:11 nas kernel: [   11.369200] Call Trace:
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff813e65a7>] get_device+0x17/0x30
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff813e7ef3>] device_add+0xd3/0x6e0
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff8108ec02>] ? complete_all+0x52/0x60
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff813e851e>] device_register+0x1e/0x30
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff813e862b>] device_create_vargs+0xfb/0x130
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff813e8691>] device_create+0x31/0x40
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffffa01af000>] ? 0xffffffffa01aefff
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffffa01af01d>] ? ss4200_led_dmi_callback+0x1d/0x1d [leds_ss4200]
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff814fdc52>] led_classdev_register+0x32/0x140
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffffa01af120>] nas_gpio_init+0x103/0xfe3 [leds_ss4200]
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffffa01af01d>] ? ss4200_led_dmi_callback+0x1d/0x1d [leds_ss4200]
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff8100215a>] do_one_initcall+0x12a/0x180
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff810c4db1>] load_module+0x1b01/0x2230
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff81314dd0>] ? ddebug_proc_open+0xc0/0xc0
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff810c55b7>] sys_init_module+0xd7/0x120
Apr  9 10:28:11 nas kernel: [   11.369200]  [<ffffffff81658c19>] system_call_fastpath+0x16/0x1b
Apr  9 10:28:11 nas kernel: [   11.369200] Code: 48 c7 c7 68 3c cd 81 31 c0 e8 fd 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
Apr  9 10:28:11 nas kernel: [   11.369200] RIP  [<ffffffff812f7d10>] kobject_get+0x10/0x40
Apr  9 10:28:11 nas kernel: [   11.369200]  RSP <ffff88007bff5bf8>
Apr  9 10:28:11 nas kernel: [   11.369200] CR2: 00000000000000e0

Expected results:

[    4.753401] leds_ss4200: detected 'Intel SS4200-E'
[    4.758175] leds_ss4200: registering PCI driver
[    4.762913] Registered led device: hdd1:blue:sata
[    4.767744] Registered led device: hdd1:amber:sata
[    4.772599] Registered led device: hdd2:blue:sata
[    4.777358] Registered led device: hdd2:amber:sata
[    4.782555] Registered led device: hdd3:blue:sata
[    4.787326] Registered led device: hdd3:amber:sata
[    4.792176] Registered led device: hdd4:blue:sata
[    4.796936] Registered led device: hdd4:amber:sata
[    4.801789] Registered led device: power:blue:power
[    4.806725] Registered led device: power:amber:power

Comment 1 Dave Jones 2013-04-10 16:20:21 UTC

*** This bug has been marked as a duplicate of bug 950160 ***


Note You need to log in before you can comment on or make changes to this bug.