[ 88.628451] BUG: unable to handle kernel paging request at f8dbf000 "isight_firmware"

From: Justin Mattock
Date: Wed Jun 04 2008 - 15:14:08 EST


Yesterday I compiled the isight_firmware module, and was happy with
the result's, "no more udev",
This morning I wasn't so lucky, upon a cold boot my system was stuck
during boot, I tried numerous boot's but still the same results,
luckily I was hoping to gather the info on what was going on here it is:

[ 88.517109] firmware: requesting isight.fw
[ 88.628451] BUG: unable to handle kernel paging request at f8dbf000
[ 88.628463] IP: [<f8bc90f7>] :isight_firmware:isight_firmware_load+0xf2/0x1c3
[ 88.628474] *pde = 375a8067 *pte = 00000000
[ 88.628483] Oops: 0000 [#1] SMP
[ 88.628490] Modules linked in: isight_firmware(+) hci_usb
cpufreq_ondemand cpufreq_performance cpufreq_powersave rfcomm hidp
l2cap bluetooth fan ipmi_watchdog ipmi_msghandler uvcvideo uinput
wlan_tkip ieee80211_crypt_tkip ieee80211_crypt arpt_mangle
arptable_filter arp_tables nf_conntrack_ipv4 nf_conntrack
iptable_mangle iptable_filter ip_tables x_tables i2c_i810 i2c_algo_bit
coretemp eeprom acpi_cpufreq fglrx(P) agpgart appletouch joydev
applesmc wlan_scan_sta firewire_ohci firewire_core ath_rate_sample
snd_hda_intel snd_pcm ath_pci ohci1394 snd_timer snd_page_alloc
snd_hwdep wlan ieee1394 ath_hal(P) evdev ehci_hcd uhci_hcd pata_acpi
button thermal video processor
[ 88.628581]
[ 88.628587] Pid: 2568, comm: modprobe Tainted: P
(2.6.26-rc4-00173-gd53a1a8 #6)
[ 88.628593] EIP: 0060:[<f8bc90f7>] EFLAGS: 00010207 CPU: 0
[ 88.628600] EIP is at isight_firmware_load+0xf2/0x1c3 [isight_firmware]
[ 88.628606] EAX: f2120150 EBX: 00000032 ECX: 0000000a EDX: c17f5638
[ 88.628610] ESI: f8dbf000 EDI: f2120158 EBP: f2111dac ESP: f2111d7c
[ 88.628615] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 88.628621] Process modprobe (pid: 2568, ti=f2110000 task=f5495380
task.ti=f2110000)
[ 88.628625] Stack: 00003def f2120150 f5728c90 00000578 f8dbeff8
c02b3854 f5728ff8 00006743
[ 88.628640] f492c700 f571ef50 f8bc97c4 f8bc9750 f2111dc8
c02b42d4 f5728c90 00000000
[ 88.628654] f571ef6c 00000000 f8bc9790 f2111ddc c026e58e
f571ef6c f571f054 f8bc9790
[ 88.628667] Call Trace:
[ 88.628676] [<c02b3854>] ? usb_autopm_do_device+0xb1/0xb9
[ 88.628694] [<c02b42d4>] ? usb_probe_interface+0xc0/0xee
[ 88.628707] [<c026e58e>] ? driver_probe_device+0xa0/0x11b
[ 88.628720] [<c026e646>] ? __driver_attach+0x3d/0x5f
[ 88.628731] [<c026ddea>] ? bus_for_each_dev+0x3b/0x5d
[ 88.628744] [<c026e425>] ? driver_attach+0x14/0x16
[ 88.628753] [<c026e609>] ? __driver_attach+0x0/0x5f
[ 88.628762] [<c026e180>] ? bus_add_driver+0x9a/0x1aa
[ 88.628775] [<c026e7c3>] ? driver_register+0x71/0xcd
[ 88.628783] [<c016427e>] ? __vunmap+0x93/0x9b
[ 88.628797] [<c02b3f01>] ? usb_register_driver+0x71/0xcb
[ 88.628808] [<f8be6017>] ? isight_firmware_init+0x17/0x19 [isight_firmware]
[ 88.628818] [<c0140d4a>] ? sys_init_module+0x163c/0x17ea
[ 88.628835] [<c020fe2e>] ? prio_tree_insert+0x1c/0x1cb
[ 88.628854] [<c0160f21>] ? vma_link+0xc0/0xce
[ 88.628866] [<c0161597>] ? mmap_region+0x2ca/0x377
[ 88.628877] [<c016ec1c>] ? __kmalloc+0x0/0xdb
[ 88.628905] [<c01038fa>] ? syscall_call+0x7/0xb
[ 88.628925] =======================
[ 88.628928] Code: e9 8e 00 00 00 83 7d d0 32 bb 32 00 00 00 0f 4e
5d d0 ba d0 00 00 00 89 d8 e8 32 5b 5a c7 89 d9 8b 75 e0 c1 e9 02 89
45 d4 89 c7 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 8b 45 d8 b9 a0 00 00 00
8b 10
[ 88.629002] EIP: [<f8bc90f7>] isight_firmware_load+0xf2/0x1c3
[isight_firmware] SS:ESP 0068:f2111d7c
[ 88.629015] ---[ end trace 0d6c893753a1cd98 ]---

like I said yesterday there was no problem at all, maybe because the
system was warm from being on all day.
after renaming isight_firmware.ko so I can boot up the system runs fine.
hope this helps in the kernel development.
regards;
--
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/