Dear people,
Yesterday night, I was running my own self compiled kernel 2.6.9-rc2,
without any patches applied and, while I had my computer left unattended
for some moments, I saw that it generated two Oopsen in a row.
BTW, I was excited to use 2.6.9-rc2 because it included the 8 byte-fix for
USB urb's, which is needed for my desktop to cooperate with my USB Drive.
I'm attaching the decoded Oops through ksymoops. I'm using a Debian testing
machine with a Duron 600MHz processor, an Asus A7V motherboard and 386MB of
memory. The kernel is not tainted. I used GCC 3.3.4 to compile the kernel;
gcc --version says: gcc (GCC) 3.3.4 (Debian 1:3.3.4-6sarge1).
Since the decoded Oops mentioned things related to filesystems, I became
scared, with fear of data corruption.
Please let me know if any further details are necessary about the
situation.
Thanks, Rog?rio Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rog?rio Brito - [email protected] - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rog?rio Brito <[email protected]> wrote:
>
> Yesterday night, I was running my own self compiled kernel 2.6.9-rc2,
> without any patches applied and, while I had my computer left unattended
> for some moments, I saw that it generated two Oopsen in a row.
Were you using a cdrom at that time? If so, this will probably fix it:
--- 25/fs/isofs/rock.c~rock-fix 2004-09-10 01:47:00.135392480 -0700
+++ 25-akpm/fs/isofs/rock.c 2004-09-10 01:47:00.139391872 -0700
@@ -62,7 +62,7 @@
}
#define MAYBE_CONTINUE(LABEL,DEV) \
- {if (buffer) kfree(buffer); \
+ {if (buffer) { kfree(buffer); buffer = NULL; } \
if (cont_extent){ \
int block, offset, offset1; \
struct buffer_head * pbh; \
_
On 15 de set de 2004, at 20:21, Andrew Morton wrote:
> Rog?rio Brito <[email protected]> wrote:
>>
>> Yesterday night, I was running my own self compiled kernel 2.6.9-rc2,
>> without any patches applied and, while I had my computer left
>> unattended
>> for some moments, I saw that it generated two Oopsen in a row.
>
> Were you using a cdrom at that time? If so, this will probably fix
> it:
Yes, I think that I was. Today I got another amount of Oopsen. I will
try the patch right now and report back my results.
Thank you very much, Rog?rio Brito.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rog?rio Brito - [email protected] - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Thursday 16 Sep 2004 11:51, Rog?rio Brito wrote:
> On 15 de set de 2004, at 20:21, Andrew Morton wrote:
> > Were you using a cdrom at that time? If so, this will probably fix
> > it:
>
> Yes, I think that I was. Today I got another amount of Oopsen. I will
> try the patch right now and report back my results.
I've been using 2.6.9-rc2 with the patch and it's working well - no oops with
cdrom use now.
tim
On Sep 16 2004, Tim Fairchild wrote:
> On Thursday 16 Sep 2004 11:51, Rog?rio Brito wrote:
> > Yes, I think that I was. Today I got another amount of Oopsen. I will
> > try the patch right now and report back my results.
>
> I've been using 2.6.9-rc2 with the patch and it's working well - no oops with
> cdrom use now.
Just as a feedback that I promised, it's working correctly now with the
patch applied. It seems that the problem was indeed caused by accessing
CDs.
Thanks, Rog?rio.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rog?rio Brito - [email protected] - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=