Re: fwohci0: panic: blockable sleep lock (sleep mutex ) Giant @ /usr/src/sys/dev/kbdmux/kbdmux.c:1103

Sean Bruno <[email protected]>
Newsgroups gmane.os.freebsd.devel.firewire
Message-ID <[email protected]>
On Fri, 2009-02-13 at 02:41 -0600, Chris Ruiz wrote:
> On Feb 10, 2009, at 10:14 PM, Sean Bruno wrote:
> 
> > On Tue, 2009-02-10 at 20:48 -0600, Chris Ruiz wrote:
> >>
> >> After 11 days of uptime, I typed 'fwcontrol -p' from a ssh session  
> >> and
> >> my system rebooted.  This is all the information I could obtain.
> >> After reboot, fwcontrol did not cause another panic.  I do no have  
> >> any
> >> swap nor did I get a chance to enter the debugger before the reboot.
> >> I'm currently in the process of updating to 188474 and will report
> >> back if this happens again.
> >>
> >
> >
> > Ah ... finally, an AMD64 reporter.  <grins evilly>
> >
> > Let's break this down a bit, what Firewire card do you have(pciconf - 
> > lv)
> 
> fwohci0@pci0:6:3:0:     class=0x0c0010 card=0x581111c1 chip=0x581111c1  
> rev=0x70 hdr=0x00
>      vendor     = 'Lucent/Agere Systems (Was: AT&T MicroElectronics)'
>      device     = 'FW322 1394A PCI PHY/Link Open Host Ctrlr I/F'
>      class      = serial bus
>      subclass   = FireWire
> 
> This "card" is built onto my motherboard.
> 
> > What Firewire device was attached to the box?
> 
> Don't laugh, there were no devices attached when the kernel paniced.
> 
> > What is the output of "fwcontrol -p" and "fwcontrol"?
> 
> # fwcontrol -p
> === base register ===
> 0x05 0x05 0xe2 0x40 0xc0 0x03 0x00 0x00
> Physical_ID:1  R:0  CPS:1
> RHB:0  IBR:0  Gap_Count:5
> Extended:7 Num_Ports:2
> PHY_Speed:2 Delay:0
> LCtrl:1 C:1 Jitter:0 Pwr_Class:0
> WDIE:0 ISBR:0 CTOI:0 CPSI:0 STOI:0 PEI:0 EAA:1 EMC:1
> Max_Legacy_SPD:0 BLINK:0 Bridge:0
> Page_Select:0 Port_Select0
> 
> === page 0 port 0 ===
> 0xf8 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> Astat:3 BStat:3 Ch:1 Con:0 RXOK:0 Dis:0
> Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0
> DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0
> Connection_unreliable:0 Beta_mode:0
> Port_error:0x0
> Loop_disable:0 In_standby:0 Hard_disable:0
> 
> === page 0 port 1 ===
> 0xf8 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> Astat:3 BStat:3 Ch:1 Con:0 RXOK:0 Dis:0
> Negotiated_speed:0 PIE:0 Fault:0 Stanby_fault:0 Disscrm:0 B_Only:0
> DC_connected:0 Max_port_speed:0 LPP:0 Cable_speed:0
> Connection_unreliable:0 Beta_mode:0
> Port_error:0x0
> Loop_disable:0 In_standby:0 Hard_disable:0
> 
> === page 1 ===
> 0x01 0x00 0x00 0x60 0x1d 0x03 0x23 0x70
> Compliance:1
> Vendor_ID:0x00601d
> Product_ID:0x032370
> 
> # fwcontrol
> 1 devices (info_len=1)
> node           EUI64          status    hostname
>     0  00-90-27-00-01-d0-dc-04      0
> 
> I did plug in my 3g iPod and caught a bunch of error messages.  Last  
> time I used my iPod on fbsd was probably back a couple years ago when  
> 6 became STABLE and it worked.  My iPod works fine with iTunes on OSX  
> and  with my car's headunit's iPod controller.
> 
> Feb 13 02:33:59 attack kernel: fwohci0: fwohci_intr_core: BUS reset
> Feb 13 02:33:59 attack kernel: fwohci0: fwohci_intr_core:  
> node_id=0x00000001, SelfID Count=3, CYCLEMASTER mode
> Feb 13 02:33:59 attack kernel: firewire0: 2 nodes, maxhop <= 1, cable  
> IRM = 1 (me)
> Feb 13 02:33:59 attack kernel: firewire0: bus manager 1 (me)
> Feb 13 02:33:59 attack kernel: firewire0: New S400 device ID: 
> 000a270002593efd
> Feb 13 02:34:00 attack kernel: sbp0:0:0 No additional information to  
> report
> Feb 13 02:34:03 attack last message repeated 7 times
> Feb 13 02:34:03 attack kernel: da1 at sbp0 bus 0 target 0 lun 0
> Feb 13 02:34:03 attack kernel: da1: <Apple Co iPod 2700> Removable  
> Simplified Direct Access SCSI-2 device
> Feb 13 02:34:03 attack kernel: da1: 50.000MB/s transfers
> Feb 13 02:34:03 attack kernel: da1: 19073MB (39063024 512 byte  
> sectors: 255H 63S/T 2431C)
> Feb 13 02:34:05 attack kernel: sbp0:0:0 Request aborted
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): READ(10). CDB: 28 0 0  
> 0 0 1 0 0 1 0
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): CAM Status: SCSI  
> Status Error
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): SCSI Status: Check  
> Condition
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): MEDIUM ERROR  
> info?:dec0adde csi:de,c0,ad,de asc:0,0
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): No additional sense  
> information
> Feb 13 02:34:05 attack kernel: (da1:sbp0:0:0:0): Retrying Command (per  
> Sense Data)
> Feb 13 02:34:06 attack kernel: sbp0:0:0 Request aborted
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): READ(10). CDB: 28 0 0  
> 0 0 1 0 0 1 0
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): CAM Status: SCSI  
> Status Error
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): SCSI Status: Check  
> Condition
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): MEDIUM ERROR  
> info?:dec0adde csi:de,c0,ad,de asc:0,0
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): No additional sense  
> information
> Feb 13 02:34:06 attack kernel: (da1:sbp0:0:0:0): Retrying Command (per  
> Sense Data)
> 
> These messages will continue on until i unplug my iPod.
> 
> Feb 13 02:34:54 attack kernel: fwohci0: fwohci_intr_core: BUS reset
> Feb 13 02:34:54 attack kernel: fwohci0: fwohci_intr_core:  
> node_id=0x00000000, SelfID Count=4, CYCLEMASTER mode
> Feb 13 02:34:54 attack kernel: firewire0: 1 nodes, maxhop <= 0, cable  
> IRM = 0 (me)
> Feb 13 02:34:54 attack kernel: firewire0: bus manager 0 (me)
> Feb 13 02:34:55 attack kernel: (da1:sbp0:0:0:0): lost device
> Feb 13 02:34:55 attack kernel: (da1:sbp0:0:0:0): Synchronize cache  
> failed, status == 0x8, scsi status == 0x0
> Feb 13 02:34:55 attack kernel: (da1:sbp0:0:0:0): removing device entry
> 

Hrm ... Ok.  Any chance that the iPod is an 800 capable device?  If it
is, I'll have a patch for you.

Sean

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.