2008-03-20 03:32:33 Maybe bug on 2008rc8 new release version.

DAVID ZHOU (CHINA)

Message: 52804

In the newest release version:

The cpu on my board is bf536.

If I use bf537 kernel can boot sucessfully on my board!

I just change kernel configuaration of cpu from bf537 into bf536 , the kernel can not boot sucessfull!

Image Name: Linux-2.6.22.18-ADI-2008R1-svn

Created: 2008-03-20 7:24:13 UTC

Image Type: Blackfin Linux Kernel Image (gzip compressed)

Data Size: 4013561 Bytes = 3.8 MB

Load Address: 00001000

Entry Point: 0014f000

Verifying Checksum ... OK

Uncompressing Kernel Image ... OK

Starting Kernel at = 14f000

Linux version 2.6.22.18-ADI-2008R1-svn (gcc version 4.1.2 (AD

I svn)) #24 Thu Mar 20 15:24:09 CST 2008

Hardware Trace Active and Enabled

Warning: limiting memory to 31MB due to hardware anomaly 05000263

Compiled for ADSP-BF536 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 MHz System Clock

Board Memory: 32MB

Kernel Managed Memory: 32MB

Memory map:

text = 0x00001000-0x000f6e00

rodata = 0x000f7000-0x0013dcf0

data = 0x0013e000-0x0014e000

stack = 0x0013e000-0x00140000

init = 0x0014e000-0x00744000

bss = 0x00744000-0x00752c30

available = 0x00752c30-0x01eff000

DMA Zone = 0x01f00000-0x02000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists. Total pages: 7874

Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 128 (order: 7, 512 bytes)

Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)

Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)

