[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problems compiling 2.6.26 kernel package on NSLU2 (Slug)

I'm getting rather frustrated trying to compile a new 2.6.26 kernel package for ARM (ixp42x) on my NSLU2. I need to upgrade as the stock 2.6.18 kernel does not support the cell modem I am trying to set up my slug as a gateway/router for.
I downloaded the following files from my friendly neighbourhood Debian mirror:
-rw-r--r-- 1 root root 7447271 Oct 26 18:13 linux-2.6_2.6.26-10~snapshot.12356.diff.gz -rw-r--r-- 1 root root 5813 Oct 26 18:13 linux-2.6_2.6.26-10~snapshot.12356.dsc 
-rw-r--r--  1 root root 61818969 Oct 26 18:14 linux-2.6_2.6.26.orig.tar.gz
Then, following http://www.nslu2-linux.org/wiki/Debian/BuildImage as a guide, and after dpkg-source -x'ing the .dsc, I did the following:
# fakeroot make -f debian/rules.gen setup_arm_none_ixp4xx >> ../kernel-build.log 2>&1 
# cd debian/build/build-arm_none_ixp4xx
# make ARCH=arm menuconfig
# (here, I configured kernel options)
# fakeroot make -f debian/rules.gen binary-arch_arm_none_ixp4xx >> ../kernel-build.log 2>&1
The kernel merrily built its way along for around 24-36 hours, then puked. The tail -30 of kernel-build.log is as follows: 

--------------SNIP------------------------------------
debugfs_remove module: vmlinux, version: 0x093f1d9c, export: EXPORT_SYMBOL_GPL debugfs_rename module: vmlinux, version: 0x45bd42ff, export: EXPORT_SYMBOL_GPL display_device_register module: drivers/video/display/display, version: 0xf2262dbd, export: EXPORT_SYMBOL display_device_unregister module: drivers/video/display/display, version: 0xca4d7488, export: EXPORT_SYMBOL free_user_ns module: vmlinux, version: 0x9f424093, export: EXPORT_SYMBOL get_dcookie module: vmlinux, version: 0x47699acc, export: EXPORT_SYMBOL_GPL gfs2_mount_lockproto module: fs/gfs2/gfs2, version: 0x6b108595, export: EXPORT_SYMBOL_GPL gfs2_register_lockproto module: fs/gfs2/gfs2, version: 0x945fbe65, export: EXPORT_SYMBOL_GPL gfs2_unmount_lockproto module: fs/gfs2/gfs2, version: 0xcf00e53c, export: EXPORT_SYMBOL_GPL gfs2_unregister_lockproto module: fs/gfs2/gfs2, version: 0x87596faf, export: EXPORT_SYMBOL_GPL gfs2_withdraw_lockproto module: fs/gfs2/gfs2, version: 0xdd48d17e, export: EXPORT_SYMBOL_GPL handle_sysrq module: vmlinux, version: 0xf925c050, export: EXPORT_SYMBOL null_ax25_address module: net/ax25/ax25, version: 0xd43ecbf1, export: EXPORT_SYMBOL profile_event_register module: vmlinux, version: 0x9159b9d6, export: EXPORT_SYMBOL_GPL profile_event_unregister module: vmlinux, version: 0x3c942368, export: EXPORT_SYMBOL_GPL register_sysrq_key module: vmlinux, version: 0x2ab12aa4, export: EXPORT_SYMBOL register_timer_hook module: vmlinux, version: 0xea3fffb0, export: EXPORT_SYMBOL_GPL selinux_secmark_refcount_dec module: vmlinux, version: 0xb65091b3, export: EXPORT_SYMBOL_GPL selinux_secmark_refcount_inc module: vmlinux, version: 0x80ee55c3, export: EXPORT_SYMBOL_GPL selinux_secmark_relabel_packet_permission module: vmlinux, version: 0x8039d043, export: EXPORT_SYMBOL_GPL selinux_string_to_sid module: vmlinux, version: 0x149db923, export: EXPORT_SYMBOL_GPL task_handoff_register module: vmlinux, version: 0x74abdafa, export: EXPORT_SYMBOL_GPL task_handoff_unregister module: vmlinux, version: 0xea065e01, export: EXPORT_SYMBOL_GPL touch_all_softlockup_watchdogs module: vmlinux, version: 0xfb0cf2e9, export: EXPORT_SYMBOL touch_softlockup_watchdog module: vmlinux, version: 0x6fcb87a1, export: EXPORT_SYMBOL unregister_sysrq_key module: vmlinux, version: 0x59833ba4, export: EXPORT_SYMBOL unregister_timer_hook module: vmlinux, version: 0xa95479e8, export: EXPORT_SYMBOL_GPL 
make[1]: *** [debian/stamps/build_arm_none_ixp4xx_kernel-package] Error 1
make[1]: Leaving directory `/mnt/disk1/usr/src/linux-2.6-2.6.26'
make: *** [binary-arch_arm_none_ixp4xx_real] Error 2
--------------SNIP------------------------------------
I have virtually no clue how to debug this. The last few lines say that the build process was working on the 'vmlinux' module... but 'vmlinux' refers to the kernel itself, not a specific driver, correct?
My only idea is that possibly the kernel was trying to build ax25 support into the kernel (and if so, it should be disabled anyways; I don't need ax25 support, and thought I disabled it) when it puked... But I could use any help I could get.
Any help that you could provide on debugging this issue would be greatly appreciated. Aside from removing ax25 support and trying again, I have no idea how to continue... 

--Jessica
Reply to: