Hi Below is a Oops of a crash that was reported to the linux1394-devel mailing list recently. My question is a general one, regarding the format of the Oops call trace. Taking the first line as an example : [d2235bc0] add_card+0x358/0xa4c [pcilynx] I understand that it references the add_card() function of the [pcilynx] driver. I assume the first number 0x358 is an offset from the start of the add_card() function. Correct ? But what does the second number 0xa4c represent ? I ask, because this format looks a bit different from the format I see in Oops from my own driver. E.g. [<f8a24d5d>] myfunc [mydriver] 0x290 (0xf23f9f38)) Thanks dom -----Original Message----- From: linux1394-devel-admin@lists.sourceforge.net [mailto:linux1394-devel-admin@lists.sourceforge.net] On Behalf Of Ben Collins Sent: Saturday, March 06, 2004 11:16 AM To: Olaf Hering Cc: linux1394-devel@lists.sourceforge.net Subject: Re: PCILynx driver on big-endian > pcilynx0: remapped memory spaces reg 0xd2222000, rom 0xd225d000, ram > 0xd223b000, aux 0xd224c000 Machine check in kernel mode. Caused by > (from SRR1=41030): Transfer error ack signal > Oops: machine check, sig: 7 [#1] > NIP: D2234164 LR: D2235BC0 SP: CB081B10 REGS: cb081a60 TRAP: 0200 Not tainted > MSR: 00041030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 > TASK = cf44da00[5313] 'modprobe' Last syscall: 128 > GPR00: 82000000 CB081B10 CF44DA00 FFFFFFFF 00000200 00000000 00000002 019D6412 > GPR08: 01A68BD1 D2222F0C 00000000 D2222000 C0290000 1001CDE0 00000001 00000000 > GPR16: 00000000 00000000 00000000 10001744 100189E0 100161CC 00000000 00000001 > GPR24: 10019400 00000000 00000000 CB00C000 00000005 C1878C00 00009032 CB00DC8C > Call trace: > [d2235bc0] add_card+0x358/0xa4c [pcilynx] > [c00d58f0] pci_device_probe_static+0x64/0x80 > [c00d595c] __pci_device_probe+0x50/0x70 > [c00d59ac] pci_device_probe+0x30/0x60 > [c00f8e70] bus_match+0x50/0x8c > [c00f8ff0] driver_attach+0x88/0xc8 > [c00f9388] bus_add_driver+0xa4/0xf4 > [c00f981c] driver_register+0x30/0x40 > [c00d5c3c] pci_register_driver+0x70/0xac > [d213f024] pcilynx_init+0x24/0xd0 [pcilynx] > [c0033824] sys_init_module+0x1ac/0x33c > [c000794c] ret_from_syscall+0x0/0x4c Hmm, I don't see this at all. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ mailing list linux1394-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux1394-devel -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
