Geert Uytterhoeven dixit:
>> Furthermore, we just wanted to use the BigRAMPlus as a swap device
>> now following Ingo's description [1]. Unfortunately, CONFIG_MTD
>> is not set in the current Debian m68k kernel and we therefore
>> can't use it.
>>
>> Any chance we can activate that?
>
>Build your
Hi Adrian,
On Sun, Jan 18, 2015 at 1:36 PM, John Paul Adrian Glaubitz
wrote:
> Important side note: We can no longer reproduce this particular crash.
Good to hear that!
> All we get now is a CPU soft-lockup which goes away when using a memfile
> to either exclude the BigRAMPlus ~256 MB from 0x4
Hi Geert!
Important side note: We can no longer reproduce this particular crash.
All we get now is a CPU soft-lockup which goes away when using a memfile
to either exclude the BigRAMPlus ~256 MB from 0x4000 _or_ the
accelerator's on-board memory ~128 MB from 0x0700.
Thus, the memfile to
On Sun, Jan 18, 2015 at 12:53 PM, Christian T. Steigies wrote:
>> [ 10.34] pc=0x122478, fa=0x8000ef4c
00122460 T __clear_user
Fault Address is logical, i.e. virtual.
>> [ 10.35] 68060 access error, fslw=810040
# define MMU060_W (0x0080)/* general write, includes rmw *
Sending this again, without large attachments. Systtem.map, config and dmesg
are here:
https://people.debian.org/~cts/kernel/
On Sat, Jan 17, 2015 at 10:05:58PM +0100, Christian T. Steigies wrote:
> Hi,
> we installed a new buster and bigram in kullervo today. With the
> 3.16 kernel from Debian (
5 matches
Mail list logo
