Hello,
I've filed a bug here about kernel panics on reboots. It only seems to
happen on my Thinkpad, not the non Thinkpad workstation. It only happens
when I reboot from Fedora into Fedora, not from Windows into Windows, so
it shouldn't be a hardware error.
Would someone else here be using a Thin
Hi folks.
Since the tool 'liveusb-creator' had got a low coverage, I tried to follow
the appropriate case in order to test it.
I encountered this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1250712
I proposed the bug as freeze exception, but I think that more testing is
welcome, in order
d of doing a "shutdown" I
>> powered off the VM thinking (expecting) everything to have been complete.
>> However, when I boot the system I get a panic.
>>
>> The last line on the screen reads
>>
>> ---[ end Kernel panic - not syncing: VFS: Unable
VM thinking (expecting) everything to have been complete.
> However, when I boot the system I get a panic.
>
> The last line on the screen reads
>
> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> Is that considered "
oot the system I get a panic.
The last line on the screen reads....
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
Is that considered "normal"?
--
If you can't laugh at yourself, others will gladly oblige.
--
test mailing list
test@lis
On 27/05/12 13:07, Denis Arnaud wrote:
I had the same problem, but just on my 32bit Rawhide. Indeed, those two
packages (device-mapper-multipath anddevice-mapper-multipath-libs) were
installed on the x86_64 Rawhide.
So, the solution/work-around is simple:
# rpm
-edevice-mapper-multipath-li
--- On Mon, 5/7/12, Jurgen Kramer wrote:
> From: Jurgen Kramer
> Subject: F17: kernel panic at shutdown
> To: test@lists.fedoraproject.org
> Date: Monday, May 7, 2012, 8:33 AM
> I am getting frequent kernel panics
> when shutting down my laptop. It is
> running the latest
panics when shutting down my laptop. It is
running the latest F17 with all updates.
Last messages before the panic are:
Cannot finalize remaining file system and devices, giving up.
Succesfully changed into root pivot.
/shutdown: line 12: /lib/dracut-lib.sh: No such file ore directory
[ kernel
esfully changed into root pivot.
> >>> /shutdown: line 12: /lib/dracut-lib.sh: No such file ore directory
> >>> [ kernel panic ]
> >>>
> >>> Any ideas what's wrong here? My other F17 test rig does not exhibit this
> >>> problem.
>
latest F17 with all updates.
>>>
>>> Last messages before the panic are:
>>>
>>> Cannot finalize remaining file system and devices, giving up.
>>> Succesfully changed into root pivot.
>>> /shutdown: line 12: /lib/dracut-lib.sh: No such file ore director
are:
>>
>> Cannot finalize remaining file system and devices, giving up.
>> Succesfully changed into root pivot.
>> /shutdown: line 12: /lib/dracut-lib.sh: No such file ore directory
>> [ kernel panic ]
>>
>> Any ideas what's wrong here? My other F17 test
up.
> Succesfully changed into root pivot.
> /shutdown: line 12: /lib/dracut-lib.sh: No such file ore directory
> [ kernel panic ]
>
> Any ideas what's wrong here? My other F17 test rig does not exhibit this
> problem.
Best guess:
Sounds like the system is switching back to th
file ore directory
[ kernel panic ]
Any ideas what's wrong here? My other F17 test rig does not exhibit this
problem.
Jurgen
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
2010/10/20 Dennis Jacobfeuerborn
>
> Just out of curiosity if you set /mnt/sysimage as installroot for yum what
> is the mount necessary for?
>
> Regards,
> Dennis
>
> it's required for yum to work. i don't remember the error, but you can try
and see for yourself. just boot any recent fedora re
On 10/20/2010 11:06 AM, cornel panceac wrote:
> 2010/10/20 cornel panceac mailto:cpanc...@gmail.com>>
>
> how can i install a newer kernel (or whatever is faulting here) if the
> system no longer boots?
> i get this error everytime i attempt boot:
>
> ...
> dracut: Switching roo
2010/10/20 cornel panceac
> how can i install a newer kernel (or whatever is faulting here) if the
> system no longer boots?
> i get this error everytime i attempt boot:
>
> ...
> dracut: Switching root
> init[1]: segfault at 464dfc . in ld-2.12.90.so[444000+2]
> .
>
> i'm not reachin
how can i install a newer kernel (or whatever is faulting here) if the
system no longer boots?
i get this error everytime i attempt boot:
...
dracut: Switching root
init[1]: segfault at 464dfc . in ld-2.12.90.so[444000+2]
.
i'm not reaching even runlevel 1.
--
When one door is close
17 matches
Mail list logo
