>Number:         20266
>Category:       kern
>Synopsis:       ieee1212 code rejects a drive for an invalid checksum
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 09 09:53:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     seebs
>Release:        NetBSD 1.6N
>Organization:
>Environment:
System: NetBSD vash.cel.plethora.net 1.6N NetBSD 1.6N (VASH) #2: Sun Feb 9 09:45:10 CST 2003 seebs@vash.cel.plethora.net:/usr/src/sys/arch/i386/compile/VASH i386
Architecture: i386
Machine: i386
>Description:
	I have a drive which gets the following errors when connected via
	ieee1394:
Invalid registration tcode: 7
Invalid ROM -> 296: CRC: 0x1f4d, Calculated CRC: 0xb36d, CRC1: 0xd8f1
	
	I diked out the failure after the "Invalid ROM" line, and the drive
	works fine.
>How-To-Repeat:
	Get a weird little 2.5" external firewire drive case from ClubMac two
	years ago.

>Fix:
	It seems to me that perhaps the "invalid ROM" should be a warning,
	not an error.  If it's going to be an error, the message should
	get printed whether or not the user has defined P1212_DEBUG; any
	fatal error should at least be mentioned.

	However, it seems to me that, since I can just hook the drive up
	anyway, it's probably not really a fatal error; perhaps some vendors
	just used the wrong ROM algorithm two years ago.
>Release-Note:
>Audit-Trail:
>Unformatted: