Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
> On Fri, Jun 15, 2018 at 9:13 PM, Veluthakkal, Sreeram > wrote: >> Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 >> Empty summary info causes OOPS". > > -ENOMSEXCHANGE Nom sex change? Oh, I see. No, it never works in Exchange either AFAICT. Only ever serves to draw attention to the "recalled" mail and make more people read it. Perhaps that was the intent? :) -- dwmw2
Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
> On Fri, Jun 15, 2018 at 9:13 PM, Veluthakkal, Sreeram > wrote: >> Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 >> Empty summary info causes OOPS". > > -ENOMSEXCHANGE Nom sex change? Oh, I see. No, it never works in Exchange either AFAICT. Only ever serves to draw attention to the "recalled" mail and make more people read it. Perhaps that was the intent? :) -- dwmw2
Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
On Fri, Jun 15, 2018 at 9:13 PM, Veluthakkal, Sreeram wrote: > Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty > summary info causes OOPS". -ENOMSEXCHANGE -- Thanks, //richard
Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
On Fri, Jun 15, 2018 at 9:13 PM, Veluthakkal, Sreeram wrote: > Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty > summary info causes OOPS". -ENOMSEXCHANGE -- Thanks, //richard
Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty summary info causes OOPS".
Recall: PROBLEM: JFFS2 Empty summary info causes OOPS
Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty summary info causes OOPS".
PROBLEM: JFFS2 Empty summary info causes OOPS
Hi, [1.] Summary: JFFS2 Empty summary node info causes OOPS [2.] Description: Under stress situations on the filesystem, OOPs are observed. The OOPs points to empty summary node info bug. Confirmed that the filesystem is not full, not corrupted and is accessible. [3.] Keywords (i.e., modules, networking, kernel): filesystem [4.] Kernel information [4.1.] Kernel version (from /proc/version): 4.1.12 Driver version: jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [6.] Output of Oops.. Kernel BUG at c0268c78 [verbose debug info unavailable] Internal error: Oops - BUG: 0 [#1] SMP ARM Modules linked in: npcm750_rng dell_usbmuxdrv(O) g_edm_mass_storage3 vcd_dev(O) usb_storage sd_mod scsi_mod rng_core oprofile md4 g_edm_mass_storage2 des_generi c dell_regmem_adds(O) dell_pmdrv(O) dell_oom_notify(O) dell_msgbox(O) g_edm_mass _storage1 dell_fpdrv(O) dell_early_board(O) dell_ipmbdrv(O) dell_i2cdrv(O) dell_ cplddrv(O) g_edm_mass_storage cifs bonding g_edm_kbdmouse usb_f_ecm g_ether_usb arc4 aess_vkcsdrv(O) aess_smadrv(O) usb_f_rndis u_ether aess_pwmdrv(O) aess_pcim ailboxdrv(O) aess_mtddrv_spi_nor(O) aess_memdrv(O) libcomposite aess_fansensordr v(O) aess_dynairqdrv(O) aess_gpiodrv(O) aess_video(O) aess_biospostdrv(O) aess_k csdrv(O) aess_eventhandlerdrv(O) aess_adcsensordrv(O) CPU: 1 PID: 998 Comm: cfgmgrd Tainted: G O 4.1.12 Hardware name: NPCMX50 Chip family task: d7ccd340 ti: d7c8a000 task.ti: d7c8a000 PC is at jffs2_sum_write_sumnode+0x508/0x518 LR is at jffs2_sum_write_sumnode+0x508/0x518 pc : [] lr : [] psr: 600b0013 sp : d7c8ba90 ip : fp : d7c8bb80 r10: 00c4 r9 : d84510a8 r8 : 00200200 r7 : 0fa4 r6 : d84510a8 r5 : d9aac000 r4 : d98ca5c0 r3 : r2 : dcba772c r1 : dcba52dc r0 : 0044 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 18c5387d Table: 17ea404a DAC: 0015 Process cfgmgrd (pid: 998, stack limit = 0xd7c8a190) Stack: (0xd7c8ba90 to 0xd7c8c000) ba80: d7c8ba88 c08a6080 c09159c0 baa0: 000a 0091ccfe d9aac11c d7c8bac0 bf074c4c bf072de0 c08a2ae8 de32a000 bac0: 0c200319 b100 00e41eb0 bf074c4c 0002 bae0: 001eb000 bf074c4c d9aac000 0fcc d84510a8 0fa4 00200200 bb00: 00100100 00c4 d7c8bb80 c0259678 bf074c58 d7c8bb47 0001 bb20: d7c8bc38 d95f5958 d9aac11c 00c4 d9aac000 0fa4 d7c8bb80 db4aa480 bb40: d845100c c0259c98 d95f5958 d9aac000 0fa4 d9aac000 d85b3d80 d9be43f8 bb60: db4aa480 c0604dc8 c0124818 d95f5998 0019d7bf d9ad9400 c060b44c bb80: 00c4 c060b44c d95f5998 d95f5958 d9aac000 00028000 d8626700 d85b3d80 bba0: d95f5980 d9be43f8 d845100c c0605688 0019d7bf d9be43f8 d845100c bbc0: db4aa480 00029000 c00532a8 d9aac000 0003b000 c060b464 bbe0: 200b0013 c060b464 0003b000 c025fee4 d7c8bc20 bc00: d7c8bc1c 0001 d9aac0fc c094fe90 00100100 00200200 d9aac000 bc20: d9aac000 0019d7bf c02614ec 000c e41eb0b1 d9aac000 d9aac000 bc40: d9aac11c 0019d7bf d9aac04c d9be43f8 d845100c d95f5958 d9aac164 c025ed54 bc60: c0029350 000c 0001 0048 c025960c 0001 bc80: d8496040 0001 d9aac000 d9aac11c 0014 d9aac04c d7c8a000 bca0: 0013 d7c8bd24 c0259acc d8496040 001c 800b0013 c060b464 bcc0: d8496040 c002a158 d9aac000 800b0013 dab67208 dab67208 dab67208 bce0: c7b77954 d9aac2fc c0793f84 d9aac000 d9aac41c c0266228 0006 c060b5c0 bd00: c7b77940 c5f06c00 0007 c7b77954 d7c8bd7c d9aac0c0 d7c8bd74 bd20: cc59aba8 0fb8 d9575c98 d7c8bd74 cc59aba8 c0266aac cc59ab68 bd40: d9aac000 d9575c98 d96c4280 c0266b00 001e c02ca360 bd60: cc59aba8 c02c2f74 d7c8bd78 d7c8bd7c d9575c98 c0793f84 c5f06c00 001e bd80: d9aac000 cc59aba8 bda0: d85f07c0 d9aac000
PROBLEM: JFFS2 Empty summary info causes OOPS
Hi, [1.] Summary: JFFS2 Empty summary node info causes OOPS [2.] Description: Under stress situations on the filesystem, OOPs are observed. The OOPs points to empty summary node info bug. Confirmed that the filesystem is not full, not corrupted and is accessible. [3.] Keywords (i.e., modules, networking, kernel): filesystem [4.] Kernel information [4.1.] Kernel version (from /proc/version): 4.1.12 Driver version: jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [6.] Output of Oops.. Kernel BUG at c0268c78 [verbose debug info unavailable] Internal error: Oops - BUG: 0 [#1] SMP ARM Modules linked in: npcm750_rng dell_usbmuxdrv(O) g_edm_mass_storage3 vcd_dev(O) usb_storage sd_mod scsi_mod rng_core oprofile md4 g_edm_mass_storage2 des_generi c dell_regmem_adds(O) dell_pmdrv(O) dell_oom_notify(O) dell_msgbox(O) g_edm_mass _storage1 dell_fpdrv(O) dell_early_board(O) dell_ipmbdrv(O) dell_i2cdrv(O) dell_ cplddrv(O) g_edm_mass_storage cifs bonding g_edm_kbdmouse usb_f_ecm g_ether_usb arc4 aess_vkcsdrv(O) aess_smadrv(O) usb_f_rndis u_ether aess_pwmdrv(O) aess_pcim ailboxdrv(O) aess_mtddrv_spi_nor(O) aess_memdrv(O) libcomposite aess_fansensordr v(O) aess_dynairqdrv(O) aess_gpiodrv(O) aess_video(O) aess_biospostdrv(O) aess_k csdrv(O) aess_eventhandlerdrv(O) aess_adcsensordrv(O) CPU: 1 PID: 998 Comm: cfgmgrd Tainted: G O 4.1.12 Hardware name: NPCMX50 Chip family task: d7ccd340 ti: d7c8a000 task.ti: d7c8a000 PC is at jffs2_sum_write_sumnode+0x508/0x518 LR is at jffs2_sum_write_sumnode+0x508/0x518 pc : [] lr : [] psr: 600b0013 sp : d7c8ba90 ip : fp : d7c8bb80 r10: 00c4 r9 : d84510a8 r8 : 00200200 r7 : 0fa4 r6 : d84510a8 r5 : d9aac000 r4 : d98ca5c0 r3 : r2 : dcba772c r1 : dcba52dc r0 : 0044 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 18c5387d Table: 17ea404a DAC: 0015 Process cfgmgrd (pid: 998, stack limit = 0xd7c8a190) Stack: (0xd7c8ba90 to 0xd7c8c000) ba80: d7c8ba88 c08a6080 c09159c0 baa0: 000a 0091ccfe d9aac11c d7c8bac0 bf074c4c bf072de0 c08a2ae8 de32a000 bac0: 0c200319 b100 00e41eb0 bf074c4c 0002 bae0: 001eb000 bf074c4c d9aac000 0fcc d84510a8 0fa4 00200200 bb00: 00100100 00c4 d7c8bb80 c0259678 bf074c58 d7c8bb47 0001 bb20: d7c8bc38 d95f5958 d9aac11c 00c4 d9aac000 0fa4 d7c8bb80 db4aa480 bb40: d845100c c0259c98 d95f5958 d9aac000 0fa4 d9aac000 d85b3d80 d9be43f8 bb60: db4aa480 c0604dc8 c0124818 d95f5998 0019d7bf d9ad9400 c060b44c bb80: 00c4 c060b44c d95f5998 d95f5958 d9aac000 00028000 d8626700 d85b3d80 bba0: d95f5980 d9be43f8 d845100c c0605688 0019d7bf d9be43f8 d845100c bbc0: db4aa480 00029000 c00532a8 d9aac000 0003b000 c060b464 bbe0: 200b0013 c060b464 0003b000 c025fee4 d7c8bc20 bc00: d7c8bc1c 0001 d9aac0fc c094fe90 00100100 00200200 d9aac000 bc20: d9aac000 0019d7bf c02614ec 000c e41eb0b1 d9aac000 d9aac000 bc40: d9aac11c 0019d7bf d9aac04c d9be43f8 d845100c d95f5958 d9aac164 c025ed54 bc60: c0029350 000c 0001 0048 c025960c 0001 bc80: d8496040 0001 d9aac000 d9aac11c 0014 d9aac04c d7c8a000 bca0: 0013 d7c8bd24 c0259acc d8496040 001c 800b0013 c060b464 bcc0: d8496040 c002a158 d9aac000 800b0013 dab67208 dab67208 dab67208 bce0: c7b77954 d9aac2fc c0793f84 d9aac000 d9aac41c c0266228 0006 c060b5c0 bd00: c7b77940 c5f06c00 0007 c7b77954 d7c8bd7c d9aac0c0 d7c8bd74 bd20: cc59aba8 0fb8 d9575c98 d7c8bd74 cc59aba8 c0266aac cc59ab68 bd40: d9aac000 d9575c98 d96c4280 c0266b00 001e c02ca360 bd60: cc59aba8 c02c2f74 d7c8bd78 d7c8bd7c d9575c98 c0793f84 c5f06c00 001e bd80: d9aac000 cc59aba8 bda0: d85f07c0 d9aac000
Re: info on Oops
On Tue, 10 Oct 2000 23:40:49 -0500, "Jerry Kelley" <[EMAIL PROTECTED]> wrote: >Is there a good primer on reading an Oops? linux/Documentation/oops-tracing.txt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
info on Oops
Is there a good primer on reading an Oops? I'm also looking for general tips on configuring the kernel and my module so that a useful stack trace is generated - entry points show function names rather than addresses. The obvious is to build with debugging turned on but is it necessary for the kernel to be built with debugging turned on to effectively trace back through a crash? It seems that the Oops in the messages log resolves symbols but on the console I only get function addresses. Jerry Kelley [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
info on Oops
Is there a good primer on reading an Oops? I'm also looking for general tips on configuring the kernel and my module so that a useful stack trace is generated - entry points show function names rather than addresses. The obvious is to build with debugging turned on but is it necessary for the kernel to be built with debugging turned on to effectively trace back through a crash? It seems that the Oops in the messages log resolves symbols but on the console I only get function addresses. Jerry Kelley [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: info on Oops
On Tue, 10 Oct 2000 23:40:49 -0500, "Jerry Kelley" [EMAIL PROTECTED] wrote: Is there a good primer on reading an Oops? linux/Documentation/oops-tracing.txt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
