| Summary: | ASTERISK-00466: OOPS in Zaptel driver from latest CVS | ||
| Reporter: | thansen (thansen) | Labels: | |
| Date Opened: | 2003-10-30 14:59:15.000-0600 | Date Closed: | 2011-06-07 14:00:39 |
| Priority: | Blocker | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Using the zaptel driver from the latest cvs (as of 30th Oct. 03) kills my E400P. rmmod tor2 zaptel && modprobe tor2 causes a kernel panic / oops. The E400P is left in a dead state where only a coldboot can make it work again (with older zaptel driver). This is what I could retrieve from the logs: Loading the module: Oct 30 16:16:02 gw-1 kernel: Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xfebf8000/0xfebf7800 irq 16 Oct 30 16:16:02 gw-1 kernel: Timeout waiting for INIT and DONE to go low Oct 30 16:16:02 gw-1 kernel: Registered Tormenta2 PCI Unloading the modules: Oct 30 16:16:57 gw-1 kernel: Trying to free nonexistent resource <f70e4580-ee1c89ff> Oct 30 16:16:57 gw-1 kernel: Trying to free nonexistent resource <f70e4280-ee1c83ff> Oct 30 16:16:57 gw-1 kernel: Trying to free nonexistent resource <f70cfe80-ee19fbff> Oct 30 16:16:57 gw-1 kernel: Unregistered Tormenta2 Shortly after this point it froze. Normally the following is logged when loading the modules: Oct 30 16:27:41 gw-1 kernel: Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xfebf8000/0xfebf7800 irq 16 Oct 30 16:27:41 gw-1 kernel: Xilinx Chip successfully loaded, configured and started!! Oct 30 16:27:41 gw-1 kernel: Tormenta 2 Quad E1/PRA Card Oct 30 16:27:41 gw-1 kernel: Detected Card number: 0 Oct 30 16:27:41 gw-1 kernel: Tor2: Launching card: 0 Oct 30 16:27:41 gw-1 kernel: Registered Tormenta2 PCI | ||
| Comments: | By: Mark Spencer (markster) 2003-11-04 23:13:11.000-0600 This is a bad E400P card. Call DIgium to RMA it. | ||