^
Advanced Search

AR# 30382 Platform Cable USB Install - System exhibits kernel panic when installing cable drivers on Linux

Description

Keywords: hang, severe, start-up

During installation of the cable drivers, my Linux machine does not boot up completely and generates kernel panic messages. The kernel log contains failure information when loading the drivers that is similar to the following message:

"EFLAGS: 00210296 (2.6.9-42.0.8.EL)
Feb 5 13:17:11 isg-grad-02 kernel: EIP is at LINUX_memset+0x10/0x1b [windrvr6]
Feb 5 13:17:11 isg-grad-02 kernel: eax: 00008d00 ebx: f0814000 ecx: 00007d6c edx: 00000101
Feb 5 13:17:12 isg-grad-02 kernel: esi: 00008d6c edi: f0815000 ebp: e150bf74 esp: e150bf6c
Feb 5 13:17:12 isg-grad-02 kernel: ds: 007b es: 007b ss: 0068
Feb 5 13:17:12 isg-grad-02 kernel: Process modprobe (pid: 8315, threadinfo=e150b000 task=dcff8250)
Feb 5 13:17:12 isg-grad-02 kernel: Stack: e150bfac c036c2a0 e150bfac f0bba47c f0814000 00000000 00008d6c c036c2e0
Feb 5 13:17:12 isg-grad-02 kernel: f0bdcf80 f0bbbcbc 00008d6c f0bbbc04 f0bcf9ce f0bd0280 f0bb7d41 c036c2e0
Feb 5 13:17:12 isg-grad-02 kernel: e150b000 c01410b6 b7f1c008 096c3c58 00c3f33a c0318eeb b7f1c008 0002e89a
Feb 5 13:17:12 isg-grad-02 kernel: Call Trace:
Feb 5 13:17:12 isg-grad-02 kernel: [<f0bba47c>] zalloc_mem+0x1c/0x30 [windrvr6]
Feb 5 13:17:12 isg-grad-02 kernel: [<f0bbbcbc>] WinDriver_init+0x1c/0x200 [windrvr6]
Feb 5 13:17:12 isg-grad-02 kernel: [<f0bbbc04>] init_module_cpp+0x14/0x80 [windrvr6]
Feb 5 13:17:12 isg-grad-02 kernel: [<f0bb7d41>] init_module+0x9/0x5d [windrvr6]
Feb 5 13:17:12 isg-grad-02 kernel: [<c01410b6>] sys_init_module+0xe9/0x1d0
Feb 5 13:17:12 isg-grad-02 kernel: [<c0318eeb>] syscall_call+0x7/0xb
Feb 5 13:17:12 isg-grad-02 kernel: Code: 0c 8b 4d 10 49 78 08 ac ae 75 08 84 c0 75 f5 31 c0 eb 04 19 c0 0c 01 5e 5f c9 c3 55 89 e5 57 83 ec 04 8b 4d 10 8a 45 0c 8b 7d 08 <f3> aa 8b 45 08 83 c4 04 5f c9 c3 55 89 e5 57 56 83 ec 04 8b 75
Feb 5 13:17:12 isg-grad-02 kernel: <0>Fatal exception: panic in 5 seconds"


When this problem occurs, the system becomes unusable. The incorrectly built drivers must be removed to make the system usable again, and allow the installation of the updated drivers.

Solution

This issue occurs if the ARCH environment variable is set to i686 on a 32-bit Linux machine. To resolve this issue, you must first boot the machine exhibiting the kernel panic in safe mode to bypass loading the Jungo WinDrivers. You can then remove the drivers from /lib/modules. Follow these steps to recover from the system failure and allow the proper building of the drivers:

1. Boot from a Linux Live CD.
2. Mount the system root directory and remove the cable driver modules. For example, if the system root directory ?/? is in the /dev/sda1 hard drive partition, run the following commands:
a. mkdir /mnt/test_root
b. mount /dev/sda1 /mnt/test_root
c. rm ?f /mnt/test_root//lib/modules/[linux_kernel_version]/kernel/drivers/misc/windrvr6.*
d. rm ?f /mnt/test_root//lib/modules/[linux_kernel_version]/kernel/drivers/misc/xpc4drvr.*

The [linux_kernel_version] in steps c and d refers to the installed kernel version.

3. Remove the Live CD from the drive and reboot the system.
4. Reinstall the drivers by following the steps in (Xilinx Answer 22648)

After rebooting in regular mode, you should unset the ARCH environment variable and install the cable drivers.

Actions

AR# 30382
Date Created 02/25/2008
Last Updated 03/28/2008
Status Active
Type
Feed Back