kern/158268: ata: SIGNATURE: ffffffff with Promise PDC40718

George Kontostanos gkontos.mail at gmail.com
Fri Jun 24 23:30:09 UTC 2011


>Number:         158268
>Category:       kern
>Synopsis:       ata: SIGNATURE: ffffffff with Promise PDC40718
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 24 23:30:08 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     George Kontostanos
>Release:        8.2-Stable
>Organization:
>Environment:
FreeBSD hp.aicom.loc 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Jun  6 19:00:19 EEST 2011     gkontos at hp.aicom.loc:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Using a SATA Promise PDC40718 controller with FreeBSD 8.2-Release and 8.2-Stable causes the following messages to appear:

Jun 22 17:08:53 hp kernel: ata2: timeout waiting to issue command
Jun 22 17:08:53 hp kernel: ata2: error issuing SETFEATURES ENABLE WCACHE command
Jun 22 17:09:33 hp kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Jun 22 17:09:33 hp kernel: ad4: WARNING - WRITE_DMA48 requeued due to channel reset LBA=321558741
Jun 22 17:09:34 hp kernel: ata2: SIGNATURE: 00000101
Jun 22 17:09:34 hp kernel: ad4: WARNING - WRITE_DMA48 requeued due to channel reset LBA=321558869
Jun 22 17:09:34 hp kernel: ata2: FAILURE - already active DMA on this device
Jun 22 17:09:34 hp kernel: ata2: setting up DMA failed
Jun 22 17:09:34 hp kernel: ata2: FAILURE - already active DMA on this device
Jun 22 17:09:34 hp kernel: ata2: setting up DMA failed

The relevant disk has been replaced 3 times. Smartmon tools have shown no errors.
The controller is listed as being supported in:

http://www.freebsd.org/cgi/man.cgi?query=ata&sektion=4&manpath=FreeBSD+8.2-RELEASE

However, there is a PR#116935 indicating that it should not be used.

http://www.freebsd.org/cgi/query-pr.cgi?pr=116935&cat=


>How-To-Repeat:
There is really no way to repeat the problem. It just happens after a period of approximately 2 months without any other indication. 
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list