LKML Archive mirror
 help / color / mirror / Atom feed
* [OOPS] with 2.4.25 - same on several machines
@ 2004-03-02 22:36 Marek Habersack
  2004-03-03 10:21 ` Marcelo Tosatti
  0 siblings, 1 reply; 3+ messages in thread
From: Marek Habersack @ 2004-03-02 22:36 UTC (permalink / raw
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 3546 bytes --]

Hey all,

  The machines are the same hardware (PIII, 512MB RAM, IDE, ext3 on /, xfs
on the other partitions, 512MB of swap). Four machines oopsed with the same
oopses:

Mar  1 17:47:24 colo19 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008
Mar  1 17:47:24 colo19 kernel:  printing eip:
Mar  1 17:47:24 colo19 kernel: c01d0d6b
Mar  1 17:47:24 colo19 kernel: *pde = 00000000
Mar  1 17:47:24 colo19 kernel: Oops: 0000
Mar  1 17:47:24 colo19 kernel: CPU:    0
Mar  1 17:47:24 colo19 kernel: EIP:    0010:[fput+27/288]    Not tainted
Mar  1 17:47:24 colo19 kernel: EFLAGS: 00010292
Mar  1 17:47:24 colo19 kernel: eax: 57405660   ebx: 57405660   ecx: 00000079
edx: 57405660
Mar  1 17:47:24 colo19 kernel: esi: 00000000   edi: fffffff7   ebp: 00000000
esp: dc75ff7c
Mar  1 17:47:24 colo19 kernel: ds: 0018   es: 0018   ss: 0018
Mar  1 17:47:24 colo19 kernel: Process apache (pid: 2873, stackpage=dc75f000)
Mar  1 17:47:24 colo19 kernel: Stack: 00000018 00000018 dc75e000 57405660 fffffff7 000000b2 c01d0077 d9e6b0c0 
Mar  1 17:47:24 colo19 kernel:        080ed9c4 00000296 00000000 c01b187b dc75ffb0 dc75e000 00000013 081dec1e 
Mar  1 17:47:24 colo19 kernel:        bffffc18 c01a04d3 00000079 081deb6c 000000b2 00000013 081dec1e bffffc18 
Mar  1 17:47:24 colo19 kernel: Call Trace:    [sys_write+247/320] [sys_time+27/96] [system_call+51/64] [handle_signal+315/
336]
Mar  1 17:47:24 colo19 kernel: 
Mar  1 17:47:24 colo19 kernel: Code: 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 18 8b 5c 24 08 8b 74 24 

followed by

Mar  1 17:47:24 colo19 kernel:  <1>Unable to handle kernel paging request at virtual address 000051b3
Mar  1 17:47:24 colo19 kernel:  printing eip:
Mar  1 17:47:24 colo19 kernel: c01cf497
Mar  1 17:47:24 colo19 kernel: *pde = 00000000
Mar  1 17:47:24 colo19 kernel: Oops: 0000
Mar  1 17:47:24 colo19 kernel: CPU:    0
Mar  1 17:47:24 colo19 kernel: EIP:    0010:[filp_close+23/128]    Not tainted
Mar  1 17:47:24 colo19 kernel: EFLAGS: 00010286
Mar  1 17:47:24 colo19 kernel: eax: dd3bb000   ebx: 0000519f   ecx: 00000000 edx: 0000519f
Mar  1 17:47:24 colo19 kernel: esi: dd3fc8a0   edi: dd3fc8a0   ebp: 00000004 esp: dc75fe28
Mar  1 17:47:24 colo19 kernel: ds: 0018   es: 0018   ss: 0018
Mar  1 17:47:24 colo19 kernel: Process apache (pid: 2873, stackpage=dc75f000)
Mar  1 17:47:24 colo19 kernel: Stack: dc859660 dd3fc8a0 000000ff 00000078 dd3fc8a0 c01b0284 0000519f dd3fc8a0 
Mar  1 17:47:24 colo19 kernel:        c1706ee0 dc76a5a0 dc75e000 0000000b c01b0977 dd3fc8a0 0000000b dc75ff48 
Mar  1 17:47:24 colo19 kernel:        dc76a5a0 c1706efc 00000008 c01a0bc3 0000000b c03d25e5 00000000 00000000 
Mar  1 17:47:24 colo19 kernel: Call Trace:    [put_files_struct+100/208] [do_exit+183/640] [die+115/128] [do_page_fault+861/1454] [do_page_fault+552/1454]
Mar  1 17:47:24 colo19 kernel:   [inet_sendmsg+66/80] [sock_sendmsg+116/176] [do_page_fault+0/1454] [error_code+52/64] [fput+27/288] [sys_write+247/320]
Mar  1 17:47:24 colo19 kernel:   [sys_time+27/96] [system_call+51/64] [handle_signal+315/336]
Mar  1 17:47:24 colo19 kernel: 
Mar  1 17:47:24 colo19 kernel: Code: 8b 43 14 85 c0 74 52 8b 43 10 31 ff 85 c0 74 07 8b 50 24 85 

The processes in all cases were different (a shell script, lsof, apache).
The kernels are patched with grsec2 and libsata, but it doesn't seem to be
relevant in this case. Could anybody shed some light on it? If necessary, I
will post the machine configs and all the information needed to diagnose.

tia,

marek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [OOPS] with 2.4.25 - same on several machines
  2004-03-02 22:36 [OOPS] with 2.4.25 - same on several machines Marek Habersack
@ 2004-03-03 10:21 ` Marcelo Tosatti
  2004-03-03 12:42   ` Marek Habersack
  0 siblings, 1 reply; 3+ messages in thread
From: Marcelo Tosatti @ 2004-03-03 10:21 UTC (permalink / raw
  To: Marek Habersack; +Cc: linux-kernel



On Tue, 2 Mar 2004, Marek Habersack wrote:

> Hey all,
> 
>   The machines are the same hardware (PIII, 512MB RAM, IDE, ext3 on /, xfs
> on the other partitions, 512MB of swap). Four machines oopsed with the same
> oopses:
> 
> Mar  1 17:47:24 colo19 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008
> Mar  1 17:47:24 colo19 kernel:  printing eip:
> Mar  1 17:47:24 colo19 kernel: c01d0d6b
> Mar  1 17:47:24 colo19 kernel: *pde = 00000000
> Mar  1 17:47:24 colo19 kernel: Oops: 0000
> Mar  1 17:47:24 colo19 kernel: CPU:    0
> Mar  1 17:47:24 colo19 kernel: EIP:    0010:[fput+27/288]    Not tainted
> Mar  1 17:47:24 colo19 kernel: EFLAGS: 00010292
> Mar  1 17:47:24 colo19 kernel: eax: 57405660   ebx: 57405660   ecx: 00000079
> edx: 57405660
> Mar  1 17:47:24 colo19 kernel: esi: 00000000   edi: fffffff7   ebp: 00000000
> esp: dc75ff7c
> Mar  1 17:47:24 colo19 kernel: ds: 0018   es: 0018   ss: 0018
> Mar  1 17:47:24 colo19 kernel: Process apache (pid: 2873, stackpage=dc75f000)
> Mar  1 17:47:24 colo19 kernel: Stack: 00000018 00000018 dc75e000 57405660 fffffff7 000000b2 c01d0077 d9e6b0c0 
> Mar  1 17:47:24 colo19 kernel:        080ed9c4 00000296 00000000 c01b187b dc75ffb0 dc75e000 00000013 081dec1e 
> Mar  1 17:47:24 colo19 kernel:        bffffc18 c01a04d3 00000079 081deb6c 000000b2 00000013 081dec1e bffffc18 
> Mar  1 17:47:24 colo19 kernel: Call Trace:    [sys_write+247/320] [sys_time+27/96] [system_call+51/64] [handle_signal+315/
> 336]
> Mar  1 17:47:24 colo19 kernel: 
> Mar  1 17:47:24 colo19 kernel: Code: 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 18 8b 5c 24 08 8b 74 24 
> 
> The processes in all cases were different (a shell script, lsof, apache).
> The kernels are patched with grsec2 and libsata, but it doesn't seem to be
> relevant in this case. Could anybody shed some light on it? If necessary, I
> will post the machine configs and all the information needed to diagnose.

Hi Marek, 

<standard reply>

Can you reproduce the problem on vanilla 2.4.25 ? 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [OOPS] with 2.4.25 - same on several machines
  2004-03-03 10:21 ` Marcelo Tosatti
