atmel-mci: issues after upgrading to linux 3.8

Hi all, Hopefully this is the right place for this. Maybe it should go to a list more related to the at91 stuff. Please tell me if that is the case. I'm not subscribed so please CC me. I have an Atmel sam9g45 based machine that has been running 3.4.0-rc4 for a long time without any major issues.

Re: atmel-mci causing oops?

> I'm not sure. > Is there any trace information of kernel? Hi, The oops isn't very descriptive so I got kgdb configured: GNU gdb (GDB) 7.3.1 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you

Re: atmel-mci causing oops?

On Monday, February 27, 2012 10:48:48 AM Jaehoon Chung wrote: > > [1.70] atmel_mci atmel_mci.1: version: 0x410 > > [1.71] atmel_mci atmel_mci.1: using DMA > > [1.71] atmel_mci atmel_mci.1: DMA not available, using PIO > > [1.73] atmel_mci atmel_mci.1: Atmel MCI cont

Re: atmel-mci causing oops?

On Monday, February 27, 2012 10:30:35 AM Seungwon Jeon wrote: > Hi. > > CONFIG_HIGHMEM is enabled in 3.3rc5? > I think your problem is similar to the following commit. > "mmc: dw_mmc: Fix PIO mode with support of highmem"(fc66a7bb13806c0) > Hi, Thank you for your input. CONFIG_HIGHMEM isn't ena

atmel-mci causing oops?

Hi all, Looking for some ideas here.. I don't seem to be able to get a better output of the oops (I have debugging info etc turned on in the config :/). Anyhow, I have 3.1 running with a SAM9G45 based board and I'm trying to get 3.3rc5 running. The only differences from mainline are a board f