Re: Kernel Panic - V6.2 - Reseved memory issue

> > > 07e93680 > > > [ 9.793035] x8 : 0020 x7 : ffff01d2b100 x6 : > > > 0007 > > > [ 9.793037] x5 : 0020 x4 : 8800 x3 : > > > 0001 > > > [ 9.793040] x

Re: Kernel Panic - V6.2 - Reseved memory issue

> > 9dc91fff > > [ 9.793031] x11: 0004 x10: 0001 x9 : > > 07e93680 > > [ 9.793035] x8 : 0020 x7 : 01d2b100 x6 : > > 0007 > > [ 9.793037] x5 : 00000020 x4 : 8800 x3 : > >

Kernel Panic - V6.2 - Reseved memory issue

Hi, I am trying to fix a kernel panic I am seeing on my vim3 board (Amlogic A311D). I don't have enough knowledge about this area, but my current guess is the kernel is using a piece of memory belonging to ARM-trusted firmware that I shouldn't. Log: [ 9.792966] SError Interrupt on

Re: REPOST : Kernel panic when try to install Rocky 8.4

you use newer kernel version provided by elrepo. Have you tried it? > Thanks, > Axel > > --- Original Message --- > On Monday, November 7th, 2022 at 14:27, Mulyadi Santosa < > mulyadi.sant...@gmail.com> wrote: > > > > On Mon, Nov 7, 2022, 18:04 mavis w

Re: REPOST : Kernel panic when try to install Rocky 8.4

As Greg KH says on the mailing list: A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing

Re: REPOST : Kernel panic when try to install Rocky 8.4

I have already tried all versions 8.x. Only 8.0 works. FYI, even rocky linux 9.0 doesn't work. Thanks, Axel --- Original Message --- On Monday, November 7th, 2022 at 14:27, Mulyadi Santosa wrote: > On Mon, Nov 7, 2022, 18:04 mavis wrote: > >> Nope, the kernel panic

Re: REPOST : Kernel panic when try to install Rocky 8.4

On Mon, Nov 7, 2022, 18:04 mavis wrote: > Nope, the kernel panic happens when the kernel boots, before the > installation window. > > I tried to boot a disk where rocky linux 8.4 is already installed and the > same things happen. > > Thanks, > Axel > Try to use newer

Re: REPOST : Kernel panic when try to install Rocky 8.4

Nope, the kernel panic happens when the kernel boots, before the installation window. I tried to boot a disk where rocky linux 8.4 is already installed and the same things happen. Thanks, Axel --- Original Message --- On Monday, November 7th, 2022 at 11:19, Mulyadi Santosa wrote

Re: REPOST : Kernel panic when try to install Rocky 8.4

On Fri, Nov 4, 2022 at 4:35 PM mavis wrote: > Hi All, > > I tried to install Rocky linux 8.4 (kernel *4.18.0-305*) but when the > kernel starts, it result to "*Kernel Panic - not syncing : Timeout: Not > all CPUs entered broadcast exception handler*". > I tried t

Re: REPOST : Kernel panic when try to install Rocky 8.4

when the kernel > > starts, it result to > > "Kernel Panic - not syncing : Timeout: Not all CPUs entered broadcast > > exception handler". > > > > I tried to use other distribs (Centos ; AlmaLinux) and I think this problem > > is related to the k

Re: REPOST : Kernel panic when try to install Rocky 8.4

On Fri, 04 Nov 2022 15:04:43 +0530, mavis wrote: > Hi All, > > I tried to install Rocky linux 8.4 (kernel 4.18.0-305) but when the kernel > starts, it result to > "Kernel Panic - not syncing : Timeout: Not all CPUs entered broadcast > exception handler". >

REPOST : Kernel panic when try to install Rocky 8.4

Hi All, I tried to install Rocky linux 8.4 (kernel 4.18.0-305) but when the kernel starts, it result to "Kernel Panic - not syncing : Timeout: Not all CPUs entered broadcast exception handler". I tried to use other distribs (Centos ; AlmaLinux) and I think this problem is related to

Re: Kernel Panic

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&#x

RE: Kernel Panic

Hello, We downgraded to older kernel. We still facing the same Kernel Panic with different Kernel. Christophe Dumont Ligne directe : 0476842574 De : Valdis Kletnieks De la part de Valdis Kletnieks Envoyé : mercredi 16 octobre 2019 16:17 À : Christophe DUMONT Cc

Re: Kernel Panic

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

RE: Kernel Panic

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 >

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. It says nothing at all about a memory leak, and as I already

RE: Kernel Panic

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.

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.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 &quo