Memory available: 23944k/32768k RAM, (6104k init code, 983k kernel code, 408k da

ta, 1024k dma, 308k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Instruction SRAM: 48 KB (40 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 1024 (order: 1, 8192 bytes)

TCP bind hash table entries: 1024 (order: 0, 4096 bytes)

TCP: Hash tables configured (established 1024 bind 1024)

TCP reno registered

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

SMSC LAN83C185: Registered new driver

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1, mdc_

clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, r

egs_base@ffc00500, dma channel@7

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 2034-06-26 02:44:57 (2034902697)

Freeing unused kernel memory: 6104k freed

dma_alloc_init: dma_page @ 0x00740000 - 256 pages at 0x01f00000

NULL pointer access (probably)

Kernel OOPS in progress

Defered Exception context

CURRENT PROCESS:

COMM=inetd PID=94

TEXT = 0x01080040-0x01085ec0 DATA = 0x01085ec4-0x01087394

BSS = 0x01087394-0x01087a84 USER-STACK = 0x01088f90

return address: [0x00034822]; contents of:

0x00034800: 6c66 0127 a328 304c 0484 e2ff fd9d 0000

0x00034810: 05f5 0167 4821 6fa6 3228 3031 101c 0000

0x00034820: 0037 [9169] 9109 0c01 1819 3211 6008 b0c8

0x00034830: 6ffa 934a 5e91 a111 60f8 0807 1807 e14a

SEQUENCER STATUS: Not tainted

SEQSTAT: 00000027 IPEND: 8030 SYSCFG: 0006

HWERRCAUSE: 0x0

EXCAUSE : 0x27

physical IVG15 asserted : <0xffa00e20> { _evt_system_call + 0x0 }

logical irq 6 mapped : <0xffa00210> { _timer_interrupt + 0x0 }

logical irq 18 mapped : <0x0008e4c0> { _bfin_serial_dma_rx_int + 0x0 }

logical irq 19 mapped : <0x0008e06c> { _bfin_serial_dma_tx_int + 0x0 }

logical irq 24 mapped : <0x00097a4c> { _bf537mac_interrupt + 0x0 }

RETE: <0x00000000> /* Maybe null pointer? */

RETN: <0x0073bdbc> /* unknown address */

RETX: <0x00034822> { _kmem_cache_alloc + 0x12 }

RETS: <0x000c7758> { _inet_bind_bucket_create + 0x10 }

PC : <0x00034822> { _kmem_cache_alloc + 0x12 }

DCPLB_FAULT_ADDR: <0x00000000> /* Maybe null pointer? */

ICPLB_FAULT_ADDR: <0x00034822> { _kmem_cache_alloc + 0x12 }

PROCESSOR STATE:

R0 : 00000000 R1 : 00000020 R2 : 00000202 R3 : 0073d880

R4 : 010873b0 R5 : 0073d880 R6 : 00000020 R7 : 0000ffff

P0 : 0073be7c P1 : 00000000 P2 : 00000000 P3 : 0014e000

P4 : 00000808 P5 : 00000000 FP : 0073be00 SP : 0073bce0

LB0: ffa01d06 LT0: ffa01d06 LC0: 00000000

LB1: 0108020b LT1: 01080202 LC1: 00000013

B0 : 00000000 L0 : 00000000 M0 : 00000000 I0 : 01085f00

B1 : 00000000 L1 : 00000000 M1 : 00000000 I1 : 01088f14

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

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

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

USP : 01088dc4 ASTAT: 02000020

Hardware Trace:

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

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

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

Source : <0xffa005d4> { _ex_trap_c + 0x5c }

2 Target : <0xffa00578> { _ex_trap_c + 0x0 }

Source : <0xffa00402> { _ex_workaround_261 + 0x22 }

3 Target : <0xffa003e0> { _ex_workaround_261 + 0x0 }

Source : <0xffa007cc> { _trap + 0x28 }

4 Target : <0xffa007a4> { _trap + 0x0 }

Source : <0xffa0051a> { _bfin_return_from_exception + 0xe }

5 Target : <0xffa0050c> { _bfin_return_from_exception + 0x0 }

Source : <0xffa003f2> { _ex_workaround_261 + 0x12 }

6 Target : <0xffa003e0> { _ex_workaround_261 + 0x0 }

Source : <0xffa007cc> { _trap + 0x28 }

7 Target : <0xffa007a4> { _trap + 0x0 }

Source : <0x00034820> { _kmem_cache_alloc + 0x10 }

8 Target : <0x00034810> { _kmem_cache_alloc + 0x0 }

Source : <0x000c7754> { _inet_bind_bucket_create + 0xc }

9 Target : <0x000c7748> { _inet_bind_bucket_create + 0x0 }

Source : <0x000c907a> { _inet_csk_get_port + 0x96 }

10 Target : <0x000c9072> { _inet_csk_get_port + 0x8e }

Source : <0x000c900e> { _inet_csk_get_port + 0x2a }

11 Target : <0x000c8ff6> { _inet_csk_get_port + 0x12 }

Source : <0x000115c6> { _local_bh_disable + 0x12 }

12 Target : <0x000115b4> { _local_bh_disable + 0x0 }

Source : <0x000c8ff2> { _inet_csk_get_port + 0xe }

13 Target : <0x000c8fe4> { _inet_csk_get_port + 0x0 }

Source : <0x000d61c8> { _tcp_v4_get_port + 0x1c }

14 Target : <0x000d61ac> { _tcp_v4_get_port + 0x0 }

Source : <0x000e28e8> { _inet_bind + 0xd0 }

15 Target : <0x000e28dc> { _inet_bind + 0xc4 }

Source : <0x000e2904> { _inet_bind + 0xec }

Stack from 0073bcc0:

00000000 ffa00730 0014256c 0014256c 00142568 00000000 00000000 00000000

00034822 00008030 00000027 00000000 0073bdbc 00034822 00034822 000c7758

00000000 02000020 0108020b ffa01d06 01080202 ffa01d06 00000013 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 01088f14 01085f00 01088dc4 0073be00 00000000 00000808

Call Trace:

[<0000ffff>] _do_group_exit+0x3/0x84

[<000c7758>] _inet_bind_bucket_create+0x10/0x40

[<000c907e>] _inet_csk_get_port+0x9a/0x1c8

[<000d61cc>] _tcp_v4_get_port+0x20/0x28

[<000e28a4>] _inet_bind+0x8c/0x1c4

[<000c9294>] _inet_csk_bind_conflict+0x0/0xa4

[<000e28ea>] _inet_bind+0xd2/0x1c4

[<000a7172>] _sys_bind+0x4e/0x74

[<00034858>] _kmem_cache_alloc+0x48/0x58

[<000d58a4>] _tcp_keepalive_timer+0x0/0x1d4

[<000d751c>] _tcp_v4_init_sock+0x1c/0xf4

[<000a916a>] _sock_setsockopt+0x62/0x52c

[<000a6460>] _sock_attach_fd+0x30/0xc8

[<000a6488>] _sock_attach_fd+0x58/0xc8

[<000a7584>] _sys_setsockopt+0x74/0x80

[<000a7124>] _sys_bind+0x0/0x74

[<00008000>] __l1sram_proc_read+0x40/0xa0

[<0015514c>] _time_init+0xcc/0xe4

[<0015513c>] _time_init+0xbc/0xe4

Modules linked in:

Kernel panic - not syncing: Kernel exception

QuoteReplyEditDelete

2008-03-20 08:30:46 Re: Maybe bug on 2008rc8 new release version.

Robin Getz (UNITED STATES)

Message: 52839 In the kernel - can you unselect:

Device Drivers

Network device support

Ethernet (10 or 100Mbit)

[*] Use L1 memory for rx/tx packets

and see if that helps?

QuoteReplyEditDelete

2008-03-20 21:16:10 Re: Maybe bug on 2008rc8 new release version.

DAVID ZHOU (CHINA)

Message: 52861

Hi,Robin

Thanks ! But If I choose bf536, there is no such option.

QuoteReplyEditDelete

2008-03-25 23:22:35 Re: Maybe bug on 2008rc8 new release version.

DAVID ZHOU (CHINA)

Message: 53023

Thanks Robin!

Is it a bug or I need to do something else ?

QuoteReplyEditDelete

2008-03-26 07:56:08 Re: Maybe bug on 2008rc8 new release version.

Paul Lau (UNITED STATES)

Message: 53047 Did you try CPU core-clock of 300 MHz instead of 500 MHz?

QuoteReplyEditDelete

2008-03-26 12:54:53 Re: Maybe bug on 2008rc8 new release version.

Robin Getz (UNITED STATES)

Message: 53065 David:

I tried replicating things - and it worked fine for me.

Starting Kernel at = 150000

Linux version 2.6.22.18-ADI-2008R1-svn4447 (rgetz@imhotep) (gcc version 4.1.2 (ADI svn)) #3 Wed Mar 26 12:34:28 EDT 2008

early printk enabled on early_BFuart0

Hardware Trace Active and Enabled

Warning: limiting memory to 56MB due to hardware anomaly 05000263

Compiled for ADSP-BF536 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

text = 0x00001000-0x000f7140

rodata = 0x000f8000-0x0013ecac

data = 0x0013f000-0x00150000

stack = 0x00140000-0x00142000

init = 0x00150000-0x007ce000

bss = 0x007ce000-0x007dcd30

available = 0x007dcd30-0x037ff000

DMA Zone = 0x03f00000-0x04000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists. Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart0,57600 panic=3

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

console handover: boot [early_BFuart0] -> real [ttyBF0]

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 48712k/65536k RAM, (6648k init code, 984k kernel code, 415k data, 1024k dma, 7756k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Instruction SRAM: 48 KB (40 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

SMSC LAN83C185: Registered new driver

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 04:49:30 (17370)

Freeing unused kernel memory: 6648k freed

dma_alloc_init: dma_page @ 0x007cb000 - 256 pages at 0x03f00000

_____________________________________

a8888b. / Welcome to the uClinux distribution \

d888888b. / _ _ \

8P"YP"Y88 / | | |_| __ __ (TM) |

8|o||o|88 _____/ | | _ ____ _ _ \ \/ / |

8' .88 \ | | | | _ \| | | | \ / |

8`._.' Y8. \ | |__ | | | | | |_| | / \ |

d/ `8b. \ \____||_|_| |_|\____|/_/\_\ |

dP . Y8b. \ For embedded processors including |

d8:' " `::88b \ the Analog Devices Blackfin /

d8" 'Y88b \___________________________________/

:8P ' :888

8a. : _a88P For further information, check out:

._/"Yaa_: .| 88P| - http://blackfin.uclinux.org/

\ YP" `| 8P `. - http://docs.blackfin.uclinux.org/

/ \.___.d| .' - http://www.uclinux.org/

`--..__)8888P`._.' jgs/a:f - https://www.analog.com/blackfin

Have a lot of fun...

BusyBox v1.4.1 (2008-03-26 12:32:01 EDT) Built-in shell (msh)

Enter 'help' for a list of built-in commands.

root:/> cat /proc/cpuinfo

processor : 0

vendor_id : Analog Devices

cpu family : 0x27c8000

model name : ADSP-BF536 500(MHz CCLK) 100(MHz SCLK)

stepping : 2

cpu MHz : 500.000/100.000

bogomips : 997.37

Calibration : 498688000 loops

cache size : 16 KB(L1 icache) 32 KB(L1 dcache-wt) 0 KB(L2 cache)

dbank-A/B : cache/cache

icache setup : 4 Sub-banks/4 Ways, 32 Lines/Way

dcache setup : 2 Super-banks/4 Sub-banks/2 Ways, 64 Lines/Way

board name : ADDS-BF537-STAMP

board memory : 65536 kB (0x00000000 -> 0x04000000)

kernel memory : 57336 kB (0x00001000 -> 0x037ff000)

root:/> uname -a

Linux blackfin 2.6.22.18-ADI-2008R1-svn4447 #3 Wed Mar 26 12:34:28 EDT 2008 blackfin unknown

root:/>

can you do a "make bugreport" can post the resulting file?

Thanks

-Robin

QuoteReplyEditDelete

2008-04-09 07:55:38 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 53911 I have the same problem on my custom bf536 board, however, I can boot the board.

The problem occurs as soon as I try to connect with the board with for example telnet.

Setting the cpu to bf537 fixes it for me as well.

Another way I found to fix it was disabling the cache.

I have to say that I'm not using the latest u-boot. Could that cause the problem?

I did the make bugreport as you suggested and attached it.

Manolo

bugreport.tgz

QuoteReplyEditDelete

2008-04-09 08:43:42 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 53921 I can add to this that when I set the bf537 cpu, I'm still not able to login to the board using dropbear. It crashes.

Telnet works however.

<edit>

Never mind. Dropbear didn't work because of a a stack overflow.

<edit>

QuoteReplyEditDelete

2008-04-10 06:17:10 Re: Maybe bug on 2008rc8 new release version.

Sonic Zhang (CHINA)

Message: 54025 Please move more code out of the L1 sram in kernel menuconfig. You should not overflow the L1 sram on bf536.

QuoteReplyEditDelete

2008-04-10 08:13:24 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 54029 Ok, I can try that, but why does it work when you select BF537?

Or is that just a lucky coincidence?

QuoteReplyEditDelete

2008-04-15 06:40:35 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 54260 I tried some different configuration for the

Blackfin Processor Options->Blackfin Kernel Optimizations

First I found out that I cannot disable all items. If I disable:

Locate entrire ASM lowlevel exception / interrupt.....etc.

Then the kernel doesn't compile

If I disable all options (except the one I cannot disable), then everything works fine.

If I then add the option:

Locate cacheline_aligned data to L1 Data Memory.

Then the network fails.

I can enable all options except:

Locate cacheline_aligned data to L1 Data memory

and

Locate Syscall Table L1 Data Memory

And then everything works fine.

So my feeling is that there's something wrong in those two items for BF536.

QuoteReplyEditDelete

2008-04-15 07:02:09 Re: Maybe bug on 2008rc8 new release version.

Ji Ma (CHINA)

Message: 54266

For my experience. blackfin toolchain has some problem on its linker.

errors happened below has no intuitive reasons, these can be solved though change your source code to another style,may be let it to avoid the errors.

1.CPLB missing acess......

2.jump to 0-0xfffff..........

errors happened below can be solve has the definitive reasons.

1.NULL pointer access

2.misaligned data access.

hardware stability problem may also cause the errors above.

QuoteReplyEditDelete

2008-04-15 08:28:53 Re: Maybe bug on 2008rc8 new release version.

Robin Getz (UNITED STATES)

Message: 54272 Ji:

The toolchain is pretty solid - I do not think there are errors with it.

What chip/platform are you testing on? If you have flakey hardware - that needs to be fixed first.

-Robin

QuoteReplyEditDelete

2008-04-15 08:44:20 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 54273 Not sure if that question was for me, but:

We are using a custom board with bf536 revision 0.3, 32 MB RAM and 8 MB Atmel spi dataflash.

We've been using 2007R1.1-RC3 since september and the hardware seems stable.

Now we're trying to switch to 2008R1-RC8 and we run into this problem.

Besides this problem the only open issue we have is that the dataflash driver seems not to work correctly with dma enabled. At first I thought it might be related, but all solutions that fix the network problem do not fix the dataflash problem, except disabling the cache.

QuoteReplyEditDelete

2008-04-15 09:20:54 Re: Maybe bug on 2008rc8 new release version.

Robin Getz (UNITED STATES)

Message: 54275 Manolo:

I think Sonic checked in a fix that would effect things on 536 day before yesterday. Can you check to see if that fixes things?

It is just 2 files, so it shouldn't be too bad to patch locally if you want.

http://blackfin.uclinux.org/gf/project/linux-kernel/scmsvn/?action=browse&path=%2F&view=rev&revision=4586

-Robin

QuoteReplyEditDelete

2008-04-15 10:19:53 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 54277 Yes, it fixed the cacheline_aligned data to L1 Data memory.

Leaves us with the following items:

The 'Locate Syscall Table L1 Data memory' option still cannot be enabled.

And the 'Locate entire ASM lowlevel exception / interrupt ...etc.' option cannot be disabled.

Both aren't a problem in the default configuration and not for me as well, but I thought I'd mention it..

Maybe it's fixed already as well on the branch?

Thanks,

Manolo

QuoteReplyEditDelete

2008-04-15 23:12:15 Re: Maybe bug on 2008rc8 new release version.

Sonic Zhang (CHINA)

Message: 54297

You can disable part of the data cache 16k or the whole data cache 32k and try these option again.

QuoteReplyEditDelete

2008-04-16 02:41:15 Re: Maybe bug on 2008rc8 new release version.

Ji Ma (CHINA)

Message: 54301

Robin:

I have done some projects on 2006RC2 and 2007RC3. the run time crash for (bf531,bf561):

"CPLB access missing...." and " jump to 0 ~ 0xffff" , I have never found the definitive solve method. I just change my coding to another style, try to increase or reduce the codes for the same function , then I can avoid them. Even I insert or remove some printk for debug also can cause this error. if this errors avoid by my style change , my hareware is working perfect.

Even sometimes I compile the same code twice , one may be crash the other is OK.

By the way,Robin , could you please tell me What's the coding error cause the crash I mentioned above?

Ji Ma

QuoteReplyEditDelete

2008-04-16 03:15:50 Re: Maybe bug on 2008rc8 new release version.

Yi Li (CHINA)

Message: 54306 Ji,

It would be great if you can post the test case here (so we can try on 2008r1).

QuoteReplyEditDelete

2008-04-16 04:25:37 Re: Maybe bug on 2008rc8 new release version.

Ji Ma (CHINA)

Message: 54323

Hi, Li, However ,I can avoid these unreasonable crashes, so , I have not the much strong eager to find out that's why, I think the problem still the problem, If I can go through it by another path. let it go. Products still perfectly push to the market.

Some day , if it is reapppear front of me , I try to post the case to you . I think it should be often if you work on the kernel module.

But if you can give me some imagine coding scene. I am glad to find out why.

To tell the truth , I have ever imagine some reasons, the excute code layout, some errors may happened when the processor's cache feed,cache flushing, cache write-back, stack pushing and popping, CPLB related ops etc. on the this error code layout.

However, it is my imagine. No warranty.

For the newly 2008R1, I won't upgrade the work onto it right now, so much drivers and kernel modules I have done on the older kernel version. I need a long free time to port them to the newly version. God bless no such "unreasonable" crashes happen on the 2008R1.

Anyway, thanks your reply.

QuoteReplyEditDelete

2008-04-16 09:49:22 Re: Maybe bug on 2008rc8 new release version.

Manolo van Ee (NETHERLANDS)

Message: 54337 Sonic:

Do you mean this as a solution? Or do you want me to try this for you?

Because I don't need this to be fixed...

Manolo

QuoteReplyEditDelete

2008-04-16 10:23:31 Re: Maybe bug on 2008rc8 new release version.

Mike Frysinger (UNITED STATES)

Message: 54338 the crash message gives you a trace back of how the code crashed. you can review the documentation: