linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gaxt <gaxt@rogers.com>
To: Ben Collins <bcollins@debian.org>
Cc: Torrey Hoffman <thoffman@arnor.net>,
	Sam Bromley <sbromley@cogeco.ca>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux firewire devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: Firewire
Date: Fri, 25 Jul 2003 15:16:52 -0400	[thread overview]
Message-ID: <3F218224.8030807@rogers.com> (raw)
In-Reply-To: <20030725184506.GE607@phunnypharm.org>

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.
> 
> Index: linux-2.6/drivers/ieee1394/ieee1394_core.c

...

root@localhost linux # make modules modules_install
...
drivers/ieee1394/csr.c: In function `calculate_expire':
drivers/ieee1394/csr.c:120: warning: implicit declaration of function 
`HPSB_VERBOSE'
...
   Building modules, stage 2.
   MODPOST
*** Warning: "HPSB_VERBOSE" [drivers/ieee1394/ieee1394.ko] undefined!
   LD [M]  drivers/ieee1394/dv1394.ko
...

root@localhost linux # modprobe ieee1394
FATAL: Error inserting ieee1394 
(/lib/modules/2.6.0-test1-mm2/kernel/drivers/ieee1394/ieee1394.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)

...

dmesg:

ieee1394: NodeMgr: Exiting thread
ohci1394_0: Soft reset finished
ohci1394_0: Freeing dma_rcv_ctx 0
ohci1394_0: Freeing dma_rcv_ctx 0
ohci1394_0: Freeing dma_trm_ctx 0
ohci1394_0: Freeing dma_trm_ctx 1
raw1394: /dev/raw1394 device initialized
ohci1394: $Rev$ Ben Collins <bcollins@debian.org>
ohci1394_0: Remapped memory spaces reg 0xd093f800
ohci1394_0: Soft reset finished
ohci1394_0: Iso contexts reg: 000000a8 implemented: 0000000f
ohci1394_0: 4 iso receive contexts available
ohci1394_0: Iso contexts reg: 00000098 implemented: 000000ff
ohci1394_0: 8 iso transmit contexts available
ohci1394_0: GUID: 060050c5:000001ce
ohci1394_0: Receive DMA ctx=0 initialized
ohci1394_0: Receive DMA ctx=0 initialized
ohci1394_0: Transmit DMA ctx=0 initialized
ohci1394_0: Transmit DMA ctx=1 initialized
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[5]  MMIO=[cfffc800-cfffcfff]  Max 
Packet=[2048]
ohci1394_0: request csr_rom address: c3efa000
ohci1394_0: IntEvent: 00020010
ohci1394_0: irq_handler: Bus reset requested
ohci1394_0: Cancel request received
ieee1394: TLABEL: splicing pending packets for abort_requests
ohci1394_0: Got RQPkt interrupt status=0x00008409
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 ... discarded
ohci1394_0: IntEvent: 00010000
ohci1394_0: SelfID interrupt received (phyid 0, root)
ohci1394_0: SelfID packet 0x807f8c56 received
ieee1394: Including SelfID 0x568c7f80
ohci1394_0: SelfID for this node is 0x807f8c56
ohci1394_0: SelfID complete
ohci1394_0: PhyReqFilter=ffffffffffffffff
ieee1394: selfid_complete called with successful SelfID stage ... 
irm_id: 0xFFC0 node_id: 0xFFC0
ieee1394: NodeMgr: Processing host reset for knodemgrd_0
ieee1394: Initiating ConfigROM request for node 0-00:1023
ieee1394: send packet local: ffc00140 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: received packet: ffc00140 ffc0ffff f0000400
ieee1394: send packet local: ffc00160 ffc00000 00000000 dee10404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00160 ffc00000 00000000 dee10404
ieee1394: TLABEL: Checking for tlabel 0
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00160 ffc00000 00000000 dee10404
ieee1394: send packet local: ffc00540 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: received packet: ffc00540 ffc0ffff f0000400
ieee1394: send packet local: ffc00560 ffc00000 00000000 dee10404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00560 ffc00000 00000000 dee10404
ieee1394: TLABEL: Checking for tlabel 1
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00560 ffc00000 00000000 dee10404
ieee1394: send packet local: ffc00940 ffc0ffff f0000400
ieee1394: TLABEL: appending packet to pending list
ieee1394: TLABEL: packet removed in abort_timedouts
ieee1394: received packet: ffc00940 ffc0ffff f0000400
ieee1394: send packet local: ffc00960 ffc00000 00000000 dee10404
ieee1394: TLABEL: no_waiter, returning
ieee1394: received packet: ffc00960 ffc00000 00000000 dee10404
ieee1394: TLABEL: Checking for tlabel 2
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: contents: ffc00960 ffc00000 00000000 dee10404
ieee1394: ConfigROM quadlet transaction error for node 0-00:1023
ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 1f0000c0
ohci1394_0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0, 
speed=0
ohci1394_0: Starting transmit DMA ctx=0
ohci1394_0: IntEvent: 00000001
ohci1394_0: Got reqTxComplete interrupt status=0x00008011
ohci1394_0: Packet sent to node 63 tcode=0x0 tLabel=0x00 ack=0x11 spd=0 
data=0x1F0000C0 ctx=0
ieee1394: TLABEL: not pending or no response expected, returning
bad: scheduling while atomic!
Call Trace:
  [<c01178e6>] schedule+0x3f6/0x400
  [<c0116c7e>] try_to_wake_up+0x9e/0x180
  [<c0117c41>] wait_for_completion+0x91/0x110
  [<c0117950>] default_wake_function+0x0/0x30
  [<c0117950>] default_wake_function+0x0/0x30
  [<c0124d02>] kill_proc_info+0x62/0x70
  [<d0aab945>] nodemgr_remove_host+0x55/0xa0 [ieee1394]
  [<d0aa70cc>] highlevel_remove_host+0x6c/0x80 [ieee1394]
  [<d094c521>] ohci1394_pci_remove+0x41/0x230 [ohci1394]
  [<c021eabb>] pci_device_remove+0x3b/0x40
  [<c0285436>] device_release_driver+0x66/0x70
  [<c0285460>] driver_detach+0x20/0x30
  [<c02856bd>] bus_remove_driver+0x3d/0x80
  [<c0285af3>] driver_unregister+0x13/0x28
  [<c021ed96>] pci_unregister_driver+0x16/0x30
  [<d094c9df>] ohci1394_cleanup+0xf/0x13 [ohci1394]
  [<c012fdf2>] sys_delete_module+0x152/0x1c0
  [<c0144100>] do_munmap+0x130/0x190
  [<c010921b>] syscall_call+0x7/0xb

ieee1394: NodeMgr: Exiting thread
ohci1394_0: Soft reset finished
ohci1394_0: Freeing dma_rcv_ctx 0
ohci1394_0: Freeing dma_rcv_ctx 0
ohci1394_0: Freeing dma_trm_ctx 0
ohci1394_0: Freeing dma_trm_ctx 1
ieee1394: Unknown symbol HPSB_VERBOSE
root@localhost linux #



  reply	other threads:[~2003-07-25 18:50 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                                           ` gaxt [this message]
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                                               ` Firewire (One fix worked, now getting oops) Sam Bromley
2003-07-26 15:12                                                 ` 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=3F218224.8030807@rogers.com \
    --to=gaxt@rogers.com \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=sbromley@cogeco.ca \
    --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).