linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Bromley <sbromley@cogeco.ca>
To: Ben Collins <bcollins@debian.org>
Cc: gaxt <gaxt@rogers.com>, Torrey Hoffman <thoffman@arnor.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux firewire devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Firewire (One fix worked, now getting oops)
Date: 26 Jul 2003 00:41:18 -0400	[thread overview]
Message-ID: <1059194478.655.49.camel@daedalus.samhome.net> (raw)
In-Reply-To: <20030725201128.GA535@phunnypharm.org>

On Fri, 2003-07-25 at 16:11, Ben Collins wrote:
> On Fri, Jul 25, 2003 at 12:35:15PM -0700, Chris Ruvolo wrote:
> > On Fri, Jul 25, 2003 at 02:45:06PM -0400, Ben Collins wrote:
> > > Maybe it wont. Try reverting back to stock, and apply this patch. I am
> > > pretty sure this will fix the problem for anyone having this issue.
> > 
> > Yes, I think this did it!  One change: needed to change HSBP_VERBOSE to
> > HSBP_DEBUG in csr.c.  
> > 
> > I will try turning on my DV camera tonight (I'm remote now) and I'll let you
> > know how that goes.
> 
> Kick ass. I've commited this change to the 1394 repo. Linus will get the
> fix soon. I'll also send it to Marcelo for 2.4.22.
> 
> Please, if you are testing, use the code at www.linux1394.org's viewcvs
> (trunk tarball will replace drivers/ieee1394 in 2.6, branches/linux-2.4
> will do the same for 2.4).
> 
> 
> Thanks for help in tracking this down.

Hi,
First, thank you all for being so diligent.
The unsolicited packet problem seems to have
been resolved. However, by running gscanbus,
then unplugging a camera and replugging it in,
I got the following oops:

Unable to handle kernel paging request at virtual address 08103a8c
 printing eip:
402fd1de
*pde = 07b1c067
*pte = 00000000
Oops: 0006 [#1]
CPU:    0
EIP:    0073:[<402fd1de>]    Not tainted
EFLAGS: 00010202
EIP is at 0x402fd1de
eax: 00001579   ebx: 4039ff60   ecx: 00001009   edx: 08103a88
esi: 00000004   edi: 00000000   ebp: bfffc788   esp: bfffc760
ds: 007b   es: 007b   ss: 007b
Process gscanbus (pid: 2525, threadinfo=c2314000 task=dc4af000)
 <6>note: gscanbus[2525] exited with preempt_count 1

-----------
Ok, you'll have to forgive me here, as I've never used
ksymoops before, but here is my attempt:


ksymoops 2.4.8 on i686 2.6.0-test1-ac1.  Options used
     -v /boot/vmlinuz-2.6.0-test1-ac2 (specified)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.6.0-test1-ac1/ (default)
     -m /boot/System.map-2.6.0-test1-ac2 (specified)

/usr/bin/nm: /boot/vmlinuz-2.6.0-test1-ac2: File format not recognized
Error (pclose_local): read_nm_symbols pclose failed 0x100
Warning (read_vmlinux): no kernel symbols in vmlinux, is
/boot/vmlinuz-2.6.0-test1-ac2 a valid vmlinux file?
Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Reading Oops report from the terminal
402fd1de
*pde = 07b1c067
*pte = 00000000
Oops: 0006 [#1]
CPU:    0
EIP:    0073:[<402fd1de>]    Not tainted
EFLAGS: 00010202
EIP is at 0x402fd1de
eax: 00001579   ebx: 4039ff60   ecx: 00001009   edx: 08103a88
esi: 00000004   edi: 00000000   ebp: bfffc788   esp: bfffc760
ds: 007b   es: 007b   ss: 007b
Process gscanbus (pid: 2525, threadinfo=c2314000 task=dc4af000)
 <6>note: gscanbus[2525] exited with preempt_count 1
402fd1de
*pde = 07b1c067
Oops: 0006 [#1]
CPU:    0
EIP:    0073:[<402fd1de>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 00001579   ebx: 4039ff60   ecx: 00001009   edx: 08103a88
esi: 00000004   edi: 00000000   ebp: bfffc788   esp: bfffc760
ds: 007b   es: 007b   ss: 007b

Warning (Oops_read): Code line not seen, dumping what data is available


>>EIP; 402fd1de <__crc_param_set_short+2b6895/75bf8f>   <=====

>>ebx; 4039ff60 <__crc_param_set_short+359617/75bf8f>
>>edx; 08103a88 <__crc_ip_finish_output+23c39/133bb1>
>>ebp; bfffc788 <__crc_class_device_add+4dfb67/51fa16>
>>esp; bfffc760 <__crc_class_device_add+4dfb3f/51fa16>


2 warnings and 2 errors issued.  Results may not be reliable.

--------
Please point me to a quick reference to the proper
usage of ksymoops if this info is at your finger tips.

Since I see the preempt bit above, I'll try compiling
without a preemtible kernel and will report the results
tomorrow.

Cheers,
Sam.





  parent reply	other threads:[~2003-07-26  4:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 13:34 Firewire gaxt
2003-07-24 22:35 ` Firewire Chris Ruvolo
2003-07-24 22:36   ` Firewire Ben Collins
2003-07-24 23:09     ` Firewire Chris Ruvolo
2003-07-24 23:14       ` Firewire Ben Collins
2003-07-24 23:48         ` Firewire Chris Ruvolo
2003-07-24 23:45           ` Firewire Ben Collins
2003-07-25  0:07             ` Firewire Chris Ruvolo
2003-07-25  0:14           ` Firewire Chris Ruvolo
2003-07-25  1:13       ` Firewire Torrey Hoffman
2003-07-25  1:27         ` Firewire Chris Ruvolo
2003-07-25  1:29           ` Firewire Ben Collins
2003-07-25  2:00             ` Firewire Chris Ruvolo
2003-07-25  2:19               ` Firewire Ben Collins
2003-07-25  3:23             ` Firewire Sam Bromley
2003-07-25  4:12               ` Firewire Ben Collins
2003-07-25  5:39                 ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins
2003-07-25 14:06                     ` Firewire gaxt
2003-07-25 13:47                       ` Firewire Ben Collins
2003-07-25 14:23                         ` Firewire gaxt
2003-07-25 15:28                           ` Firewire gaxt
2003-07-25 14:29                     ` Firewire Chris Ruvolo
2003-07-25 14:29                       ` Firewire Ben Collins
2003-07-25 15:40                         ` Firewire Ben Collins
2003-07-25 16:07                           ` Firewire Chris Ruvolo
2003-07-25 16:18                             ` Firewire Ben Collins
2003-07-25 17:02                               ` Firewire Chris Ruvolo
2003-07-25 17:07                                 ` Firewire Ben Collins
2003-07-25 17:51                               ` Firewire Torrey Hoffman
2003-07-25 18:13                                 ` Firewire Chris Ruvolo
2003-07-25 18:12                                   ` Firewire Ben Collins
2003-07-25 18:43                                     ` Firewire gaxt
2003-07-25 18:26                                       ` Firewire Ben Collins
2003-07-25 18:45                                         ` Firewire Ben Collins
2003-07-25 19:16                                           ` Firewire gaxt
2003-07-25 19:35                                           ` Firewire Chris Ruvolo
2003-07-25 20:11                                             ` Firewire Ben Collins
2003-07-25 21:48                                               ` Firewire gaxt
2003-07-26  4:41                                               ` Sam Bromley [this message]
2003-07-26 15:12                                                 ` Firewire (One fix worked, now getting oops) Ben Collins
2003-07-26 17:41                                                   ` Sam Bromley
2003-07-26 17:45                                                     ` Ben Collins
2003-07-26 16:52                                               ` Firewire Chris Ruvolo
2003-07-26 17:45                                                 ` Firewire Ben Collins
2003-07-25 20:48                                             ` Firewire Torrey Hoffman
2003-07-25 20:44                                               ` Firewire Ben Collins
2003-07-25 18:18                                   ` Firewire Torrey Hoffman
2003-07-25 18:33                                   ` Firewire gaxt
2003-07-25 16:28                           ` Firewire gaxt
2003-07-25 15:53                         ` Firewire Chris Ruvolo
2003-07-25 15:47                           ` Firewire Ben Collins
2003-07-25 16:14                             ` Firewire Chris Ruvolo
2003-07-25 13:34                   ` Firewire Ben Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1059194478.655.49.camel@daedalus.samhome.net \
    --to=sbromley@cogeco.ca \
    --cc=bcollins@debian.org \
    --cc=gaxt@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=thoffman@arnor.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).