Re: firewire disk stopped working

If you haven't already, boot back into the previous kernel environment
and let me know what revision of CURRENT it was that worked.

Then I'll need to know what version you were using that broke.

I'm trying to get my AMD64 system built this weekend to test things.

Sean


On Sun, 2009-02-15 at 00:12 +0200, Boris Kotzev wrote:
> My external firewire disk "Seagate FreeAgent Pro" stopped working with CURRENT 
> from today. It used to work without any problems before today's update.
> 
> After plugging the cable the following error messages begin scrolling on the 
> console continuously:
> 
> sbp0:0:0 sbp_scsi_status: unknown scsi status 0x0                                                                               
> sbp0:0:0 Obj: Data buffer, Error: Type error                                                                                    
> sbp0:0:0 sbp_scsi_status: unknown scsi status 0x0                                                                               
> sbp0:0:0 Obj: Data buffer, Error: Type error                                                                                    
> 
> They stop only after the cable is unplugged. 
> 
> Information about the system:
> 
> # uname -a
> FreeBSD zembla.universe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Feb 14 
> 22:06:57 EET 2009     [email protected]:/usr/obj/usr/src/sys/CUSTOM  amd64
> 
> The output from "pciconf -lv" is: 
> 
> # pciconf -lv
> fwohci0@pci0:3:3:0:     class=0x0c0010 card=0x581111c1 chip=0x581111c1 
> rev=0x61 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
> 
> The output from "fwcontrol" is:
> 
> # fwcontrol
> 2 devices (info_len=2)
> node           EUI64          status    hostname
>    0  00-1c-b3-ff-fe-98-73-de      0
>   -1  00-20-37-00-04-a0-34-21      0
> 
> Output from "fwcontrol -p" is:
> 
> # fwcontrol -p
> === base register ===          
> 0x61 0x05 0xe3 0x40 0xc0 0x03 0x00 0x20 
> Physical_ID:24  R:0  CPS:1              
> RHB:0  IBR:0  Gap_Count:5               
> Extended:7 Num_Ports:3                  
> 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:1 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 0 port 2 ===
> 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 0x61
> Compliance:1
> Vendor_ID:0x00601d
> 
> Is there any way to make the disk work again?
> 
> Sincerely,
> 
> Boris Kotzev
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
> To unsubscribe, send any mail to "[email protected]"

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "[email protected]"