stonewall@xxxxxxxxxxxxx wrote: > Using the 2.6.12.2 kernel, and the new flexcop driver, when I go to bring my > devices down so they can be unloaded (for reboot or otherwise), the: > > ifconfig <dev> down > > On the last device locks at the ifconfig. It doesn't lock the machine, and if > this is being done from command line, it can be Ctrl-C out of . . . but is > problematic for reboots. > > This is using the B2C2 skystar2 card, using the latest b2c2_flexcop drivers on > the 2.6.12 kernel. I have created several dvb0_? devices for different PIDs. > And it's always the *last* one that does the lock at ifconfig down. This did > not occur with 2.6.11.11. You could build your kernel with CONFIG_MAGIC_SYSRQ=y, CONFIG_FRAME_POINTER=y and CONFIG_KALLSYMS_ALL=y, and when ifconfig hands press SysRq-T and post the calltrace of ifconfig (from dmesg output). Then we could see where it hangs. Johannes
