[#3824] serial driver causes problems during PM suspend resume

Submitted By: Michael Hennerich

Open Date

2008-01-11 10:16:07 Close Date

2008-01-28 01:21:10

Priority:

High Assignee:

Sonic Zhang

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

2007R1 svn branch

Category:

N/A Board:

STAMP

Processor:

BF537 Silicon Revision:

0.3

Is this bug repeatable?:

Yes Resolution:

Fixed

Uboot version or rev.:

trunk Toolchain version or rev.:

App binary format:

N/A

Summary: serial driver causes problems during PM suspend resume

Details:

The serial driver causes problems during PM suspend resume on 2007R1 svn branch

For the issue to recreate enable PM support (Cause Wakeup Event by GPIO PF2)

see PM test - and have PF2 constantly being asserted. (push button)

root:~> while [ 1 ];echo standby > /sys/power/state;done;

Stopping tasks ... done.

Suspending console(s)

After a while you will see one or all below reported issues.

If you type chars into the console while running this test - the bugs are more likely to happen.

This issue seems to be already fixed on 2008R1.

1) There are messages like this coming out of the dma driver:

Assertion failed! dma_ch[channel].chan_status != DMA_CHANNEL_FREE && channel < MAX_BLACKFIN_DMA_CHANNEL, arch/blackfin/kernel/bfin_dma_5xx.c, disable_dma, line=417

Unable to attach Blackfin UART TX DMA channel

Assertion failed! dma_ch[channel].chan_status != DMA_CHANNEL_FREE && channel < MAX_BLACKFIN_DMA_CHANNEL, arch/blackfin/kernel/bfin_dma_5xx.c, disable_dma, line=417

Assertion failed! dma_ch[channel].chan_status != DMA_CHANNEL_FREE && channel < MAX_BLACKFIN_DMA_CHANNEL, arch/blackfin/kernel/bfin_dma_5xx.c, get_dma_curr_xcount, line=583

Unable to attach Blackfin UART TX DMA channel

Error 1:

0: Waiting for input from trig

Stopping tasks: ========|

Suspending console(s)

Restarting tasks...<0>Data access CPLB miss

- Used by the MMU to signal a CPLB miss on a data access.

CURRENT PROCESS:

COMM=sh PID=92

TEXT = 0x92003060-0x92003060 DATA = 0x92003060-0x92003060

BSS = 0x92003060-0x92003060 USER-STACK = 0x92003060

return address: 0x0001d2a4; contents of [PC-16...PC+8]:

RETE: 00000000 RETN: 0027fe9c RETX: 0001d2a4 RETS: 0000e724

IPEND: 8030 SYSCFG: 0036

SEQSTAT: 00000026 SP: 0027fdc0

R0: 0000ffff R1: 0000001f R2: 00000000 R3: ffffffff

R4: ffffffff R5: 029dfac4 R6: ffffe000 R7: 00000004

P0: 92003060 P1: 0027febc P2: 0027fec8 P3: 02989920

P4: 00000072 P5: 02aadce8 FP: 0027fed0

A0.w: 00000000 A0.x: 00000000 A1.w: 00000000 A1.x: 00000000

LB0: 0285d687 LT0: 0285d674 LC0: fffffffd

LB1: 02930fdf LT1: 02930fde LC1: 00000000

B0: 00000000 L0: 00000000 M0: 00000000 I0: 029a0584

B1: 00000000 L1: 00000000 M1: 00000000 I1: ffffffff

B2: 00000000 L2: 00000000 M2: 00000000 I2: 00000000

B3: 00000000 L3: 00000000 M3: 00000000 I3: 00000000

USP: 029dfa70 ASTAT: 02003004

DCPLB_FAULT_ADDR=92003064

ICPLB_FAULT_ADDR=0001d2a4

Hardware Trace:

0 Target : <0x00004720> { _trap_c + 0x0 }

Source : <0xffa00b68> { _exception_to_level5 + 0xb4 }

1 Target : <0xffa00ab4> { _exception_to_level5 + 0x0 }

Source : <0xffa00ab2> { _ex_trap_c + 0x4e }

2 Target : <0xffa00a0c> { _handle_bad_cplb + 0x0 }

Source : <0xffa00504> { __cplb_hdr + 0x5c }

3 Target : <0xffa00502> { __cplb_hdr + 0x5a }

Source : <0x000046b2> { _panic_cplb_error + 0x16 }

4 Target : <0x0000469c> { _panic_cplb_error + 0x0 }

Source : <0xffa004fe> { __cplb_hdr + 0x56 }

5 Target : <0xffa004fa> { __cplb_hdr + 0x52 }

Source : <0xffa004ea> { __cplb_hdr + 0x42 }

6 Target : <0xffa004e4> { __cplb_hdr + 0x3c }

Source : <0xffa004de> { __cplb_hdr + 0x36 }

7 Target : <0xffa004dc> { __cplb_hdr + 0x34 }

Source : <0xffa004d4> { __cplb_hdr + 0x2c }

8 Target : <0xffa004d0> { __cplb_hdr + 0x28 }

Source : <0xffa00648> { _cplb_mgr + 0x140 }

9 Target : <0xffa00644> { _cplb_mgr + 0x13c }

Source : <0xffa007ac> { _cplb_mgr + 0x2a4 }

10 Target : <0xffa007a4> { _cplb_mgr + 0x29c }