Messages in this thread | | | Date | Tue, 24 Feb 2004 05:58:10 -0800 | From | "Jim Deas" <> |
| |
Can someone point me in the right direction. I am getting a oops on a driver I am porting from 2.4 to 2.6.2 kernel. I have expanded the file_operations structures and have a driver that loads and inits the hardware but when I call the open function I get an oops. The best I can track it is
EIP 0060:[c0188954] chrdev_open +0x104
What is the best debug tool to put this oops information in clear sight? It appears to never get to my modules open routine so I am at a debugging crossroad. What is the option on a kernel compile to get the compile listing so I can see what is at 0x104 in this block of code?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |