On Mon, Apr 3, 2023 at 12:29 PM Lucas Tanure wrote:
>
> On Sun, Apr 2, 2023 at 1:55 PM Bagas Sanjaya wrote:
> >
> > On Sun, Apr 02, 2023 at 09:10:36AM +0100, Lucas Tanure wrote:
> > > Log:
> > >
> > > [ 9.792966] SError Interrupt on CPU3, code 0xbf00 -- SError
> > > [ 9.792980] CPU: 3
On Sun, Apr 2, 2023 at 1:55 PM Bagas Sanjaya wrote:
>
> On Sun, Apr 02, 2023 at 09:10:36AM +0100, Lucas Tanure wrote:
> > Log:
> >
> > [ 9.792966] SError Interrupt on CPU3, code 0xbf00 -- SError
> > [ 9.792980] CPU: 3 PID: 3471 Comm: kded5 Tainted: G C 6.2.0 #1
> > [ 9.792985] Hardware
On Tue, Oct 22, 2019 at 09:38:59AM +, Christophe DUMONT wrote:
> Hello,
>
>
>
> We downgraded to older kernel. We still facing the same Kernel Panic with
> different Kernel.
Please contact your vendor for support, they are the only ones that can
support you as it's a very odd and old ke
: kernelnewbies@kernelnewbies.org
Objet : Re: Kernel Panic
On Wed, 16 Oct 2019 07:34:01 -, Christophe DUMONT said:
> What made me think about a memory leak is the message : Java Not Tainted
> 3.10.0-1062.1.1.el7.x86_64.=20
That just tells you that the currently executing process was java.
I
On Thu, Oct 17, 2019 at 07:48:49AM +, Christophe DUMONT wrote:
> We can put aside Java Memory Leak.
>
> I downgraded to kernel 3.10.0-957.27.2.el7.x86_64, there are no more crashes.
>
> The bug comes from ‘futex‘ syscall. What can causes that bug and how
> can i investigate ?
You can try to
de Valdis Kletnieks
Envoyé : mercredi 16 octobre 2019 16:17
À : Christophe DUMONT
Cc : kernelnewbies@kernelnewbies.org
Objet : Re: Kernel Panic
On Wed, 16 Oct 2019 07:34:01 -, Christophe DUMONT said:
> What made me think about a memory leak is the message : Java Not Tainted
>
On Wed, 16 Oct 2019 07:34:01 -, Christophe DUMONT said:
> What made me think about a memory leak is the message : Java Not Tainted
> 3.10.0-1062.1.1.el7.x86_64.=20
That just tells you that the currently executing process was java.
It says nothing at all about a memory leak, and as I already
Valdis Kletnieks
Envoyé : mardi 15 octobre 2019 22:20
À : Christophe DUMONT
Cc : kernelnewbies@kernelnewbies.org
Objet : Re: Kernel Panic
On Tue, 15 Oct 2019 07:21:18 -, Christophe DUMONT said:
> We're facing Kernel Panic on CentOS 7 since upgrading from 3.10.0-957 to
> 3.10.
On Tue, 15 Oct 2019 07:21:18 -, Christophe DUMONT said:
> We're facing Kernel Panic on CentOS 7 since upgrading from 3.10.0-957 to
> 3.10.0-1062. I'm thinking about a java memory leak, but not sure.
> Do you know what's going on here ?
Well, what made you think "Java memory leak"?
Java is u
On Tue, Oct 15, 2019 at 07:21:18AM +, Christophe DUMONT wrote:
> We're facing Kernel Panic on CentOS 7 since upgrading from 3.10.0-957 to
> 3.10.0-1062. I'm thinking about a java memory leak, but not sure.
> Do you know what's going on here ?
Looks similar to this: https://access.redhat.com/s
The first process that the *nix starts after booting up is init. The
init process
which has pid 1 live for as long as the host do not reboot. That message
means that something has made init exit prematurely. Check your init.d, systemd
or whatever init system you're using...
Regards,
2016-08-22 9:
On Wed, Aug 17, 2016 at 7:05 AM, shobhit bhadani wrote:
>
>>Which version of kernel are you using?
>
> I am using kernel 3.8
Are you from the past? 3.8 was released more than 3 years ago!, Around
the same day the metor exploted over Russia and the Pope resigned
(coincidence, I do not think so).
Hi
On Tuesday, August 16, 2016, shobhit bhadani wrote:
> Hi,
>
> I am new to kernel.
> What does this issue mean "not syncing: Attempted to kill init! "?
>
> Is this a user space issue?
>
> 17:10:09.0464-04:00 - Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b // Is this
On Thu, Aug 04, 2016 at 02:01:21PM +0530, Narasimha M wrote:
> Hi All,
>
> I am using linux-3.10.20 kernel and facing the below reported panic
> some times. As this is coming from general linux stack. Could you
> please guide how to debug these kind of panics.
That's a very old and obsolete kerne
Hi,
We are using that for some internal project.
On Thu, Aug 4, 2016 at 2:00 PM, Shubhrajyoti Datta
wrote:
>
>
> On Thu, Aug 4, 2016 at 1:52 PM, Narasimha M wrote:
>>
>> Hi All,
>>
>> I am using linux-3.10.20 kernel and facing the below reported panic
>
>
> why use this kernel
>
>>
>> some ti
On Thu, Aug 4, 2016 at 1:52 PM, Narasimha M wrote:
> Hi All,
>
> I am using linux-3.10.20 kernel and facing the below reported panic
>
why use this kernel
> some times. As this is coming from general linux stack. Could you
> please guide how to debug these kind of panics.
>
>
> Call Trace:
> [
Am 2016-06-26 18:38, schrieb Aruna Hewapathirane:
> And completely off-topic what are the options for some of us who very
> much
> wish to attend the Linux conference North America (
> http://events.linuxfoundation.org/events/linuxcon-north-america ) but
> simply cannot afford the standard registr
On Sun, Jun 26, 2016 at 12:38:29PM -0400, Aruna Hewapathirane wrote:
> > What exactly was the crash? And where did you find this kernel module
> > source from?
>
> Greg,
>
> A little digging around using Google threw this up :
> http://superuser.com/questions/1092083/how-to-disable-kill-command-
> What exactly was the crash? And where did you find this kernel module
> source from?
Greg,
A little digging around using Google threw this up :
http://superuser.com/questions/1092083/how-to-disable-kill-command-on-linux
If you scroll down you will see the exact same code :)
And completely of
On Sun, Jun 26, 2016 at 09:35:55AM +, Manavendra Nath Manav wrote:
> Can someone explain the following kernel module code. I'm not familiar with
> x86
> assembly so have problem understanding this part. Also it seems this code is
> able to modify the kernel stack.
>
> /**start
Thanks. I am taking the kernel from kernel.org not the one provided by
Red Hat or any other OS. AFAIU, certification or module signatures are
done during kernel compilation (by turning on MODULE_SIG*).
On Tue, Feb 23, 2016 at 2:02 PM, Leo Silva (a.k.a kirotawa)
wrote:
> If it's a kernel provide b
Thanks. I understand your point, but I am one of those people who
simply can't do an upgrade to the LTS kernel. Again, I think this
doesn't necessarily answer my question about FIPS and kernel panic.
An additional note, older kernels (2.6.x) and its RH derivatives,
works fine when started under FI
On Tue, Feb 23, 2016 at 02:41:37PM -0600, Tapas Sarangi wrote:
> Thanks for the reply.
> I am using and compiling kernel from kernel.org. I believe 3.18.27
> with patches is as new as in January of this year.
The 3.18 kernel was released in December of 2014, the .y patches on the
end of that rel
Thanks for the reply.
I am using and compiling kernel from kernel.org. I believe 3.18.27 with
patches is as new as in January of this year.
Sent from my iPhone
> On Feb 23, 2016, at 2:02 PM, Greg KH wrote:
>
>> On Tue, Feb 23, 2016 at 01:41:50PM -0600, Tapas Sarangi wrote:
>> I am recompi
If it's a kernel provide by a company, such as RHEL or SUSE, I'd recommend
to ask for them support/bugzilla.
Regarding FIPS/fipsmode, it's a kind of certification that is done by these
company with focus on specific hardware and Kernels, if just a bit is
different on a crypto algorithm it'll proba
On Tue, Feb 23, 2016 at 01:41:50PM -0600, Tapas Sarangi wrote:
> I am recompiling 3.18.27 on a platform derived from el6. FIPS mode is
> enabled by checking the following configs:
>
> CONFIG_CRYPTO_FIPS=y
> CONFIG_CRYPTO_TEST=y
If you are using a RHEL system, you need to contact Red Hat for sup
On Thu, Oct 15, 2015 at 6:23 PM, jinz...@wingtech.com
wrote:
> Dear all:
> I met a problem as below, what the function of walk_page_range??
> Exception Class: Kernel (KE)
> PC is at [] walk_page_range+0x3c/0x314
>
> Current Executing Process:
> [Binder_C, 3611][main, 354]
>
> Backtrace:
> []
On Mon, 22 Jul 2013 17:14:48 +0530, sandeep kumar said:
> While porting the SD card controller driver, i am seeing a kernel panic.
> While tracing with printk, i am struck at
>
> in arch/arm/mm/dma_mapping.c ,
> Function,
>
> static struct page *__dma_alloc_buffer(struct device *dev, size_t size,
Hi Ivan,
On Sun, May 5, 2013 at 1:44 PM, Ivan Nikolaev wrote:
...
> EVERYTHING WORKS if I enable in the kernel some filesystem (like ext2 or
> squashfs) and create the initrd image of that type and put inside the
> contents of the directory. Isolinux then boots the kernel this way:
>
> LABEL linu
On Wed, May 01, 2013 at 10:24:40PM +0530, Pranay Srivastava wrote:
> https://github.com/pranjas/block_driver
>
Thank you so much, looks pretty heavy-duty right now though!!!
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.ker
On 5/1/13, Kumar amit mehta wrote:
> Hi,
>
> I'm new to block layer in linux and to learn the same, I'm trying to
> come up with a sample memory based block device driver, with which I can
> experiment and learn along the way. I'm referring to sample code from
> the linux tree [1] and assorted inf
kernel panic logs?
On Wed, May 1, 2013 at 10:57 AM, Kumar amit mehta wrote:
> Hi,
>
> I'm new to block layer in linux and to learn the same, I'm trying to
> come up with a sample memory based block device driver, with which I can
> experiment and learn along the way. I'm referring to sample code
I am trying to create a root file systems using busybox for ARM926EJ-s
based board.
I'm using linaro tool chain 4.6.1(arm-linux-gnueabi-) in ubuntu 10.04
First step,I started with
make defconfig
CFLAGS=-march=armv5te make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
menuconfig
enabled only static bin
On 2012-04-11 19:03:42 (+0530), pcuser p wrote:
> I'm getting kernel panic after cramfs root file system is mounted,I am
> expecting to enter login prompt after root file system is mounted.
>
> Kernel cmd line : mem=32M console=ttySAC0,115200 root=/dev/ram0
> rootfstype=cramfs init=/linuxrc initr
boot option:
root=/dev/mtdblock1 rootfstype=ext3 rw console=ttyS0,115200
mtdparts=phys_mapped_flash:1024k(bootloader)ro,256k(product_info),256k(system_para),128k(exception_info),128k(bootloader_env),-(reserve);gen_nand.0:128M(root),-(usr)
boot logs:
Using octmgmt0 device
TFTP from server 10.10.10
2011/7/13 史星星(研六 福州) :
> Hi,
>
> I got a problem when trying to boot linux 2.6.32.13 on my Octeon
> CN5650 board.
>
> Booting logs below:
>
> ...omit….
>
> EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
>
> kjournald starting. Commit interval 5 seconds
>
> EXT
36 matches
Mail list logo
