I had to try, a new iso "https://abf.rosalinux.ru/platforms/openmandriva2013.0/products/53/product_build_lists/1577"; from Bero, because the 25/09 ISO didn't work.
With this release 29/09 I have concluded the installation. There was only two problems (but I don't think they are in relation with the previous one) The first was a long pause on the Prompt, before starting the installation wizard. The second was a very long pause before the partitioning form (the form was white without any write. I had to try, a new iso "https://abf.rosalinux.ru/platforms/openmandriva2013.0/products/53/product_build_lists/1577"; from Bero, because the 25/09 ISO didn't work. With this release 29/09 I have concluded the installation. There was only two problems (but I don't think they are in relation with the previous one) The first was a long pause on the Prompt, before starting the installation wizard. The second was a very long pause before the partitioning form (the form was white without any write. I've already tried, some restart (8) and no kernel panic has appeared now I'm going to use the system a while...... Thank you very much and sorry for my terrible delay I'm available for any test Ciao -- Davide Garatti Via Tofane 20 16161 Genova In data venerdì 11 ottobre 2013 19:05:35, Chris Tanner ha scritto: > I was getting the panic here, but after adding the noplymouth parameter > to grub2, I have had no problems booting the last couple of days. I have > not had a chance to see if the recent update to plymouth helped at all. > > I have a nvidia graphics card and am using nouveau. > > I didn't see the panic when running openmandriva under VirtualBox. > > Hope this helps. > > Regards, > > Chris > > On 11/10/13 16:46, Marco A Benatto wrote: > > I agree with Tomasz about plymouth relation to panic. > > Seems some stack from kernel (maybe even drm_kms_helper stuff) can be > > running under a misbehaviour, I already saw some similar panics > > occurring due to dma errors (or the lack of proper handle on dma > > requesting/operating errors) on drivers...so I believe is not > > plymouth-related issue. > > > > > > I'm trying to reproduce the panic and get the vmcore and dmesg using > > kdump tool but I still haven't found any machine that could do it here. > > > > I think arisel said with crashkernel parameter the panic stopped (so > > it turn impossible to get the vmcore with kdump as it requires it). I > > suggested for this case do blacklist the drm driver (i.e.: radeon), > > bring the system up without kms stuff and modprobe manually the module > > after it. I writing some systemtap scripts to provide also some debug > > information for this case. I'll let you guys know when it's finished. > > > > On 10/11/2013 05:41 PM, Tomasz Paweł Gajc wrote: > >> As it was said few times on irc, there are no evidences it is caused > >> by plymouth. According to some rumors dracut-034 in some mysterious > >> way fixes kernel panic (I haven't found any related to this commits > >> on upstream git between 033 and 034 release) > >> > >> Myself I was unable to reproduce any kernel panic, so it would be > >> nice if someone do some real investigation with use of kexec-tools > >> and kdump to provide full crash with debuginfo. > >> > >> Wysłano z BlackBerry® w Orange > >> > >> -----Original Message----- > >> From: Robert Xu <[email protected]> > >> Sender: [email protected] > >> Date: Fri, 11 Oct 2013 15:25:59 > >> To: Cooker OpenMandriva<[email protected]> > >> Reply-To: Cooker OpenMandriva <[email protected]> > >> Subject: [OM Cooker] Kernel Panic update?
signature.asc
Description: This is a digitally signed message part.
