Thread: 1394 Kernel panic on 2.4.0
Brought to you by:
aeb,
bencollins
From: Karthik M. <kma...@ho...> - 2001-01-12 03:32:27
|
Summary of my setup: kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible PCMCIA 1394 adapter, 1394 drivers from kernel tree. No signs of trouble after boot in syslog and /proc/pci lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded When I switch on my camcorder, an oops followed by a kernel panic occurs. Same if the camcorder is on when I boot. I tried compiling the latest driver sources from CVS. They do not compile as they are, since a struct definition seems to have changed. I had to edit guid.c and ohci1394.c to replace a couple of lines of the form xxx->tq.next = NULL; with INIT_LIST_HEAD(xxx->tq.list); I made the edits based on a diff of the kernel version with the downloaded version. With those changes, the drivers compile, but the panic still occurs, so those changes in the kernel driver sources may be part of the problem. Can anyone suggest anything? (I've just joined the list and the archives only go till Dec 15, so I don't know if this has been discussed here before) Thanks, Karthik |
From: Jeff L. <Jeff.Lessem@Colorado.EDU> - 2001-01-12 03:55:08
|
I too am having the same problem with my camcorder and 2.4.0. The problem also occured with 2.4.0-prerelease, if it makes any difference. I am using a TI TSB12LV23 based OHCI Compliant card. If it would be helpful I can try to capture the oops and panic. This will be difficult because the machine hangs, so I will have to attach a serial console, etc. so I don't want to do this unless it will help with debugging. In your message of: Thu, 11 Jan 2001 21:46:40 CST, you write: >Summary of my setup: >kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible >PCMCIA 1394 adapter, 1394 drivers from kernel tree. > >No signs of trouble after boot in syslog and /proc/pci > >lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > >When I switch on my camcorder, an oops followed by a kernel panic >occurs. Same if the camcorder is on when I boot. |
From: scott w. <swo...@ho...> - 2001-01-12 04:11:44
|
On Thu, Jan 11, 2001 at 08:55:31PM -0700, Jeff Lessem wrote: > I too am having the same problem with my camcorder and 2.4.0. The > problem also occured with 2.4.0-prerelease, if it makes any > difference. I am using a TI TSB12LV23 based OHCI Compliant card. > > If it would be helpful I can try to capture the oops and panic. This > will be difficult because the machine hangs, so I will have to attach > a serial console, etc. so I don't want to do this unless it will help > with debugging. > > In your message of: Thu, 11 Jan 2001 21:46:40 CST, you write: > >Summary of my setup: > >kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible > >PCMCIA 1394 adapter, 1394 drivers from kernel tree. > > > >No signs of trouble after boot in syslog and /proc/pci > > > >lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > > > > >When I switch on my camcorder, an oops followed by a kernel panic > >occurs. Same if the camcorder is on when I boot. > > I have the same problem with a SIIG TI based 1394 card, Pyro WebCam and kernel 2.4.0. I have even tried Alan Cox's AC2 patch which has an update to ohci1394 with no luck. I haven't tried compiling the kernel with the Magic SysRequest option to try and recover from the OOP's. There a doc in linux/Documentation which talks about how to debug OOPs. Have you tried the 2.2.18 kernel + 1394 patch? That's what I am currently running and no OOPs. Modules load fine and it is able to talk to the device. Of course I don't have any software which works with the WebCam yet. good luck. scott worley swo...@ho... |
From: Perry G. <pe...@gi...> - 2001-01-12 04:16:39
|
Karthik, Jeff, Look at ieee1394_core.c:343, you will see a call to highlevel_host_reset(host); This function hasn't been implemented yet, so just cut or comment the line out. I made a tiny script, Pray, that does "sync; sleep 3; sync", so I always have a moment of silent meditation when loading unknown modules. Regards, Perry ======= What other people wrote about this subject on the ========== ======= lin...@li... list ========== Sebastien, just a quick note that I had the same result as you with 2.4.0. I commented out the call you refrence, and the pcilynx driver behaves pretty much the same as 2.2.18 with the CVS drivers. Still got troubles, but the machine doesn't die since you were quick to find the problem. Regards, Perry Sebastien Rougeaux wrote: > I think I found the problem. > > in ieee_core.c, there is a call to highlevel_host_reset(), which is > a function that is not defined. > > Andreas, why is there a call to such function ? Can you modify that > and see if it solves the problem with 2.4.0 kernel (seems to work > for me). > > Cheers, > > Sebastien Rougeaux Karthik Madathil wrote: > Summary of my setup: > kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible > PCMCIA 1394 adapter, 1394 drivers from kernel tree. > > No signs of trouble after boot in syslog and /proc/pci > > lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > When I switch on my camcorder, an oops followed by a kernel panic > occurs. Same if the camcorder is on when I boot. > > I tried compiling the latest driver sources from CVS. They do not > compile > as they are, since a struct definition seems to have changed. I had to > edit guid.c and ohci1394.c to replace a couple of lines of the form > xxx->tq.next = NULL; > with > INIT_LIST_HEAD(xxx->tq.list); > I made the edits based on a diff of the kernel version with the > downloaded > version. > > With those changes, the drivers compile, but the panic still occurs, so > those changes in the kernel driver sources may be part of the problem. > > Can anyone suggest anything? > > (I've just joined the list and the archives only go till Dec 15, so I > don't > know if this has been discussed here before) > > Thanks, > Karthik > |