a look at the hard drive, and I can try to add something to the
discussion.
The situation is the same as described above, kernel panic at switch-root.
Three kernels were available (up to 5.12), and they all failed in the same way.
Partitions look fine, fat for UEFI (not tested, but hey, I reach
On 10/8/21 06:18, Chris Murphy wrote:
5.13.9 is now in koji you might give that a shot.
5.13.5 changelog shows
commit c3eb534eae09de6cdd3e0ff63897b20e1b079cdb
vmxnet3: fix cksum offload issues for tunnels with non-default udp ports
5.13.6 changelog shows several vmware related commits
htt
5.13.9 is now in koji you might give that a shot.
5.13.5 changelog shows
commit c3eb534eae09de6cdd3e0ff63897b20e1b079cdb
vmxnet3: fix cksum offload issues for tunnels with non-default udp ports
5.13.6 changelog shows several vmware related commits
https://cdn.kernel.org/pub/linux/kernel/v5.x
Hi,
I am running F34 in a Vmware Player VM and have just done the first
boot after installing the update that installed Kernel 5.13.6-200, which
fails with a kernel panic saying it can't mount the root volume, but
Kernel 5.13.4-200 boots quite happily. Is this a known issue?
re
g immediately becomes black and it's very
> clear that the Mac is restarting
> - When it restarts, it mentions that "A problem occurred that necessitated
> the reboot"
> - I've attached the full Kernel panic log to this email
>
> Some details from the Kernel Panic
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
>
> Sorry I am not advertising but P
gt; > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
>
>
> Sorry I am not advertising b
hilip Rhoades from Australia? offered to
look into my Teo En Ming Linux bootable live CD/DVD kernel panic
*problem* and he asked me where he can download my ISO files so that he
can help me to troubleshoot the problem, if I guess his intent
correctly.
--
-BEGIN EMAIL SIGNATURE-
The G
On Wed, 2020-03-18 at 07:44 +0800, Turritopsis Dohrnii Teo En Ming
wrote:
> Hi,
>
> The iso is about 250 MB. The download links can be found here:
What does this have to do with Fedora? Apparently you have created your
own Linux distro, not as a fork of Fedora but as an entirely
independent proje
creating a VM with this - I couldn't find a download link . .
Thanks,
Phil.
On 2020-03-18 03:31, Turritopsis Dohrnii Teo En Ming wrote:
Subject: Teo En Ming's Linux From Scratch (LFS) 20200302-systemd
Bootable Live CD/DVD Kernel Panic
Good day from Singapore to all Linux users,
Recen
Subject: Teo En Ming's Linux From Scratch (LFS) 20200302-systemd
Bootable Live CD/DVD Kernel Panic
Good day from Singapore to all Linux users,
Recently, on 12 March 2020, I have successfully created my own custom
Linux distribution which I affectionately call it Teo En Ming Linux.
My c
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin wrote:
>
> Symbolic links missing on / (/bin->/usr/bin and such).
> /bin/bash missing or corrupted.
> /lib64/ libraries missing or corrupted.
> systemd itself missing, pivot root attempts to run systemd and that
> may be what is failing, but you don't r
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin wrote:
>
> Symbolic links missing on / (/bin->/usr/bin and such).
> /bin/bash missing or corrupted.
> /lib64/ libraries missing or corrupted.
> systemd itself missing, pivot root attempts to run systemd and that
> may be what is failing, but you don't r
Symbolic links missing on / (/bin->/usr/bin and such).
/bin/bash missing or corrupted.
/lib64/ libraries missing or corrupted.
systemd itself missing, pivot root attempts to run systemd and that
may be what is failing, but you don't really know what the underlying
cause is for it to fail.
What exa
On Mon, Sep 9, 2019 at 9:07 PM Tony Nelson wrote:
>
> Usually, when it all goes wrong just after pivot-root, there is a
> problem with the new (real) root. Exactly how it goes wrong is not
> useful. I would look hard at whatever is mounted at /sysroot. It
> should be what you expect / (root) to
On 19-09-09 14:10:24, murph nj wrote:
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
...
Usually, when it all goes wrong just after pivot-root, there is
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
I can just reinstall, but I'm trying to learn more about how to
recover from errors, instead of taking the eas
On Thu, Sep 5, 2019 at 11:08 AM sixpack13 wrote:
>
> e2fsck is for ext -partitions
> AFAIK /boot/efi is fat !
You are correct. I already checked, all the partitions are fine.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
e2fsck is for ext -partitions
AFAIK /boot/efi is fat !
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-o
Everything left on the screen after the kernel panic is (too much to
> type)
>
> https://imgur.com/a/kf81crl
What I pull from that is that the error causing the problem is a page
fault when it asks for some memory. But I don't know where to go from
that insight, other than openi
On Wed, Sep 4, 2019 at 9:56 PM Tony Nelson wrote:
>
>
> It dies trying to pivot-root, so add to the kernel command line
>
> rd.break=pre-pivot
>
Interesting. I was able to drop to a shell. I took a look at the
journal, and it looked like a possible hibernation problem, so I took
that out
On 19-09-04 17:42:40, murph nj wrote:
...
Everything left on the screen after the kernel panic is (too much to
type)
https://imgur.com/a/kf81crl
...
Unfortunately, it goes right to a kernel panic, so no prompts at all
to work with. (I'd have chewed on it more before asking for help
On Wed, Sep 4, 2019 at 5:42 PM murph nj wrote:
>
> On Wed, Sep 4, 2019 at 4:21 PM stan via users
> wrote:
> >
> > On Wed, 4 Sep 2019 15:05:36 -0400
> > murph nj wrote:
> >
> > > I was able to mount the drives, and check them, no problems.
> >
> > Did that include the boot partition, where the ke
them previously
by hitting the escape key right after entering my password for the
disks.)
Everything left on the screen after the kernel panic is (too much to type)
https://imgur.com/a/kf81crl
> Does it drop to a dracut or grub prompt? If it does, it is also
> possible to view the tempora
On Wed, 4 Sep 2019 15:05:36 -0400
murph nj wrote:
> I was able to mount the drives, and check them, no problems. I was
> also able to move all of my important data off of the drives to an
> external, so I'm not worried about any loss to the data on the drives.
> No worries of fatal mistakes anym
lable from the boot menu, along with
> > rescue mode. All of them kernel panic.
>
> Does it get far enough along to put messages in the journal? You could
> run a boot that fails, then boot from the USB, and mnt the installed
> filesystem (usually under /mnt/sysimage), chroot t
e from the boot menu, along with
> rescue mode. All of them kernel panic.
Does it get far enough along to put messages in the journal? You could
run a boot that fails, then boot from the USB, and mnt the installed
filesystem (usually under /mnt/sysimage), chroot to /mnt/sysimage, and
run journa
Fedora.
There are three kernels available from the boot menu, along with
rescue mode. All of them kernel panic.
--murph
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
On Tue, 3 Sep 2019 22:31:52 -0400
murph nj wrote:
> I've got an Acer laptop that has been shutting down suddenly. (I
> suspect a bad battery, working on that.)
>
> After a sudden shutdown last night, I now get a kernel panic on boot
> right after "Starting Switch Roo
ght, I now get a kernel panic on boot
right after "Starting Switch Root..."
I was able to boot from a USB stick, and was able to read the journal,
but I didn't see anything obvious to help.
I was able to get all of my data off of the (encrypted) disks, so
that's not a problem, bu
On 18/12/17 14:34, John Pilkington wrote:
On 18/12/17 10:20, John Pilkington wrote:
On 16/12/17 18:10, John Pilkington wrote:
On 13/12/17 11:57, John Pilkington wrote:
software-updates just upgraded 82 packages. On reboot, immediate
kernel panic.
4.13.16-202 is running ok.
yumex-dnf shows
On 18/12/17 10:20, John Pilkington wrote:
On 16/12/17 18:10, John Pilkington wrote:
On 13/12/17 11:57, John Pilkington wrote:
software-updates just upgraded 82 packages. On reboot, immediate
kernel panic.
4.13.16-202 is running ok.
yumex-dnf shows two instances of the new kernel packages
On 16/12/17 18:10, John Pilkington wrote:
On 13/12/17 11:57, John Pilkington wrote:
software-updates just upgraded 82 packages. On reboot, immediate
kernel panic.
4.13.16-202 is running ok.
yumex-dnf shows two instances of the new kernel packages ??
nvidia 387.22
... 4.14.5-200.fc26
On 13/12/17 11:57, John Pilkington wrote:
software-updates just upgraded 82 packages. On reboot, immediate kernel
panic.
4.13.16-202 is running ok.
yumex-dnf shows two instances of the new kernel packages ??
nvidia 387.22
... 4.14.5-200.fc26 panics too for me
software-updates just upgraded 82 packages. On reboot, immediate kernel
panic.
4.13.16-202 is running ok.
yumex-dnf shows two instances of the new kernel packages ??
nvidia 387.22
___
users mailing list -- users@lists.fedoraproject.org
To
that installed 4.13.5-100.fc25.x86_64
>
>
> Cant mount /boot
>
>
>
> System:ELITEGROUP COMPUTER SYSTEM CO.,LTD. P965T-A/P965T-A, BIOS 6.00
> PG 08/30/2007
>
> 4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ
>
>
>
> Kernel panic
>
>
On Mon, 23 Oct 2017 23:31:36 +0100
Ntlworld wrote:
> Thanks very much for your help Stan
You're welcome.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Thanks very much for your help Stan
> On 23 Oct 2017, at 23:28, stan wrote:
>
> On Mon, 23 Oct 2017 22:56:53 +0100
> Andy Paterson wrote:
>
>> Hi
>> I did a manual dracut as suggested except I had to specify the .img
>> filename otherwise it just generated a file 4.13.5-100.fc25.x86_64 :)
>> w
On Mon, 23 Oct 2017 22:56:53 +0100
Andy Paterson wrote:
> Hi
> I did a manual dracut as suggested except I had to specify the .img
> filename otherwise it just generated a file 4.13.5-100.fc25.x86_64 :)
> which is not what grub is looking for. I did:
Sorry about that. I use the command to gener
On Monday, 23 October 2017 21:53:50 BST stan wrote:
> On Mon, 23 Oct 2017 20:57:44 +0100
> Andy Paterson wrote:
>
>
> > Hi,
> >
> > after doinga a "dnf reinstall kernel"
> >
> > which reinstalled kernel for x86_64 4.13.5-100.fc25 from the updates
> > repository, I still have
> > no /boot/
On Mon, 23 Oct 2017 20:57:44 +0100
Andy Paterson wrote:
> Hi,
> after doinga a "dnf reinstall kernel"
> which reinstalled kernel for x86_64 4.13.5-100.fc25 from the updates
> repository, I still have
> no /boot/initramfs-4.13.5-100.fc25.x86_64.img. I conclude therefore
> that the package t
P965T-A/P965T-A, BIOS 6.00 PG
> > 08/30/2007
> >
> > 4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ
> >
> >
> >
> > Kernel panic
> >
> >
> >
> > Can boot previous kernel :
> >
> > 4.12.14-200.fc25.x86_64
&g
On Monday, 23 October 2017 18:42:44 BST stan wrote:
> On Mon, 23 Oct 2017 12:11:39 +0100
> Andy Paterson wrote:
>
>
> > My apologies,
> >
> > /boot:/dev/sda3 on /boot type ext4
> >
> > (rw,relatime,seclabel,data=ordered) Not (I agree!) that that tells
> > you much!
> >
> > All I can see i
On Mon, 23 Oct 2017 12:11:39 +0100
Andy Paterson wrote:
>
> My apologies,
> /boot:/dev/sda3 on /boot type ext4
> (rw,relatime,seclabel,data=ordered) Not (I agree!) that that tells
> you much!
>
> All I can see is that in /etc/grub2.cfg :
>
> Previous menu entries (eg 4.12.14-200.fc25.x86
On Mon, 23 Oct 2017 12:11:39 +0100
Andy Paterson wrote:
> My apologies,
> /boot:/dev/sda3 on /boot type ext4
> (rw,relatime,seclabel,data=ordered) Not (I agree!) that that tells
> you much!
>
> All I can see is that in /etc/grub2.cfg :
>
> Previous menu entries (eg 4.12.14-200.fc25.x86_64
P965T-A/P965T-A, BIOS 6.00 PG
> > 08/30/2007
> >
> > 4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ
> >
> >
> >
> > Kernel panic
> >
> >
> >
> > Can boot previous kernel :
> >
> > 4.12.14-200.fc25.x86_64
&g
On 10/21/17 23:10, Andy Paterson wrote:
>
> FC25 kernel update that installed 4.13.5-100.fc25.x86_64
>
> Cant mount /boot
>
>
>
> System:ELITEGROUP COMPUTER SYSTEM CO.,LTD. P965T-A/P965T-A, BIOS 6.00 PG
> 08/30/2007
>
> 4 X Intel Core2 Quad CPU Q6700
On 10/21/2017 08:10 AM, Andy Paterson wrote:
Hi, after a recent package manager based update,
FC25 kernel update that installed 4.13.5-100.fc25.x86_64
Cant mount /boot
Can you explain this further? Was that an error during the update or
you're saying that you can't mount the /boot partition
Hi, after a recent package manager based update,
FC25 kernel update that installed 4.13.5-100.fc25.x86_64
*Cant mount /boot*
System:ELITEGROUP COMPUTER SYSTEM CO.,LTD. P965T-A/P965T-A, BIOS 6.00 PG
08/30/2007
4 X Intel Core2 Quad CPU Q6700 @ 2.66GHZ
*Kernel panic*
Can boot previous kernel
On Mon, Aug 3, 2015 at 3:30 AM, Patrick O'Callaghan
wrote:
> On Sun, 2015-08-02 at 17:58 -0600, Chris Murphy wrote:
>> And then if you're still feeling industrious by the time all of this
>> is done, tomorrow there will be a 4.2.0.rc5 build to test against and
>> you can report whether it implode
On Sun, 2015-08-02 at 17:58 -0600, Chris Murphy wrote:
> > Is this a 32-bit system by any chance?
>
> Duh. Subject.
Right.
> If you know or are willing to learn how to setup netconsole you might
> be able to capture the call trace for a bug report (I just attach the
> entire thing I collect rath
> Is this a 32-bit system by any chance?
Duh. Subject.
If you know or are willing to learn how to setup netconsole you might
be able to capture the call trace for a bug report (I just attach the
entire thing I collect rather than "snipping here"). Switching to a
debug version of the problem kerne
On Sun, Aug 2, 2015 at 4:22 PM, Patrick O'Callaghan
wrote:
> On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote:
>> > I'll try updating again tomorrow before I report anything.
>>
>> That sort of inconsistency leads one to suspect a hardware issue.
>> Perhaps a fan that's not running so things
On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote:
> > I'll try updating again tomorrow before I report anything.
>
> That sort of inconsistency leads one to suspect a hardware issue.
> Perhaps a fan that's not running so things are too hot, a power
> supply
> that's dying, dirty memory conne
hmm. I don't know if I'm in the same experience or not. I'm running
fedora 21 and upgraded to kernel 4.0.8 from 4.0.7 on 7/19. I didn't
have any issues until about the 26th. But then my system started to
lock up. It wasn't just GNOME but direct access was locked -- ie no
response via keyboard,
On Thu, Jul 30, 2015 at 4:43 PM, Patrick O'Callaghan
wrote:
> On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote:
>> On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan" <
>> pocallag...@gmail.com> wrote:
>>
>> > This is happening every few minutes since I updated today:
>> >
>> > Jul 30 1
On Thu, 2015-07-30 at 16:13 -0700, Rick Stevens wrote:
> On 07/30/2015 03:43 PM, Patrick O'Callaghan wrote:
> > On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote:
> > > On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan" <
> > > pocallag...@gmail.com> wrote:
> > >
> > > > This is happeni
On 07/30/2015 03:43 PM, Patrick O'Callaghan wrote:
On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote:
On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan" <
pocallag...@gmail.com> wrote:
This is happening every few minutes since I updated today:
Jul 30 18:26:21 Bree kernel: BUG: unab
On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote:
> On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan" <
> pocallag...@gmail.com> wrote:
>
> > This is happening every few minutes since I updated today:
> >
> > Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL
> > pointer
Hello Ranjan,
Yes I'm Real. To prove I'm real first off.. You are Ranjan Maitra and your
mail Id users@lists.fedoraproject.org
I was just taking a quick shower and I heard my phone vibrate, my hair isnt
even close to being dry yet but I wanted to quickly check my email to see if it
was you wr
On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan"
wrote:
> This is happening every few minutes since I updated today:
>
> Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer
> dereference at 0288
> Jul 30 18:26:21 Bree kernel: IP: []
> __kmalloc_node_trac
On Thu, Jul 30, 2015 at 11:54 AM, Patrick O'Callaghan
wrote:
> This is happening every few minutes since I updated today:
>
> Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer
> dereference at 0288
> Jul 30 18:26:21 Bree kernel: IP: []
> __kmalloc_node_track_call
This is happening every few minutes since I updated today:
Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL pointer
dereference at 0288
Jul 30 18:26:21 Bree kernel: IP: []
__kmalloc_node_track_caller+0x1c4/0x320
Going to try booting the previous kernel.
poc
--
users
On 04.04.2015 14:01, Patrick O'Callaghan wrote:
...
>
> Mine all use UUID. These are the two entries (not working, working):
>
> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnul
> inux-3.13.5-202.fc2
On 04/04/2015 04:02 PM, Patrick O'Callaghan wrote:
On Sat, 2015-04-04 at 12:45 -0700, Joe Zeff wrote:
On 04/04/2015 06:19 AM, Paul Cartwright wrote:
then grub2-install /dev/sda ( assuming sda is where you have grub installed)
Unless you think there's something wrong with grub, that shouldn't
On Sat, 2015-04-04 at 12:45 -0700, Joe Zeff wrote:
> On 04/04/2015 06:19 AM, Paul Cartwright wrote:
> > then grub2-install /dev/sda ( assuming sda is where you have grub installed)
>
> Unless you think there's something wrong with grub, that shouldn't be
> needed.
I also thought that grub2 wasn'
On 04/04/2015 06:19 AM, Paul Cartwright wrote:
then grub2-install /dev/sda ( assuming sda is where you have grub installed)
Unless you think there's something wrong with grub, that shouldn't be
needed.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription o
On Sat, 4 Apr 2015 13:57:39 -0400 Tom Horsley wrote:
> On Sat, 04 Apr 2015 18:50:39 +0100
> Patrick O'Callaghan wrote:
>
> > No idea. Obviously not something I expected. I would assume a problem
> > with the yum install script but no-one else seems to have mentioned it.
>
> I just updated my f2
On Sat, 2015-04-04 at 13:57 -0400, Tom Horsley wrote:
> On Sat, 04 Apr 2015 18:50:39 +0100
> Patrick O'Callaghan wrote:
>
> > No idea. Obviously not something I expected. I would assume a problem
> > with the yum install script but no-one else seems to have mentioned it.
>
> I just updated my f21
On Sat, 2015-04-04 at 09:19 -0400, Paul Cartwright wrote:
> On 04/04/2015 08:28 AM, Patrick O'Callaghan wrote:
> > On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
> >> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> >> fedora --class gnu-linux --class gnu --class
On Sat, 04 Apr 2015 18:50:39 +0100
Patrick O'Callaghan wrote:
> No idea. Obviously not something I expected. I would assume a problem
> with the yum install script but no-one else seems to have mentioned it.
I just updated my f21 partition and got this new kernel. It built
the initrd and boots ju
On Sat, 2015-04-04 at 10:33 -0600, jd1008 wrote:
>
> On 04/04/2015 06:01 AM, Patrick O'Callaghan wrote:
> > menuentry 'Fedora (3.19.3-200.fc21.x86_64)
> Why is initrd missing for 3.19.3-200 ??
No idea. Obviously not something I expected. I would assume a problem
with the yum install script but no
On 04/04/2015 06:01 AM, Patrick O'Callaghan wrote:
menuentry 'Fedora (3.19.3-200.fc21.x86_64)
Why is initrd missing for 3.19.3-200 ??
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora
On 04/04/2015 08:28 AM, Patrick O'Callaghan wrote:
> On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
>> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
>> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
>> 'gnul
>> inux-3.13.5-202.fc20.x86_64-a
On Sat, 2015-04-04 at 13:01 +0100, Patrick O'Callaghan wrote:
> menuentry 'Fedora (3.19.3-200.fc21.x86_64) 21 (Twenty One)' --class
> fedora --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnul
> inux-3.13.5-202.fc20.x86_64-advanced-6a9a800c-309b-4b69-b269-884ad495e7b9' {
>
On Sat, 2015-04-04 at 07:52 -0400, Paul Cartwright wrote:
> On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> > (0,0)
> >
> > Maybe something wrong in grub.conf? The previous ker
On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> (0,0)
>
> Maybe something wrong in grub.conf? The previous kernel boots fine.
>
> poc
my entries show UUID, not block..
linux16 /boot/
On 04/04/2015 07:45 AM, Patrick O'Callaghan wrote:
> As I suspected, the nVidia thing does seem to be a red herring. I
> rebooted and copied the last line of the stack trace:
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block
> (0,0)
>
>
sion number as
> the latest kmod, so I don't know if this is even going to fix the
> problem rather than open another can of worms. There isn't anything in
> the stack trace that mentions nVidia so all this may just be a red
> herring.
As I suspected, the nVidia thing does seem
On Dec 30, 2013, at 8:26 PM, Sean Darcy wrote:
> Kernel driver in use: tg3
>
>
> Not sure what to do with this.
Reboot, at grub menu highlight the f20 kernel option, hit e to edit, find the
linux command line, remove quiet rhgb, add rd.blacklist=tg3 and then F10 to
boot.
Chris Murphy
On 12/30/2013 06:39 PM, Chris Murphy wrote:
On Dec 30, 2013, at 3:41 PM, Sean Darcy wrote:
Sadly, it's a real kernel panic. Everything stops. I can't even reboot. It's a
good thing there's a power cord!
I'll copy what's on the screen, and submit it as a bug
On Dec 30, 2013, at 3:41 PM, Sean Darcy wrote:
>
> Sadly, it's a real kernel panic. Everything stops. I can't even reboot. It's
> a good thing there's a power cord!
>
> I'll copy what's on the screen, and submit it as a bug report. Maybe som
On 12/30/2013 11:38 AM, Chris Murphy wrote:
On Dec 29, 2013, at 5:11 PM, Sean Darcy wrote:
Updated to F19, kernel-3.12.5-200.fc19.x86_64.
On boot I get a kernel panic around [2.2]. The trace that's on the screen is
about smp, timers, hpet. Can't read quickly enough to see wha
On Dec 29, 2013, at 5:11 PM, Sean Darcy wrote:
> Updated to F19, kernel-3.12.5-200.fc19.x86_64.
>
> On boot I get a kernel panic around [2.2]. The trace that's on the screen is
> about smp, timers, hpet. Can't read quickly enough to see what actually
> happened.
T
Updated to F19, kernel-3.12.5-200.fc19.x86_64.
On boot I get a kernel panic around [2.2]. The trace that's on the
screen is about smp, timers, hpet. Can't read quickly enough to see what
actually happened.
/var/log/messages has no log of the kernel boot. Shouldn'
On 20.07.2013 02:59, Jim wrote:
…
> chroot /mnt/sysimage
> su
> cd /boot/grub2
> vi grub.cfg
>
> To the first Menu-list and remove NEW kernel , so it will boot on second
> older kernel.
>
> Am i using the best procedure to get rid of the NEW kernel ?
rpm -e foobar
poma
--
users mailing list
Fedora 18
Did a update and reboot, got a kernel panic in NEW kernel can't get into
Linux.
At Bootup at kernel Window I tried to hit Down-Arrow to goto second
kernel in menu but hitting Down-Arrow won't respond.
I guess i will have to go into the back door with a Fedora-18-Netin
placing systemd
with an earlier version? And what could have been the reason for the
kernel panic in the first place? An unfortunate race condition during
'yum update' that I just happened to run into? Some unfortunate
combination of services and configuration?
/Markus
--
users maili
Reindl Harald writes:
some years ago you had the possibility to boot from
install DVD in rescue mode and "chroot /sysimage"
but these days all this extended options seems to
go away or perfectly hidden
I'm pretty sure that the F18 install image has a boot option for rescue mode
that'll autom
Am 21.01.2013 20:01, schrieb Bruno Wolff III:
> On Mon, Jan 21, 2013 at 19:59:30 +0100,
> Markus Lindholm wrote:
>>
>> What now, how can I repair the system?
>
> Normally, you want to reboot with the previous kernel
you missed "I've got two kernel versions to choose from,
3.6.10-4 and 3.7.2.
On Mon, Jan 21, 2013 at 19:59:30 +0100,
Markus Lindholm wrote:
What now, how can I repair the system?
Normally, you want to reboot with the previous kernel.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mai
Hi
I've run into a nasty problem with kernel panic during boot. I did a
fresh installation of F18 last Wednesday and it was a smooth
experience, but then yesterday I did a 'yum update' that ended up
causing a kernel panic (there wasn't much more happening on the
machine at
On Mon, 11 Jun 2012 23:25:40 +0800
Ed Greshko wrote:
> Does you camera support taking movies? If so, you can always step through
> it :-)
Not at a high enough resolution to read anything :-).
If only I could squash the annoying behavior of the reboot process
insisting on clearing the scre
On 06/11/2012 11:03 PM, Tom Horsley wrote:
> I'm no longer as certain this has anything to do with NFS.
> Even if I umount all NFS filesystems, I still panic at
> reboot when running 3.4.0. I did go ahead and add a bug
> even without any info available from the walkback:
>
> https://bugzilla.redhat
I'm no longer as certain this has anything to do with NFS.
Even if I umount all NFS filesystems, I still panic at
reboot when running 3.4.0. I did go ahead and add a bug
even without any info available from the walkback:
https://bugzilla.redhat.com/show_bug.cgi?id=830862
--
users mailing list
use
On 11/06/12 12:56, Nicolae Ghimbovschi wrote:
I have regular system hangs after some time with the latest kernel
3.4.0. No logs.
I have and nvidia proprietary drivers. So not sure what piece is causing this.
Since "preupgrading" to F17, I can't even boot 3.4. Still running on
F16's 3.3 atm.
h to a different boot partition, and I wound up
> with the system totally frozen and the tail end of a
> kernel panic on my screen with various nfs_* routine
> names included in the walkback.
>
> Unfortunately no information was recorded in any logs,
> so I have nothing
I typed "reboot" on my f17 desktop today to temporarily
switch to a different boot partition, and I wound up
with the system totally frozen and the tail end of a
kernel panic on my screen with various nfs_* routine
names included in the walkback.
Unfortunately no information was recor
pdate -
but that's another story). It must have updated the Kernel because the
next day when I turned on the PC I had a kernel panic (details below)
and the machine failed to boot.
Looks like either dracut didn't put the driver you need for your hard
drive in the ramdisk image or the gru
2.7-1.fc16.i686 PAE)
Loading initial ramdisk ...
[ 2.957551] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block (0,0)
Looks like a busted initramfs to me. Something might've gotten broken during
the automatic update.
First-ly, carefully compare the command lines in gr
1 - 100 of 153 matches
Mail list logo
