Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-16 Thread David Woodhouse
> 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 eithe

Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-16 Thread David Woodhouse
> 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 eithe

Re: Recall: PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-16 Thread Richard Weinberger
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

2018-06-16 Thread Richard Weinberger
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

2018-06-15 Thread Veluthakkal, Sreeram
Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty summary info causes OOPS".

Recall: PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-15 Thread Veluthakkal, Sreeram
Veluthakkal, Sreeram would like to recall the message, "PROBLEM: JFFS2 Empty summary info causes OOPS".

PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-15 Thread Veluthakkal, Sreeram
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

PROBLEM: JFFS2 Empty summary info causes OOPS

2018-06-15 Thread Veluthakkal, Sreeram
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

Re: info on Oops

2000-10-10 Thread Keith Owens
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

info on Oops

2000-10-10 Thread Jerry Kelley
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

info on Oops

2000-10-10 Thread Jerry Kelley
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

Re: info on Oops

2000-10-10 Thread Keith Owens
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