FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 08-31-2011, 07:49 PM
mike cloaked
 
Default kernel panic

On Wed, Aug 31, 2011 at 8:35 PM, mike cloaked <mike.cloaked@gmail.com> wrote:
> On Wed, Aug 31, 2011 at 7:12 PM, Hiisi <hiisi@fedoraproject.org> wrote:
>> On 31 August 2011 20:51, Bruno Wolff III <bruno@wolff.to> wrote:
>>> On Wed, Aug 31, 2011 at 14:03:39 +0200,
>>> *"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>>>>
>>>> How can I report the full set of
>>>> messages? (If not copying by hand??)
>>>
>>> It is relatively common for people to take a picture of the screen after
>>> a crash to capture a traceback or other information that won't be in any
>>> logs.
>>
>> When system freezes the only way of making a screenshot is take a
>> picture by camera, upload photo on the web and post the link here.
>
> Are any of the suggestions in the following link for getting a console
> output for info immediately prior to the crash helpful?
>
> http://wiki.openvz.org/Remote_console_setup
>

There is more about netconsole at
http://www.kernel.org/doc/Documentation/networking/netconsole.txt


--
mike c
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-31-2011, 07:51 PM
mike cloaked
 
Default kernel panic

On Wed, Aug 31, 2011 at 8:49 PM, mike cloaked <mike.cloaked@gmail.com> wrote:
> On Wed, Aug 31, 2011 at 8:35 PM, mike cloaked <mike.cloaked@gmail.com> wrote:
>> On Wed, Aug 31, 2011 at 7:12 PM, Hiisi <hiisi@fedoraproject.org> wrote:
>>> On 31 August 2011 20:51, Bruno Wolff III <bruno@wolff.to> wrote:
>>>> On Wed, Aug 31, 2011 at 14:03:39 +0200,
>>>> *"antonio.montagnani@alice.it" <antonio.montagnani@alice.it> wrote:
>>>>>
>>>>> How can I report the full set of
>>>>> messages? (If not copying by hand??)
>>>>
>>>> It is relatively common for people to take a picture of the screen after
>>>> a crash to capture a traceback or other information that won't be in any
>>>> logs.
>>>
>>> When system freezes the only way of making a screenshot is take a
>>> picture by camera, upload photo on the web and post the link here.
>>
>> Are any of the suggestions in the following link for getting a console
>> output for info immediately prior to the crash helpful?
>>
>> http://wiki.openvz.org/Remote_console_setup
>>
>
> There is more about netconsole at
> http://www.kernel.org/doc/Documentation/networking/netconsole.txt
>

Also

https://fedoraproject.org/wiki/Netconsole


--
mike c
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 10-24-2011, 02:45 AM
Vitor Eiji Justus Sakaguti
 
Default kernel panic

Hi,

Just a heads up to all users of broadcom-wl: a lot of people (myself
included) have been reporting kernel panics at boot time after upgrade
to current version, so if you're planing to upgrade, be sure to have a
live cd around to chroot into your system.
There are still no known workarounds other than blacklisting the wl
module (thus disabling wireless board) or removing the package.

[1] http://aur.archlinux.org/packages.php?ID=19514

Good luck!
Vitor
 
Old 10-24-2011, 02:52 AM
Dave Reisner
 
Default kernel panic

On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:
> Hi,
>
> Just a heads up to all users of broadcom-wl: a lot of people (myself
> included) have been reporting kernel panics at boot time after upgrade
> to current version, so if you're planing to upgrade, be sure to have a
> live cd around to chroot into your system.
> There are still no known workarounds other than blacklisting the wl
> module (thus disabling wireless board) or removing the package.
>
> [1] http://aur.archlinux.org/packages.php?ID=19514
>
> Good luck!
> Vitor

Or just blacklist the module from the kernel cmdline via
"modprobe.blacklist=wl". It appears to be a race condition that's
triggered when its loaded by udev during bootstrap. Loading it
afterwards (either from rc.local or manually) doesn't trigger the panic.

No need to freak out.

d
 
Old 10-24-2011, 03:44 AM
Vitor Eiji Justus Sakaguti
 
Default kernel panic

On Mon, Oct 24, 2011 at 12:52 AM, Dave Reisner <d@falconindy.com> wrote:
> On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:
>> Hi,
>>
>> Just a heads up to all users of broadcom-wl: a lot of people (myself
>> included) have been reporting kernel panics at boot time after upgrade
>> to current version, so if you're planing to upgrade, be sure to have a
>> live cd around to chroot into your system.
>> There are still no known workarounds other than blacklisting the wl
>> module (thus disabling wireless board) or removing the package.
>>
>> [1] http://aur.archlinux.org/packages.php?ID=19514
>>
>> Good luck!
>> Vitor
>
> Or just blacklist the module from the kernel cmdline via
> "modprobe.blacklist=wl".

Kind of what I said (less verbosely).

> It appears to be a race condition that's
> triggered when its loaded by udev during bootstrap. Loading it
> afterwards (either from rc.local or manually) doesn't trigger the panic.

It does for me.

> No need to freak out.

My point exactly.

Cheers
 
Old 10-24-2011, 04:35 AM
Gaetan Bisson
 
Default kernel panic

[2011-10-24 01:44:50 -0200] Vitor Eiji Justus Sakaguti:
> On Mon, Oct 24, 2011 at 12:52 AM, Dave Reisner <d@falconindy.com> wrote:
> > On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:
> >> Hi,
> >>
> >> Just a heads up to all users of broadcom-wl: a lot of people (myself
> >> included) have been reporting kernel panics at boot time after upgrade
> >> to current version, so if you're planing to upgrade, be sure to have a
> >> live cd around to chroot into your system.
> >> There are still no known workarounds other than blacklisting the wl
> >> module (thus disabling wireless board) or removing the package.
> >>
> >> [1] http://aur.archlinux.org/packages.php?ID=19514
> >>
> >> Good luck!
> >> Vitor
> >
> > Or just blacklist the module from the kernel cmdline via
> > "modprobe.blacklist=wl".
>
> Kind of what I said (less verbosely).

No. Dave's point is that you don't need a LiveCD: you can just add
"modprobe.blacklist=wl" as a parameter to your kernel in the boot
loader.

--
Gaetan
 
Old 10-24-2011, 10:58 AM
Vitor Eiji Justus Sakaguti
 
Default kernel panic

On Mon, Oct 24, 2011 at 2:35 AM, Gaetan Bisson <bisson@archlinux.org> wrote:
> [2011-10-24 01:44:50 -0200] Vitor Eiji Justus Sakaguti:
>> On Mon, Oct 24, 2011 at 12:52 AM, Dave Reisner <d@falconindy.com> wrote:
>> > On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:
>> >> Hi,
>> >>
>> >> Just a heads up to all users of broadcom-wl: a lot of people (myself
>> >> included) have been reporting kernel panics at boot time after upgrade
>> >> to current version, so if you're planing to upgrade, be sure to have a
>> >> live cd around to chroot into your system.
>> >> There are still no known workarounds other than blacklisting the wl
>> >> module (thus disabling wireless board) or removing the package.
>> >>
>> >> [1] http://aur.archlinux.org/packages.php?ID=19514
>> >>
>> >> Good luck!
>> >> Vitor
>> >
>> > Or just blacklist the module from the kernel cmdline via
>> > "modprobe.blacklist=wl".
>>
>> Kind of what I said (less verbosely).
>
> No. Dave's point is that you don't need a LiveCD: you can just add
> "modprobe.blacklist=wl" as a parameter to your kernel in the boot
> loader.

If you look at the comments, you'll see that blacklisting didn't work
for hermes14, so I thought other people might run into this problem as
well.
Better safe than sorry

But thanks for taking the time to look at this, everyone!
 
Old 12-21-2011, 10:55 PM
"TE Dukes"
 
Default Kernel Panic

Hello,

Just upgrade to 6.2 but have not been able to run a newer kernel than
2.6.32-131.12.1.el6.x86_64.

I'm getting the error at boot, Not syncing: VFS Unable to mount root fs on
unknown-block(0,0)

I have google this error and see a lot of the same but no clear answers.

Any help would be appreciated.

TIA

-Eddie

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-22-2011, 12:54 AM
"TE Dukes"
 
Default Kernel Panic

> -----Original Message-----
> From: centos-bounces@centos.org
> [mailto:centos-bounces@centos.org] On Behalf Of Edward Martinez
> Sent: Wednesday, December 21, 2011 9:29 PM
> To: centos@centos.org
> Subject: Re: [CentOS] Kernel Panic
>
> On 12/21/11 15:55, TE Dukes wrote:
> > Hello,
> >
> > Just upgrade to 6.2 but have not been able to run a newer
> kernel than
> > 2.6.32-131.12.1.el6.x86_64.
> >
> > I'm getting the error at boot, Not syncing: VFS Unable to
> mount root
> > fs on
> > unknown-block(0,0)
> >
> > I have google this error and see a lot of the same but no
> clear answers.
> >
> > Any help would be appreciated.
> >
> > TIA
> >
> > -Eddie
> >
> > _______________________________________________
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> >
>
> Have you read this? Somebody file a bug report about the
> same error as yours, and it turned out the error was caused
> by a missing
>
> initramfs. this may also be your case? issuing*dracut*creates it.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=632412

Yes, I saw that but was afraid to run that because I don't know what it
does.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-22-2011, 01:29 AM
Edward Martinez
 
Default Kernel Panic

On 12/21/11 15:55, TE Dukes wrote:
> Hello,
>
> Just upgrade to 6.2 but have not been able to run a newer kernel than
> 2.6.32-131.12.1.el6.x86_64.
>
> I'm getting the error at boot, Not syncing: VFS Unable to mount root fs on
> unknown-block(0,0)
>
> I have google this error and see a lot of the same but no clear answers.
>
> Any help would be appreciated.
>
> TIA
>
> -Eddie
>
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>

Have you read this? Somebody file a bug report about the same error
as yours, and it turned out the error was caused by a missing

initramfs. this may also be your case? issuing*dracut*creates it.

https://bugzilla.redhat.com/show_bug.cgi?id=632412




_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 09:41 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org