@ 2004-03-03 12:42   ` Marek Habersack
  0 siblings, 0 replies; 3+ messages in thread
From: Marek Habersack @ 2004-03-03 12:42 UTC (permalink / raw
  To: Marcelo Tosatti; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Wed, Mar 03, 2004 at 07:21:23AM -0300, Marcelo Tosatti scribbled:
[snip]
> > Mar  1 17:47:24 colo19 kernel: 
> > Mar  1 17:47:24 colo19 kernel: Code: 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 18 8b 5c 24 08 8b 74 24 
> > 
> > The processes in all cases were different (a shell script, lsof, apache).
> > The kernels are patched with grsec2 and libsata, but it doesn't seem to be
> > relevant in this case. Could anybody shed some light on it? If necessary, I
> > will post the machine configs and all the information needed to diagnose.
> 
> Hi Marek, 
> 
> <standard reply>
> 
> Can you reproduce the problem on vanilla 2.4.25 ? 
I'll try, it will probably take a while, at least till the weekend. The only
common pattern between the machines was the uptime - slightly above 36h. I
will be able to install 2.4.25 vanilla tomorrow, so I suppose Sunday at the
latest I will have some results.

thanks

marek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-03-03 12:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-02 22:36 [OOPS] with 2.4.25 - same on several machines Marek Habersack
2004-03-03 10:21 ` Marcelo Tosatti
2004-03-03 12:42   ` Marek Habersack

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).