Re: Kernel Panic

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: h

Kernel Panic

Hello Kernel World, 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 ? Christophe [cid:image001.png@01

Re: QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown

On Wed, Jun 19, 2019 at 10:05:54PM -0600, Manuel Quintero Fonseca wrote: > thank you all, I will review the information There is also a nice tool which makes it easy to run a QEMU virtual machine with locally built kernel: https://git.kernel.org/pub/scm/utils/kernel/virtme/virtme.git/ __

Re: QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown

les, it gives me two problems, I hope you can >> guide me. >> >> $qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r` >> >> end Kernel panic - not sysncing: VFS: Unable to mount toor fs on >> unknown-block(0,0) >> >> >> aku@openSUSE:~> sudo qemu-syste

Re: QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown

ews-and-blog/blog/2017/01/16/setting-up-qemu-kvm-for-kernel-development/ > > Following the first examples, it gives me two problems, I hope you can > guide me. > > $qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r` > > end Kernel panic - not sysncing: VFS: Unable to mou

QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown

first examples, it gives me two problems, I hope you can guide me. $qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r` end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown-block(0,0) aku@openSUSE:~> sudo qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r` [sudo] passw

Re: [linux-3.12.19] - kernel panic observed

On Tue, 10 Jul 2018 12:08:25 +0530, Sriram said: > I m working on linux-3.12.19 kernel. You have our condolences. Note that the fix for your problem has probably already been found, somewhere in the millions of lines of changes since then. [/usr/src/linux-next] git diff --shortstat v3.12 next-20

Re: [linux-3.12.19] - kernel panic observed

f length of the IPv6 packet is more than 1340, application does the IPv6 fragmentation and 2 fragments are written to raw socket. If I run this application using a script continously, there is no issue observed for around 30-40 mins. After that we see kernel panic with the stack trace like below. U

Re: [linux-3.12.19] - kernel panic observed

On Tue, Jul 10, 2018 at 12:08:25PM +0530, Sriram wrote: > Hi, > > I m working on linux-3.12.19 kernel. Wow that is old. And unsupported and obsolete and very very very insecure. Please work on updating to a newer kernel version that the community can help you out with (like 4.14 or 4.17). If y

[linux-3.12.19] - kernel panic observed

issue observed for around 30-40 mins. After that we see kernel panic with the stack trace like below. Unable to handle kernel paging request for data at address 0x04d0 Faulting instruction address: 0xc0789578 Oops: Kernel access of bad area, sig: 11 [#1] SMP NR_CPUS=24 CoreNet Generic

Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

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:

Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

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).

Fwd: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

-- Forwarded message -- From: shobhit bhadani Date: Tue, Aug 16, 2016 at 4:46 PM Subject: Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x000b To: Pranay Srivastava Hi, >Hi >On Tuesday, August 16, 2016, shobhit bhadani wrote: >> Hi, >

Re: Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

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

Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

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 a User-space Issue ?* 17:10:09.0464-04:00 - 17:10:09.

Re: Kernel panic debugging

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

Re: Kernel panic debugging

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

Kernel panic debugging

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. Call Trace: [] get_pageblock_flags_group+0xa8/0xd0 [] suitable_migration_target+0x1c/0x68 [] compaction_al

Re: Kernel panic debugging

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: > [

Kernel panic debugging

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. Call Trace: [] get_pageblock_flags_group+0xa8/0xd0 [] suitable_migration_target+0x1c/0x68 [] compaction_al

Re: Kernel panic after insmod

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

Re: Kernel panic after insmod

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-

Re: Kernel panic after insmod

> 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

Re: Kernel panic after insmod

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

Kernel panic after insmod

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/ #include MODULE_LICENSE("GPL"); int __init init(void) __attrib

Re: Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

On Tue, Mar 8, 2016 at 11:03 AM, 张云 wrote: > > You can circumvent the grub-install bug by substituting a USB memory for > the disk image. > > 发自 网易邮箱大师 > ​Ok, thanks! -Patrick​ ___ Kernelnewbies mailing list Kernelnewbies

回复：Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

You can circumvent the grub-install bug by substituting a USB memory for the disk image. 发自 网易邮箱大师 在2016年03月09日 00:56，Patrick 写道: The problem is caused by the command below mkfs -t vfat /dev/loop0 /dev/loop0 is the whole disk, and /dev/loop0p1 is the partition. The command make a file

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

> > The problem is caused by the command below > > mkfs -t vfat /dev/loop0 > > > /dev/loop0 is the whole disk, and /dev/loop0p1 is the partition. > > The command make a file system on the disk, thus overrides the disk’s > partition table. > > I guess that it is the partition on which you want to ma

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

> On Mar 8, 2016, at 7:29 AM, Patrick wrote: > > On Fri, Mar 4, 2016 at 9:09 PM, 张云 mailto:zyun...@163.com>> > wrote: > First your must know exactly how linux boot (not at source code level). > > Most recent linux distributions boot as > > grub —> kernel —> initramfs’ /init executable

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

On Fri, Mar 4, 2016 at 9:09 PM, 张云 wrote: > First your must know exactly how linux boot (not at source code level). > > Most recent linux distributions boot as > > grub —> kernel —> initramfs’ /init executable > > All the userspace affair is started by initramfs’ /init. Kernel no longer >

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

> > What filesystem is on the /dev/sda image that qemu is using? You'll need > to > ​​ > ​ > either build your kernel with the support for that built into the kernel, > or an initrd that modprobes the filesystem module, and then mounts the > filesystem (then there's a few fun and games involved in

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

ing to a loopback device associated with > the disk image. However, at some point far into the boot process, I get a > kernel panic. I can't read the beginning of the error messages that the > kernel prints, because the errors run off the screen. > > I copied the bzImage onto the d

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

On Fri, 04 Mar 2016 16:27:35 -0700, Patrick said: > [4.413323] No filesystem could mount root, tried: ext3 ext2 ext4 vfat > fuseblk > [4.415310] Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,0) > > So, I think maybe now the kernel is m

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

6 ram11 (driver?) [4.353597] 010c 65536 ram12 (driver?) [4.354517] 010d 65536 ram13 (driver?) [4.354977] 010e 65536 ram14 (driver?) [4.358393] 010f 65536 ram15 (driver?) [ 4.359420] 0b00 1048575 sr0 driver: sr [4.360499] 0800

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

> On 04 Mar 2016, at 23:50, Patrick wrote: > ​Thanks for the response.​ I had seen that StackOverflow post and done that a > couple of days ago. I was hoping there was another answer, since I wouldn't > be able to do that if I weren't using QEMU. > If you weren’t using Qemu I’d point you at ne

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

e disk image. However, at some point far into the boot process, I > > get a kernel panic. I can't read the beginning of the error messages that > > the kernel prints, because the errors run off the screen. > > > You should be able to persuade qemu to be a bit more helpful

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

On 2016-03-04 11:38:33 (-0700), Patrick wrote: > I was able to install SYSLINUX on a disk image and get the kernel I built > to start booting Linux with QEMU pointing to a loopback device associated > with the disk image. However, at some point far into the boot process, I > get a ker

Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

Hello, I was able to install SYSLINUX on a disk image and get the kernel I built to start booting Linux with QEMU pointing to a loopback device associated with the disk image. However, at some point far into the boot process, I get a kernel panic. I can't read the beginning of the error mes

Re: Kernel Panic in FIPS mode

PS mode is >> enabled by checking the following configs: >> >> CONFIG_CRYPTO_FIPS=y >> CONFIG_CRYPTO_TEST=y >> >> Following RH docs, initramfs was regenerated using dracut-fips (el6). >> I also generated hmac signed vmlinuz during the compilation. >> >

Re: Kernel Panic in FIPS mode

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 sta

Re: Kernel Panic in FIPS mode

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

Re: Kernel Panic in FIPS mode

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

Re: Kernel Panic in FIPS mode

llowing configs: > > CONFIG_CRYPTO_FIPS=y > CONFIG_CRYPTO_TEST=y > > Following RH docs, initramfs was regenerated using dracut-fips (el6). > I also generated hmac signed vmlinuz during the compilation. > > During boot, kernel panics with the following trace: > kernel line

Re: Kernel Panic in FIPS mode

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

Kernel Panic in FIPS mode

boot, kernel panics with the following trace: kernel line has the arguments, 'fips=1 boot=/dev/sda1'. "end Kernel Panic - not syncing: Module crc32c_intel signature verification failed in FIPS mode" Some additional info: It seems under fips mode, initrd runs, './sbin

Re: kernel panic

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: > []

kernel panic

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: [] __do_kernel_fault.part.5+0x70/0x84 [] do_bad_area+0x90/0x94 [] do_transla

Re: v3.15 kernel panic, bisecting didn't help

On Tue, Jun 10, 2014 at 9:02 AM, wrote: > On Tue, 10 Jun 2014 08:26:12 -0500, Greg Donald said: > >> the end. All 7 of the bisected kernels I built yesterday boot just >> fine. > > Just to clarify - did 'git bisect' report a 'first bad commit is '? My last "git bisect good" reported this:

Re: v3.15 kernel panic, bisecting didn't help

On Tue, 10 Jun 2014 08:26:12 -0500, Greg Donald said: > the end. All 7 of the bisected kernels I built yesterday boot just > fine. Just to clarify - did 'git bisect' report a 'first bad commit is '? Just wondering if the bisect in fact finished, or if you had an 8th bisect still to do

Re: v3.15 kernel panic, bisecting didn't help

between those two versions that is now causing a kernel panic on two identical systems, and doing a git bisect doesn't turn up a meaningful answer at the end. All 7 of the bisected kernels I built yesterday boot just fine. Thanks, -- Greg Donald ___

Re: v3.15 kernel panic, bisecting didn't help

Greg Donald writes: > On Tue, Jun 10, 2014 at 4:29 AM, Bjørn Mork wrote: >> Greg Donald writes: >> >>> [0.00] Linux version 3.15.0-1+ (root@mars) (gcc version 4.7.2 >> >> What's with the '+'? Do you have some commit on top of v3.15? If so, >> did you include that in your bisect? > > Th

Re: v3.15 kernel panic, bisecting didn't help

On Tue, Jun 10, 2014 at 4:29 AM, Bjørn Mork wrote: > Greg Donald writes: > >> [0.00] Linux version 3.15.0-1+ (root@mars) (gcc version 4.7.2 > > What's with the '+'? Do you have some commit on top of v3.15? If so, > did you include that in your bisect? The + is something Debian's make-k

Re: v3.15 kernel panic, bisecting didn't help

Greg Donald writes: > [0.00] Linux version 3.15.0-1+ (root@mars) (gcc version 4.7.2 What's with the '+'? Do you have some commit on top of v3.15? If so, did you include that in your bisect? Bjørn ___ Kernelnewbies mailing list Kernelnewbie

Re: v3.15 kernel panic, bisecting didn't help

On Mon, Jun 9, 2014 at 3:47 PM, wrote: > On Mon, 09 Jun 2014 15:35:20 -0500, Greg Donald said: >> I can boot v3.15.0-rc8 but not v3.15.0 (full kernel panic below). >> >> I tried bisecting, I did >> >> git bisect v3.15 v.3.15-rc8 >> >> After 7 compile

Re: v3.15 kernel panic, bisecting didn't help

On Mon, 09 Jun 2014 15:35:20 -0500, Greg Donald said: > I can boot v3.15.0-rc8 but not v3.15.0 (full kernel panic below). > > I tried bisecting, I did > > git bisect v3.15 v.3.15-rc8 > > After 7 compile and reboot cycles I don't think I was able to find the > bad co

v3.15 kernel panic, bisecting didn't help

I can boot v3.15.0-rc8 but not v3.15.0 (full kernel panic below). I tried bisecting, I did git bisect v3.15 v.3.15-rc8 After 7 compile and reboot cycles I don't think I was able to find the bad commit. Every bisection booted with no problems. I ran "git bisect good" each time

Re: kernel panic while doing dma_alloc_coherent() function

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 dev

kernel panic while doing dma_alloc_coherent() function

Hi guys I am trying to port opensource kernel 3.0.11 onto MSM chipset. 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

Re: Kernel panic when using initramfs instead of initrd

ted the init cpio image with a command like this: > > find | cpio -H newc -o | gzip -9 > initrd.gz > > The boot arguments are the same. When I boot, what I have is a kernel panic > with the following details: > > List of all partitions: > No filesystem could mount ro

Kernel panic when using initramfs instead of initrd

find | cpio -H newc -o | gzip -9 > initrd.gz The boot arguments are the same. When I boot, what I have is a kernel panic with the following details: List of all partitions: No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block

Re: kernel panic in sample block device driver

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

Re: kernel panic in sample block device driver

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

Re: kernel panic in sample block device driver

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

kernel panic in sample block device driver

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 information available over the internet. My curre

Re: suse 11 kernel panic

https://bugzilla.kernel.org/show_bug.cgi?id=16991 this link maybe help？ 2012-07-25 c265n46 发件人：tingwei liu 发送时间：2012-07-24 07:39 主题：suse 11 kernel panic 收件人："kernelnewbies" 抄送： Suse 11 SP1 kernel panic。 I can't debug it without debuginfo. Who can give me a link of sels

Re: suse 11 kernel panic

> BTW, I saw these lines in the oops message: > kernel: [3077010.856312] last sysfs file: > /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map > > does your program somehow read or write to this sysfs entry? This program doesn't operate this file. But call some syscall,such as sched_setaffin

Re: suse 11 kernel panic

Hi... On Tue, Jul 24, 2012 at 3:39 PM, tingwei liu wrote: > 24 cores BTW, I saw these lines in the oops message: kernel: [3077010.856312] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map does your program somehow read or write to this sysfs entry? > Right, This is my

Re: suse 11 kernel panic

On Tue, Jul 24, 2012 at 12:39 PM, Mulyadi Santosa wrote: > Hi > > On Tue, Jul 24, 2012 at 6:38 AM, tingwei liu wrote: >> Suse 11 SP1 kernel panic。 >> >> I can't debug it without debuginfo. Who can give me a link of sels >> 2.6.32.12-0.7.default.debu

Re: suse 11 kernel panic

Hi On Tue, Jul 24, 2012 at 6:38 AM, tingwei liu wrote: > Suse 11 SP1 kernel panic。 > > I can't debug it without debuginfo. Who can give me a link of sels > 2.6.32.12-0.7.default.debug or give some advise. Better just report it to the SuSE novell team about this bug...so th

suse 11 kernel panic

Suse 11 SP1 kernel panic。 I can't debug it without debuginfo. Who can give me a link of sels 2.6.32.12-0.7.default.debug or give some advise. Thanks for any reply! kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer dereference at 0008 kernel: [3077010.85629

Re: kernel panic after VFS mount in FPGA board

Tag_ABI_HardFP_use: SP and DP Tag_DIV_use: Not allowed If i use this binary in for root file system,with init=/linuxrc I'm getting undefined instruction error and kernel panics init (1): undefined instruction: pc=40047930 Code: aa80 0714 e3e0 e1a0f00e (eca0420c) Kernel panic -

Re: kernel panic after VFS mount in FPGA board

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=

kernel panic after VFS mount in FPGA board

Hi, I'm doing kernel porting to arm926 based FPGA board,very minimal setup (uart + timer only) 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. Below are the details #define PLAT_PHYS_OFFSET

Kernel panic - not syncing: junk in compressed archive

h the CONFIG_INITRAMFS_SOURCE option. An other way is to provide a configuration file to this option. I have tried all these methods but each time, the boot stops with the following message: Kernel panic - not syncing: junk in compressed archive I have googled on that but have not found relevant solution.

Re: Workqueue and kernel panic on device disconnect

Am 25.10.2011 23:29, schrieb Frank Schäfer: > Hi, > > I'm trying to use a workqueue in a usb driver for polling the states > of the device buttons. > That works fine, but when I disconnect the device, the kernel > sometimes explodes. > The machine turns off immediately, without saving a backtrace

Workqueue and kernel panic on device disconnect

Hi, I'm trying to use a workqueue in a usb driver for polling the states of the device buttons. That works fine, but when I disconnect the device, the kernel sometimes explodes. The machine turns off immediately, without saving a backtrace (I will try to make a photo tomorrow) The code: sta

Re: analysis of kernel panic logs.

On Tue, Sep 6, 2011 at 10:14 PM, Dave Hylands wrote: > Hi Sandeep, > > On Mon, Sep 5, 2011 at 1:37 AM, sandeep kumar > wrote: > ...snip... >> As our analysis for the problem goes, >> init being the critical process, when killed, platform called a system call >> to restart the kernel. >> is it co

Re: analysis of kernel panic logs.

Hi Sandeep, On Mon, Sep 5, 2011 at 1:37 AM, sandeep kumar wrote: ...snip... > As our analysis for the problem goes, > init being the critical process, when killed, platform called a system call > to restart the kernel. > is it correct or we missd something? I'm not sure. What exactly do you mean

Re: analysis of kernel panic logs.

Hi Dave, I want to share what is the problem and how it got fixed. The problem goes like this, The init process(init.c) of ANDROID parses "init.rc" file which specifies the actions to be done on a specific trigger. In our case mistakenly we specified the trigger,but no action. Due to which the p

Re: analysis of kernel panic logs.

Hi Sandeep, On Sun, Sep 4, 2011 at 10:51 PM, sandeep kumar wrote: > Hi Dave, > > The problem is solved. > But i have one doubt. > >>So the PC is 0, and the LR is C92F. That tells me that the code at >>C92F in your init process is trying to call a function through a NULL >>pointer. You can try dis

Re: analysis of kernel panic logs.

Hi Dave, The problem is solved. But i have one doubt. >So the PC is 0, and the LR is C92F. That tells me that the code at >C92F in your init process is trying to call a function through a NULL >pointer. You can try disassembling your init process. Something like >arm-eabi-objdump --disassemble i

  1   2   >