Re: Kernel BUG at page_alloc.c:117!

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

Hello Dirk,
 
 First, thank you for responding so fast.
 I have to use the kernel 2.4.18 (or at best the
2.4.22). 
 I want first understand what's appened; Is-it a
kernel
 problem or is-it a bug off our application which is
written in C++.
 It seems like there a bug with the VM; is it true?
And
 what is exactly the problem? Is it a hardware
problem?(Need I to add RAM or change Hard dirve?)
 
 Zine.
 
> 
> --- Dirk Henning Gerdes <mail@dirk-gerdes.de> a
> écrit
> :
> 
> > Hello Zine,
> > 
> > your kernel is quite old.
> > Probably it would just help to update to a newer
> > one.
> > I think on 2.4 the 2.4.32 is the current version.
> > 
> > Dirk
> > 
> > Am Montag, den 05.12.2005, 14:16 +0100 schrieb
> zine
> > el abidine Hamid:
> > > Hi,
> > > 
> > > 
> > > I'm using a Linux RedHat kernel 2.4.18-3 and the
> > > system hung after a while with this error
> > > (/var/log/messages):

Dec  1 14:54:58 Republique_ncl_a kernel: ------------[
cut here ]------------
Dec  1 14:54:58 Republique_ncl_a kernel: kernel BUG at
page_alloc.c:117!
Dec  1 14:54:58 Republique_ncl_a kernel: invalid
operand: 0000
Dec  1 14:54:58 Republique_ncl_a kernel: wdpiano
w83781d via686a lm80 i2c-proc i2c-isa i2c-core auto
fs parport_pc plip
Dec  1 14:54:58 Republique_ncl_a kernel: CPU:    0
Dec  1 14:54:58 Republique_ncl_a kernel: EIP:   
0010:[<c01316e7>]    Not tainted
Dec  1 14:54:58 Republique_ncl_a kernel: EFLAGS:
00010282
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel: EIP is at
__free_pages_ok [kernel] 0x57 (2.4.18-3)
Dec  1 14:54:58 Republique_ncl_a kernel: eax: 00000020
  ebx: c16502d8   ecx: 00000001   edx: 000019
0e
Dec  1 14:54:58 Republique_ncl_a kernel: esi: 00000000
  edi: 000001d0   ebp: 00000000   esp: c1755f
38
Dec  1 14:54:58 Republique_ncl_a kernel: ds: 0018  
es: 0018   ss: 0018
Dec  1 14:54:58 Republique_ncl_a kernel: Process
kswapd (pid: 5, stackpage=c1755000)
Dec  1 14:54:58 Republique_ncl_a kernel: Stack:
c02250b5 00000075 c013d0e3 ddf7e600 c16502d8 000001d
0 c013b23a c16502d8
Dec  1 14:54:58 Republique_ncl_a kernel:       
c16502f4 c16502d8 c16502d8 000001d0 000001d0 c012ff8
b 00000c24 0000019d
Dec  1 14:54:58 Republique_ncl_a kernel:       
00000125 c02c473c 00000c24 00000848 0000000f c013038
8 c02c473c 000001d0
Dec  1 14:54:58 Republique_ncl_a kernel: Call Trace:
[<c013d0e3>] try_to_free_buffers [kernel] 0xb3
Dec  1 14:54:58 Republique_ncl_a kernel: [<c013b23a>]
try_to_release_page [kernel] 0x3a
Dec  1 14:54:58 Republique_ncl_a kernel: [<c012ff8b>]
page_launder_zone [kernel] 0x42b
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130388>]
page_launder [kernel] 0x168
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130c12>]
do_try_to_free_pages [kernel] 0x12
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130f11>]
kswapd [kernel] 0x101
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0105000>]
stext [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0107136>]
kernel_thread [kernel] 0x26
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130e10>]
kswapd [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel: Code: 0f 0b
5d 58 8b 3d f0 e2 32 c0 89 d8 29 f8 69 c0 b7 6d
 db b6
Dec  1 14:54:59 Republique_ncl_a ucd-snmp[12873]:
Connection from 111.9.3.13
Dec  1 14:55:30 Republique_ncl_a last message repeated
9 times
Dec  1 14:56:31 Republique_ncl_a last message repeated
17 times

> > > 
> > > 
> > > 
> > > Can anyone explain me what does it mean? What
> the
> > > problem?   How can I resolve this problem?
> > > 
> > > Thanks.
> > > 
> > > Zine. 
> > > 
> > > 
> > > 	
> > > 
> > > 	
> > > 		
> > >
> >
>
___________________________________________________________________________
> > 
> > > Appel audio GRATUIT partout dans le monde avec
> le
> > nouveau Yahoo! Messenger 
> > > Téléchargez cette version sur
> > http://fr.messenger.yahoo.com
> > > -
> > > To unsubscribe from this list: send the line
> > "unsubscribe linux-kernel" in
> > > the body of a message to
> majordomo@vger.kernel.org
> > > More majordomo info at 
> > http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at  http://www.tux.org/lkml/
> > > 
> > -- 
> > Dirk Henning Gerdes
> > Bönnersdyk 47
> > 47803 Krefeld
> > 
> > Tel:  02151-755745
> >       0174-7776640
> > Mail: mail@dirk-gerdes.de
> > 
> > -
> > To unsubscribe from this list: send the line
> > "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at 
> > http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 
> 
> 
> 	
> 	
> 		
>
___________________________________________________________________________
> Appel audio GRATUIT partout dans le monde avec le
> nouveau Yahoo! Messenger 
> Téléchargez cette version sur
> http://fr.messenger.yahoo.com
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Arjan van de Ven]

On Mon, 2005-12-05 at 14:57 +0100, zine el abidine Hamid wrote:
> Hello Dirk,
>  
>  First, thank you for responding so fast.
>  I have to use the kernel 2.4.18 (or at best the
> 2.4.22). 

why?

>  I want first understand what's appened; 

something in the kernel did something wrong, which caused the VM to
notice the corruption

> Is-it a
> kernel
>  problem or is-it a bug off our application which is
> written in C++.

it's probably a driver bug (at least that's most common)
>  It seems like there a bug with the VM; is it true?

no it's something that went wrong and first got noticed in the VM,
that's different from being a bug in the VM.


which exactly modules were in use? Are there any modules that didn't
come with that kernel? 

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

I have to use the 2.4.18 kernel because We use an
application which is build on this kernel.
The module are the next one (lsmod):

Module                  Size  Used by    Not tainted
wdpiano                 1920   0  (unused)
w83781d                18592   0  (unused)
via686a                 9924   0 
lm80                    6624   0  (unused)
i2c-proc                8160   0  [w83781d via686a
lm80]
i2c-isa                 1892   0  (unused)
i2c-core               18720   0  [w83781d via686a
lm80 i2c-proc i2c-isa]
autofs                 12164   0  (autoclean) (unused)
parport_pc             18756   1  (autoclean)
plip                   12744   1  (autoclean)
parport                34208   1  (autoclean)
[parport_pc plip]
eepro100               20336   1 
ext3                   67136   2 
jbd                    49400   2  [ext3]



The kernel is (uname) :
Linux Republique_ncl_a 2.4.18-3 #1 Thu Apr 18 07:37:53
EDT 2002 i686 unknown


Zine.

--- Arjan van de Ven <arjan@infradead.org> a écrit :

> On Mon, 2005-12-05 at 14:57 +0100, zine el abidine
> Hamid wrote:
> > Hello Dirk,
> >  
> >  First, thank you for responding so fast.
> >  I have to use the kernel 2.4.18 (or at best the
> > 2.4.22). 
> 
> why?
> 
> >  I want first understand what's appened; 
> 
> something in the kernel did something wrong, which
> caused the VM to
> notice the corruption
> 
> > Is-it a
> > kernel
> >  problem or is-it a bug off our application which
> is
> > written in C++.
> 
> it's probably a driver bug (at least that's most
> common)
> >  It seems like there a bug with the VM; is it
> true?
> 
> no it's something that went wrong and first got
> noticed in the VM,
> that's different from being a bug in the VM.
> 
> 
> which exactly modules were in use? Are there any
> modules that didn't
> come with that kernel? 
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Arjan van de Ven]

On Mon, 2005-12-05 at 15:25 +0100, zine el abidine Hamid wrote:
> 
> I have to use the 2.4.18 kernel because We use an
> application which is build on this kernel.

the good news is that userspace applications are not kernel version
specific! At least in general; there are some low level system tools
that sometimes are impacted (these are usually the "kernel helpers" like
the insmod tool or udev). Regular applications work on just about any
kernel; applications written for linux in 1994 still work on 2.6
kernels!

> The module are the next one (lsmod):
> 
> Module                  Size  Used by    Not tainted
> wdpiano                 1920   0  (unused)

what is this?

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

Indeed, I tested the application with a 2.4.22 kernel
and it seems to work; but I'm not the author of this
application.

The module "wdpiano" is C programme which allow us to
use the Watch-Dog Timer of the mother board (ROCKY
3703EVR).


Zine

PS : The user's manual definition of The Watch-Dog
Timer is : "a device to ensure thet standalone systems
can always recover from abnormal conditions that cause
the system to crash. These conditions may result from
an external EMI or software bug."

--- Arjan van de Ven <arjan@infradead.org> a écrit :

> On Mon, 2005-12-05 at 15:25 +0100, zine el abidine
> Hamid wrote:
> > 
> > I have to use the 2.4.18 kernel because We use an
> > application which is build on this kernel.
> 
> the good news is that userspace applications are not
> kernel version
> specific! At least in general; there are some low
> level system tools
> that sometimes are impacted (these are usually the
> "kernel helpers" like
> the insmod tool or udev). Regular applications work
> on just about any
> kernel; applications written for linux in 1994 still
> work on 2.6
> kernels!
> 
> > The module are the next one (lsmod):
> > 
> > Module                  Size  Used by    Not
> tainted
> > wdpiano                 1920   0  (unused)
> 
> what is this?
> 
> 
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

I don't know if it's helpfull but the output of
ksymoops is :

ksymoops 2.4.4 on i686 2.4.18-3.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.18-3/ (default)
     -m /boot/System.map-2.4.18-3 (default)

Warning: You did not tell me where to find symbol
information.  I will
assume that the log matches the kernel and modules
that are running
right now and I'll use the default options above for
symbol resolution.
If the current kernel and/or modules do not match the
log, you can get
more accurate output by telling me the kernel version
and where to find
map, modules, ksyms etc.  ksymoops -h explains the
options.

Error (expand_objects): cannot stat(/lib/ext3.o) for
ext3
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/jbd.o) for
jbd

....


Warning (compare_maps): parport symbol
parport_unregister_port not found in
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
 Ignoring
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
entry
Warning (compare_maps): parport symbol
parport_wait_event not found in
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
 Ignoring
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
entry
Warning (compare_maps): parport symbol
parport_wait_peripheral not found in
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
 Ignoring
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
entry
Warning (compare_maps): parport symbol parport_write
not found in
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
 Ignoring
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
entry
Warning (map_ksym_to_module): cannot match loaded
module ext3 to a unique module object.  Trace may not
be reliable.
Warning (map_ksym_to_module): cannot match loaded
module jbd to a unique module object.  Trace may not
be reliable.
Dec  1 14:54:58 Republique_ncl_a kernel: kernel BUG at
page_alloc.c:117!
Dec  1 14:54:58 Republique_ncl_a kernel: invalid
operand: 0000
Dec  1 14:54:58 Republique_ncl_a kernel: CPU:    0
Dec  1 14:54:58 Republique_ncl_a kernel: EIP:   
0010:[<c01316e7>]    Not tainted

Using defaults from ksymoops -t elf32-i386 -a i386
Dec  1 14:54:58 Republique_ncl_a kernel: EFLAGS:
00010282
Dec  1 14:54:58 Republique_ncl_a kernel: eax: 00000020
  ebx: c16502d8   ecx: 00000001   edx: 000019
Dec  1 14:54:58 Republique_ncl_a kernel: esi: 00000000
  edi: 000001d0   ebp: 00000000   esp: c1755f
Dec  1 14:54:58 Republique_ncl_a kernel: ds: 0018  
es: 0018   ss: 0018
Dec  1 14:54:58 Republique_ncl_a kernel: Process
kswapd (pid: 5, stackpage=c1755000)
Dec  1 14:54:58 Republique_ncl_a kernel: Stack:
c02250b5 00000075 c013d0e3 ddf7e600 c16502d8 000001d
Dec  1 14:54:58 Republique_ncl_a kernel:       
c16502f4 c16502d8 c16502d8 000001d0 000001d0 c012ff8
Dec  1 14:54:58 Republique_ncl_a kernel:       
00000125 c02c473c 00000c24 00000848 0000000f c013038
Dec  1 14:54:58 Republique_ncl_a kernel: Call Trace:
[<c013d0e3>] try_to_free_buffers [kernel] 0xb3
Dec  1 14:54:58 Republique_ncl_a kernel: [<c013b23a>]
try_to_release_page [kernel] 0x3a
Dec  1 14:54:58 Republique_ncl_a kernel: [<c012ff8b>]
page_launder_zone [kernel] 0x42b
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130388>]
page_launder [kernel] 0x168
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130c12>]
do_try_to_free_pages [kernel] 0x12
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130f11>]
kswapd [kernel] 0x101
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0105000>]
stext [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0107136>]
kernel_thread [kernel] 0x26
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130e10>]
kswapd [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel: Code: 0f 0b
5d 58 8b 3d f0 e2 32 c0 89 d8 29 f8 69 c0 b7 6d
sh: /usr/bin/objdump: Aucun fichier ou répertoire de
ce type
Error (pclose_local): Oops_decode pclose failed 0x7f00
Error (Oops_decode): no objdump lines read for
/tmp/ksymoops.QPZFYU

>>EIP; c01316e7 <__free_pages_ok+57/310>   <=====
Trace; c013d0e3 <try_to_free_buffers+b3/110>
Trace; c013b23a <try_to_release_page+3a/60>
Trace; c012ff8b <page_launder_zone+42b/6c0>
Trace; c0130388 <page_launder+168/300>
Trace; c0130c12 <do_try_to_free_pages+12/180>
Trace; c0130f11 <kswapd+101/2d0>
Trace; c0105000 <_stext+0/0>
Trace; c0107136 <kernel_thread+26/30>
Trace; c0130e10 <kswapd+0/2d0>


977 warnings and 869 errors issued.  Results may not
be reliable.




Tank's for your help.

Zine

--- zine el abidine Hamid <zine46@yahoo.fr> a écrit :

> Indeed, I tested the application with a 2.4.22
> kernel
> and it seems to work; but I'm not the author of this
> application.
> 
> The module "wdpiano" is C programme which allow us
> to
> use the Watch-Dog Timer of the mother board (ROCKY
> 3703EVR).
> 
> 
> Zine
> 
> PS : The user's manual definition of The Watch-Dog
> Timer is : "a device to ensure thet standalone
> systems
> can always recover from abnormal conditions that
> cause
> the system to crash. These conditions may result
> from
> an external EMI or software bug."
> 
> --- Arjan van de Ven <arjan@infradead.org> a écrit :
> 
> > On Mon, 2005-12-05 at 15:25 +0100, zine el abidine
> > Hamid wrote:
> > > 
> > > I have to use the 2.4.18 kernel because We use
> an
> > > application which is build on this kernel.
> > 
> > the good news is that userspace applications are
> not
> > kernel version
> > specific! At least in general; there are some low
> > level system tools
> > that sometimes are impacted (these are usually the
> > "kernel helpers" like
> > the insmod tool or udev). Regular applications
> work
> > on just about any
> > kernel; applications written for linux in 1994
> still
> > work on 2.6
> > kernels!
> > 
> > > The module are the next one (lsmod):
> > > 
> > > Module                  Size  Used by    Not
> > tainted
> > > wdpiano                 1920   0  (unused)
> > 
> > what is this?
> > 
> > 
> > 
> > -
> > To unsubscribe from this list: send the line
> > "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at 
> > http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 
> 
> 
> 	
> 
> 	
> 		
>
___________________________________________________________________________
> 
> Appel audio GRATUIT partout dans le monde avec le
> nouveau Yahoo! Messenger 
> Téléchargez cette version sur
> http://fr.messenger.yahoo.com
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Rob Landley]

On Monday 05 December 2005 09:05, zine el abidine Hamid wrote:

> PS : The user's manual definition of The Watch-Dog
> Timer is : "a device to ensure thet standalone systems
> can always recover from abnormal conditions that cause
> the system to crash. These conditions may result from
> an external EMI or software bug."

Such as the power supply filling up with dust and catching fire.

Rather an optimistic user's manual, really...

Rob
-- 
Steve Ballmer: Innovation!  Inigo Montoya: You keep using that word.
I do not think it means what you think it means.

Re: Kernel BUG at page_alloc.c:117!

[Keith Mannthey]

You might want to file a bug with the distro you are running. The
kernel numbering seems to be RedHat?  Perhaps they have seen and fixed
the problem already upsteam in their tree somewhere.

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

Indeed, It's a RedHat station. But I want first to
know if it's a kernel bug or not.
Perhaps the informations (logs, modules, ksymoops ) I
gived you are not sufficient.
I want to understand what's happen because the problem
is not reproductible.
 
Is it due to a module that I load? (I think to the
module "wdpiano"...?)
Is it a hardware problem...? (such as RAM, or I/O
error )
How can I determine the origine of the problem?

The sar base (I can send the file if you need it)
don't help me a lot... (all seems to be ok)

Thanks for your help.

Zine

PS : I don't know if you have already received this
mail; that's why I send it again without the attached
file... excuses me for the noise..

--- Keith Mannthey <kmannth@gmail.com> a écrit :

> You might want to file a bug with the distro you are
> running. The
> kernel numbering seems to be RedHat?  Perhaps they
> have seen and fixed
> the problem already upsteam in their tree somewhere.
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Nix]

On 6 Dec 2005, Rob Landley whispered secretively:
> On Monday 05 December 2005 09:05, zine el abidine Hamid wrote:
> 
>> PS : The user's manual definition of The Watch-Dog
>> Timer is : "a device to ensure thet standalone systems
>> can always recover from abnormal conditions that cause
>> the system to crash. These conditions may result from
>> an external EMI or software bug."
> 
> Such as the power supply filling up with dust and catching fire.
> 
> Rather an optimistic user's manual, really...

The Algol-68 people considered this problem long ago:
<http://gcc.gnu.org/ml/gcc-help/2004-11/msg00107.html>.

-- 
`Don't confuse the shark with the remoras.' --- Rob Landley

Re: Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

Hello,


I come back to you. The code of the module wdpiano is
the next one :


#include <linux/config.h>
#include <linux/module.h>
#include <linux/version.h>
#include <linux/types.h>
#include <linux/errno.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/miscdevice.h>
#include <linux/watchdog.h>
#include <linux/slab.h>
#include <linux/ioport.h>
#include <linux/fcntl.h>
#include <asm/io.h>
#include <asm/uaccess.h>
#include <asm/system.h>
#include <linux/notifier.h>
#include <linux/reboot.h>
#include <linux/init.h>


#define WDIO 0x443
#define WDIODIS 0x43
static int wdpiano_is_open=0; // le fichier driver
n'est pas ouvert
static unsigned char tempo=10; //temporisation de 10
second par défaut

MODULE_PARM(tempo, "b");
MODULE_PARM_DESC(tempo, "time-out period from 1s to
255s (default 10s)");
MODULE_AUTHOR("Massinissa AGOUDJIL RATP(R)
<massinissa.agoudjil@ratp.fr>");
MODULE_LICENSE("GPL");

static int wdpiano_open(struct inode *inode, struct
file *file) {
   if (MINOR(inode->i_rdev)!=WATCHDOG_MINOR) return
-ENODEV;
   // access exclusive au fichier de driver
   if (wdpiano_is_open) return -EBUSY;
   // Comptage du nombre de chargement
   MOD_INC_USE_COUNT;
   //Initialise le timeout
   outb_p(tempo,WDIO);
    printk("<1>wdpiano: initialised with a time-out of
%ds\n",tempo);
   // limiter l'ouverture 
   wdpiano_is_open=1;
   return 0;
}

static int wdpiano_release(struct inode *inode, struct
file *file) {
   if (MINOR(inode->i_rdev)==WATCHDOG_MINOR) {
#ifndef CONFIG_WATCHDOG_NOWAYOUT
      //désactiver le watchdog à la fermeture
      inb_p(WDIO);
      inb_p(WDIODIS);
#endif
      wdpiano_is_open=0;
   }
   MOD_DEC_USE_COUNT;
   return 0;
}

static ssize_t wdpiano_write(struct file *file, const
char *buf, size_t count, loff_t *ppos) {
   if (ppos!=&file->f_pos)
     return -ESPIPE;
   if (count) {
      //reinitialiser le timer du watchdog
      inb_p(WDIODIS);
      inb_p(WDIO);
      return 1;
   }
   return 0;
}
//Un petit message!
static int wdpiano_notify_sys(struct notifier_block
*this, unsigned long code,
	void *unused) {
	if(code==SYS_DOWN || code==SYS_HALT) {
	    //désactiver le watchdog à la fermeture
      	    inb_p(WDIO);
      	    inb_p(WDIODIS);
	}
	return NOTIFY_DONE;
}


static struct file_operations wdpiano_fops = {
  owner:          THIS_MODULE,
// read:           wdpiano_read,
   write:          wdpiano_write,
   open:           wdpiano_open,
   release:        wdpiano_release,
};

static struct miscdevice wdpiano_dev = {
   WATCHDOG_MINOR, //fixer le mineur voir miscdevice.h
et devices.txt
     "watchdog",   //fixer le nom de fichier d'accee 
     &wdpiano_fops
};



static struct notifier_block wdpiano_notifier = {
   wdpiano_notify_sys,
     NULL,
     0
};

int init_module(void)
{
 int retval;

 printk("Piano watchdog driver RATP(r) V1.0\n");

 wdpiano_dev.fops = &wdpiano_fops;
 // Allocation des ressources
 register_reboot_notifier(&wdpiano_notifier);
 // Enregistrement du module
 retval = misc_register(&wdpiano_dev);
/* if (retval)
         return retval;*/
 return 0;
}



void cleanup_module(void)
{
 printk("<1>wdpiano: cleanup_module\n");

 // Suppression du module
 misc_deregister(&wdpiano_dev);
 //liberation des ressources 
 unregister_reboot_notifier(&wdpiano_notifier);
}



Thank's for your help.

Zine



--- Dirk Henning Gerdes <mail@dirk-gerdes.de> a écrit
:

> Hi Zine!
> 
> That is not the point. But I suppose that the module
> which runs under
> 2.4.18 won't run under Linux 2.6. Or quite even
> under 2.4.32.
> That could cause some problems, either.
> If the vendor would give you a new version
> compatible to 2.6, you could
> update your whole kernel.
> 
> 
> Am Dienstag, den 06.12.2005, 11:35 +0100 schrieb
> zine el abidine Hamid:
> > Why? Do you think that the problem is the module
> > wdpiano?
> > 
> > It's a small program which modify the Watch-Dog
> Timer
> > value only...
> > 
> > --- Dirk Henning Gerdes <mail@dirk-gerdes.de> a
> écrit
> > :
> > 
> > > Probably you can contact the manufactor of the
> board
> > > to get a driver for
> > > the watchdog, which runs under newer
> Linux-versions,
> > > if you really need
> > > the watchdog
> > > Am Montag, den 05.12.2005, 17:48 +0100 schrieb
> zine
> > > el abidine Hamid:
> > > > 
> > > > I don't know if it's helpfull but the output
> of
> > > > ksymoops is :
> > > > 
> > > > ksymoops 2.4.4 on i686 2.4.18-3.  Options used
> > > >      -V (default)
> > > >      -k /proc/ksyms (default)
> > > >      -l /proc/modules (default)
> > > >      -o /lib/modules/2.4.18-3/ (default)
> > > >      -m /boot/System.map-2.4.18-3 (default)
> > > > 
> > > > Warning: You did not tell me where to find
> symbol
> > > > information.  I will
> > > > assume that the log matches the kernel and
> modules
> > > > that are running
> > > > right now and I'll use the default options
> above
> > > for
> > > > symbol resolution.
> > > > If the current kernel and/or modules do not
> match
> > > the
> > > > log, you can get
> > > > more accurate output by telling me the kernel
> > > version
> > > > and where to find
> > > > map, modules, ksyms etc.  ksymoops -h explains
> the
> > > > options.
> > > > 
> > > > Error (expand_objects): cannot
> stat(/lib/ext3.o)
> > > for
> > > > ext3
> > > > ksymoops: No such file or directory
> > > > Error (expand_objects): cannot
> stat(/lib/jbd.o)
> > > for
> > > > jbd
> > > > 
> > > > ....
> > > > 
> > > > 
> > > > Warning (compare_maps): parport symbol
> > > > parport_unregister_port not found in
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > >  Ignoring
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > entry
> > > > Warning (compare_maps): parport symbol
> > > > parport_wait_event not found in
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > >  Ignoring
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > entry
> > > > Warning (compare_maps): parport symbol
> > > > parport_wait_peripheral not found in
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > >  Ignoring
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > entry
> > > > Warning (compare_maps): parport symbol
> > > parport_write
> > > > not found in
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > >  Ignoring
> > > >
> > >
> >
>
/lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > entry
> > > > Warning (map_ksym_to_module): cannot match
> loaded
> > > > module ext3 to a unique module object.  Trace
> may
> > > not
> > > > be reliable.
> > > > Warning (map_ksym_to_module): cannot match
> loaded
> > > > module jbd to a unique module object.  Trace
> may
> > > not
> > > > be reliable.
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> kernel
> > > BUG at
> > > > page_alloc.c:117!
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> invalid
> > > > operand: 0000
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: CPU: 
>   0
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: EIP: 
>  
> > > > 0010:[<c01316e7>]    Not tainted
> > > > 
> > > > Using defaults from ksymoops -t elf32-i386 -a
> i386
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> EFLAGS:
> > > > 00010282
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: eax:
> > > 00000020
> > > >   ebx: c16502d8   ecx: 00000001   edx: 000019
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: esi:
> > > 00000000
> > > >   edi: 000001d0   ebp: 00000000   esp: c1755f
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: ds:
> 0018 
> > > 
> > > > es: 0018   ss: 0018
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> Process
> > > > kswapd (pid: 5, stackpage=c1755000)
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> Stack:
> > > > c02250b5 00000075 c013d0e3 ddf7e600 c16502d8
> > > 000001d
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:      
> 
> > > > c16502f4 c16502d8 c16502d8 000001d0 000001d0
> > > c012ff8
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:      
> 
> > > > 00000125 c02c473c 00000c24 00000848 0000000f
> > > c013038
> > > > Dec  1 14:54:58 Republique_ncl_a kernel: Call
> > > Trace:
> > > > [<c013d0e3>] try_to_free_buffers [kernel] 0xb3
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > [<c013b23a>]
> > > > try_to_release_page [kernel] 0x3a
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > [<c012ff8b>]
> > > > page_launder_zone [kernel] 0x42b
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > [<c0130388>]
> > > > page_launder [kernel] 0x168
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > [<c0130c12>]
> > > > do_try_to_free_pages [kernel] 0x12
> > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> 
=== message truncated ===



	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Dirk Henning Gerdes]

Hi Zine!

I didn't get that you have the source-code of the module.
The keyword "tainted" in your lsmod-output shows, that you have a
propritary driver loaded in your system. I thought that would be the
watchdog-driver. But from the sourcecode you can see, that the driver
stands under gpl and won't taint your kernel.
I would strongly suggest to update to 2.4.32 and recompile the
watchdog-module. I don't think, that you will find an error in such old
code in an acceptable time.

Dirk

Am Mittwoch, den 07.12.2005, 10:40 +0100 schrieb zine el abidine Hamid:
> Hello,
> 
> 
> I come back to you. The code of the module wdpiano is
> the next one :
> 
> 
> #include <linux/config.h>
> #include <linux/module.h>
> #include <linux/version.h>
> #include <linux/types.h>
> #include <linux/errno.h>
> #include <linux/kernel.h>
> #include <linux/sched.h>
> #include <linux/miscdevice.h>
> #include <linux/watchdog.h>
> #include <linux/slab.h>
> #include <linux/ioport.h>
> #include <linux/fcntl.h>
> #include <asm/io.h>
> #include <asm/uaccess.h>
> #include <asm/system.h>
> #include <linux/notifier.h>
> #include <linux/reboot.h>
> #include <linux/init.h>
> 
> 
> #define WDIO 0x443
> #define WDIODIS 0x43
> static int wdpiano_is_open=0; // le fichier driver
> n'est pas ouvert
> static unsigned char tempo=10; //temporisation de 10
> second par défaut
> 
> MODULE_PARM(tempo, "b");
> MODULE_PARM_DESC(tempo, "time-out period from 1s to
> 255s (default 10s)");
> MODULE_AUTHOR("Massinissa AGOUDJIL RATP(R)
> <massinissa.agoudjil@ratp.fr>");
> MODULE_LICENSE("GPL");
> 
> static int wdpiano_open(struct inode *inode, struct
> file *file) {
>    if (MINOR(inode->i_rdev)!=WATCHDOG_MINOR) return
> -ENODEV;
>    // access exclusive au fichier de driver
>    if (wdpiano_is_open) return -EBUSY;
>    // Comptage du nombre de chargement
>    MOD_INC_USE_COUNT;
>    //Initialise le timeout
>    outb_p(tempo,WDIO);
>     printk("<1>wdpiano: initialised with a time-out of
> %ds\n",tempo);
>    // limiter l'ouverture 
>    wdpiano_is_open=1;
>    return 0;
> }
> 
> static int wdpiano_release(struct inode *inode, struct
> file *file) {
>    if (MINOR(inode->i_rdev)==WATCHDOG_MINOR) {
> #ifndef CONFIG_WATCHDOG_NOWAYOUT
>       //désactiver le watchdog à la fermeture
>       inb_p(WDIO);
>       inb_p(WDIODIS);
> #endif
>       wdpiano_is_open=0;
>    }
>    MOD_DEC_USE_COUNT;
>    return 0;
> }
> 
> static ssize_t wdpiano_write(struct file *file, const
> char *buf, size_t count, loff_t *ppos) {
>    if (ppos!=&file->f_pos)
>      return -ESPIPE;
>    if (count) {
>       //reinitialiser le timer du watchdog
>       inb_p(WDIODIS);
>       inb_p(WDIO);
>       return 1;
>    }
>    return 0;
> }
> //Un petit message!
> static int wdpiano_notify_sys(struct notifier_block
> *this, unsigned long code,
> 	void *unused) {
> 	if(code==SYS_DOWN || code==SYS_HALT) {
> 	    //désactiver le watchdog à la fermeture
>       	    inb_p(WDIO);
>       	    inb_p(WDIODIS);
> 	}
> 	return NOTIFY_DONE;
> }
> 
> 
> static struct file_operations wdpiano_fops = {
>   owner:          THIS_MODULE,
> // read:           wdpiano_read,
>    write:          wdpiano_write,
>    open:           wdpiano_open,
>    release:        wdpiano_release,
> };
> 
> static struct miscdevice wdpiano_dev = {
>    WATCHDOG_MINOR, //fixer le mineur voir miscdevice.h
> et devices.txt
>      "watchdog",   //fixer le nom de fichier d'accee 
>      &wdpiano_fops
> };
> 
> 
> 
> static struct notifier_block wdpiano_notifier = {
>    wdpiano_notify_sys,
>      NULL,
>      0
> };
> 
> int init_module(void)
> {
>  int retval;
> 
>  printk("Piano watchdog driver RATP(r) V1.0\n");
> 
>  wdpiano_dev.fops = &wdpiano_fops;
>  // Allocation des ressources
>  register_reboot_notifier(&wdpiano_notifier);
>  // Enregistrement du module
>  retval = misc_register(&wdpiano_dev);
> /* if (retval)
>          return retval;*/
>  return 0;
> }
> 
> 
> 
> void cleanup_module(void)
> {
>  printk("<1>wdpiano: cleanup_module\n");
> 
>  // Suppression du module
>  misc_deregister(&wdpiano_dev);
>  //liberation des ressources 
>  unregister_reboot_notifier(&wdpiano_notifier);
> }
> 
> 
> 
> Thank's for your help.
> 
> Zine
> 
> 
> 
> --- Dirk Henning Gerdes <mail@dirk-gerdes.de> a écrit
> :
> 
> > Hi Zine!
> > 
> > That is not the point. But I suppose that the module
> > which runs under
> > 2.4.18 won't run under Linux 2.6. Or quite even
> > under 2.4.32.
> > That could cause some problems, either.
> > If the vendor would give you a new version
> > compatible to 2.6, you could
> > update your whole kernel.
> > 
> > 
> > Am Dienstag, den 06.12.2005, 11:35 +0100 schrieb
> > zine el abidine Hamid:
> > > Why? Do you think that the problem is the module
> > > wdpiano?
> > > 
> > > It's a small program which modify the Watch-Dog
> > Timer
> > > value only...
> > > 
> > > --- Dirk Henning Gerdes <mail@dirk-gerdes.de> a
> > écrit
> > > :
> > > 
> > > > Probably you can contact the manufactor of the
> > board
> > > > to get a driver for
> > > > the watchdog, which runs under newer
> > Linux-versions,
> > > > if you really need
> > > > the watchdog
> > > > Am Montag, den 05.12.2005, 17:48 +0100 schrieb
> > zine
> > > > el abidine Hamid:
> > > > > 
> > > > > I don't know if it's helpfull but the output
> > of
> > > > > ksymoops is :
> > > > > 
> > > > > ksymoops 2.4.4 on i686 2.4.18-3.  Options used
> > > > >      -V (default)
> > > > >      -k /proc/ksyms (default)
> > > > >      -l /proc/modules (default)
> > > > >      -o /lib/modules/2.4.18-3/ (default)
> > > > >      -m /boot/System.map-2.4.18-3 (default)
> > > > > 
> > > > > Warning: You did not tell me where to find
> > symbol
> > > > > information.  I will
> > > > > assume that the log matches the kernel and
> > modules
> > > > > that are running
> > > > > right now and I'll use the default options
> > above
> > > > for
> > > > > symbol resolution.
> > > > > If the current kernel and/or modules do not
> > match
> > > > the
> > > > > log, you can get
> > > > > more accurate output by telling me the kernel
> > > > version
> > > > > and where to find
> > > > > map, modules, ksyms etc.  ksymoops -h explains
> > the
> > > > > options.
> > > > > 
> > > > > Error (expand_objects): cannot
> > stat(/lib/ext3.o)
> > > > for
> > > > > ext3
> > > > > ksymoops: No such file or directory
> > > > > Error (expand_objects): cannot
> > stat(/lib/jbd.o)
> > > > for
> > > > > jbd
> > > > > 
> > > > > ....
> > > > > 
> > > > > 
> > > > > Warning (compare_maps): parport symbol
> > > > > parport_unregister_port not found in
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > > >  Ignoring
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > > entry
> > > > > Warning (compare_maps): parport symbol
> > > > > parport_wait_event not found in
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > > >  Ignoring
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > > entry
> > > > > Warning (compare_maps): parport symbol
> > > > > parport_wait_peripheral not found in
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > > >  Ignoring
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > > entry
> > > > > Warning (compare_maps): parport symbol
> > > > parport_write
> > > > > not found in
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o.
> > > > >  Ignoring
> > > > >
> > > >
> > >
> >
> /lib/modules/2.4.18-3/kernel/drivers/parport/parport.o
> > > > > entry
> > > > > Warning (map_ksym_to_module): cannot match
> > loaded
> > > > > module ext3 to a unique module object.  Trace
> > may
> > > > not
> > > > > be reliable.
> > > > > Warning (map_ksym_to_module): cannot match
> > loaded
> > > > > module jbd to a unique module object.  Trace
> > may
> > > > not
> > > > > be reliable.
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > kernel
> > > > BUG at
> > > > > page_alloc.c:117!
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > invalid
> > > > > operand: 0000
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: CPU: 
> >   0
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: EIP: 
> >  
> > > > > 0010:[<c01316e7>]    Not tainted
> > > > > 
> > > > > Using defaults from ksymoops -t elf32-i386 -a
> > i386
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > EFLAGS:
> > > > > 00010282
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: eax:
> > > > 00000020
> > > > >   ebx: c16502d8   ecx: 00000001   edx: 000019
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: esi:
> > > > 00000000
> > > > >   edi: 000001d0   ebp: 00000000   esp: c1755f
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: ds:
> > 0018 
> > > > 
> > > > > es: 0018   ss: 0018
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > Process
> > > > > kswapd (pid: 5, stackpage=c1755000)
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > Stack:
> > > > > c02250b5 00000075 c013d0e3 ddf7e600 c16502d8
> > > > 000001d
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:      
> > 
> > > > > c16502f4 c16502d8 c16502d8 000001d0 000001d0
> > > > c012ff8
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:      
> > 
> > > > > 00000125 c02c473c 00000c24 00000848 0000000f
> > > > c013038
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel: Call
> > > > Trace:
> > > > > [<c013d0e3>] try_to_free_buffers [kernel] 0xb3
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > > [<c013b23a>]
> > > > > try_to_release_page [kernel] 0x3a
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > > [<c012ff8b>]
> > > > > page_launder_zone [kernel] 0x42b
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > > [<c0130388>]
> > > > > page_launder [kernel] 0x168
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > > > [<c0130c12>]
> > > > > do_try_to_free_pages [kernel] 0x12
> > > > > Dec  1 14:54:58 Republique_ncl_a kernel:
> > 
> === message truncated ===
> 
> 
> 
> 	
> 
> 	
> 		
> ___________________________________________________________________________ 
> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
> Téléchargez cette version sur http://fr.messenger.yahoo.com
> 
-- 
Dirk Henning Gerdes
Bönnersdyk 47
47803 Krefeld

Tel:  02151-755745
      0174-7776640
Mail: mail@dirk-gerdes.de

Kernel BUG at page_alloc.c:117!

[zine el abidine Hamid]

Hi,


I'm using a Linux RedHat kernel 2.4.18-3 and the
system hung after a while with this error
(/var/log/messages):

Dec  1 14:54:58 Republique_ncl_a kernel: ------------[
cut here ]------------
Dec  1 14:54:58 Republique_ncl_a kernel: kernel BUG at
page_alloc.c:117!
Dec  1 14:54:58 Republique_ncl_a kernel: invalid
operand: 0000
Dec  1 14:54:58 Republique_ncl_a kernel: wdpiano
w83781d via686a lm80 i2c-proc i2c-isa i2c-core auto
fs parport_pc plip
Dec  1 14:54:58 Republique_ncl_a kernel: CPU:    0
Dec  1 14:54:58 Republique_ncl_a kernel: EIP:   
0010:[<c01316e7>]    Not tainted
Dec  1 14:54:58 Republique_ncl_a kernel: EFLAGS:
00010282
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel: EIP is at
__free_pages_ok [kernel] 0x57 (2.4.18-3)
Dec  1 14:54:58 Republique_ncl_a kernel: eax: 00000020
  ebx: c16502d8   ecx: 00000001   edx: 000019
0e
Dec  1 14:54:58 Republique_ncl_a kernel: esi: 00000000
  edi: 000001d0   ebp: 00000000   esp: c1755f
38
Dec  1 14:54:58 Republique_ncl_a kernel: ds: 0018  
es: 0018   ss: 0018
Dec  1 14:54:58 Republique_ncl_a kernel: Process
kswapd (pid: 5, stackpage=c1755000)
Dec  1 14:54:58 Republique_ncl_a kernel: Stack:
c02250b5 00000075 c013d0e3 ddf7e600 c16502d8 000001d
0 c013b23a c16502d8
Dec  1 14:54:58 Republique_ncl_a kernel:       
c16502f4 c16502d8 c16502d8 000001d0 000001d0 c012ff8
b 00000c24 0000019d
Dec  1 14:54:58 Republique_ncl_a kernel:       
00000125 c02c473c 00000c24 00000848 0000000f c013038
8 c02c473c 000001d0
Dec  1 14:54:58 Republique_ncl_a kernel: Call Trace:
[<c013d0e3>] try_to_free_buffers [kernel] 0xb3
Dec  1 14:54:58 Republique_ncl_a kernel: [<c013b23a>]
try_to_release_page [kernel] 0x3a
Dec  1 14:54:58 Republique_ncl_a kernel: [<c012ff8b>]
page_launder_zone [kernel] 0x42b
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130388>]
page_launder [kernel] 0x168
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130c12>]
do_try_to_free_pages [kernel] 0x12
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130f11>]
kswapd [kernel] 0x101
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0105000>]
stext [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0107136>]
kernel_thread [kernel] 0x26
Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130e10>]
kswapd [kernel] 0x0
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel:
Dec  1 14:54:58 Republique_ncl_a kernel: Code: 0f 0b
5d 58 8b 3d f0 e2 32 c0 89 d8 29 f8 69 c0 b7 6d
 db b6
Dec  1 14:54:59 Republique_ncl_a ucd-snmp[12873]:
Connection from 111.9.3.13
Dec  1 14:55:30 Republique_ncl_a last message repeated
9 times
Dec  1 14:56:31 Republique_ncl_a last message repeated
17 times



Can anyone explain me what does it mean? What the
problem?   How can I resolve this problem?

Thanks.

Zine. 


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: Kernel BUG at page_alloc.c:117!

[Dirk Henning Gerdes]

Hello Zine,

your kernel is quite old.
Probably it would just help to update to a newer one.
I think on 2.4 the 2.4.32 is the current version.

Dirk

Am Montag, den 05.12.2005, 14:16 +0100 schrieb zine el abidine Hamid:
> Hi,
> 
> 
> I'm using a Linux RedHat kernel 2.4.18-3 and the
> system hung after a while with this error
> (/var/log/messages):
> 
> Dec  1 14:54:58 Republique_ncl_a kernel: ------------[
> cut here ]------------
> Dec  1 14:54:58 Republique_ncl_a kernel: kernel BUG at
> page_alloc.c:117!
> Dec  1 14:54:58 Republique_ncl_a kernel: invalid
> operand: 0000
> Dec  1 14:54:58 Republique_ncl_a kernel: wdpiano
> w83781d via686a lm80 i2c-proc i2c-isa i2c-core auto
> fs parport_pc plip
> Dec  1 14:54:58 Republique_ncl_a kernel: CPU:    0
> Dec  1 14:54:58 Republique_ncl_a kernel: EIP:   
> 0010:[<c01316e7>]    Not tainted
> Dec  1 14:54:58 Republique_ncl_a kernel: EFLAGS:
> 00010282
> Dec  1 14:54:58 Republique_ncl_a kernel:
> Dec  1 14:54:58 Republique_ncl_a kernel: EIP is at
> __free_pages_ok [kernel] 0x57 (2.4.18-3)
> Dec  1 14:54:58 Republique_ncl_a kernel: eax: 00000020
>   ebx: c16502d8   ecx: 00000001   edx: 000019
> 0e
> Dec  1 14:54:58 Republique_ncl_a kernel: esi: 00000000
>   edi: 000001d0   ebp: 00000000   esp: c1755f
> 38
> Dec  1 14:54:58 Republique_ncl_a kernel: ds: 0018  
> es: 0018   ss: 0018
> Dec  1 14:54:58 Republique_ncl_a kernel: Process
> kswapd (pid: 5, stackpage=c1755000)
> Dec  1 14:54:58 Republique_ncl_a kernel: Stack:
> c02250b5 00000075 c013d0e3 ddf7e600 c16502d8 000001d
> 0 c013b23a c16502d8
> Dec  1 14:54:58 Republique_ncl_a kernel:       
> c16502f4 c16502d8 c16502d8 000001d0 000001d0 c012ff8
> b 00000c24 0000019d
> Dec  1 14:54:58 Republique_ncl_a kernel:       
> 00000125 c02c473c 00000c24 00000848 0000000f c013038
> 8 c02c473c 000001d0
> Dec  1 14:54:58 Republique_ncl_a kernel: Call Trace:
> [<c013d0e3>] try_to_free_buffers [kernel] 0xb3
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c013b23a>]
> try_to_release_page [kernel] 0x3a
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c012ff8b>]
> page_launder_zone [kernel] 0x42b
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130388>]
> page_launder [kernel] 0x168
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130c12>]
> do_try_to_free_pages [kernel] 0x12
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130f11>]
> kswapd [kernel] 0x101
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0105000>]
> stext [kernel] 0x0
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0107136>]
> kernel_thread [kernel] 0x26
> Dec  1 14:54:58 Republique_ncl_a kernel: [<c0130e10>]
> kswapd [kernel] 0x0
> Dec  1 14:54:58 Republique_ncl_a kernel:
> Dec  1 14:54:58 Republique_ncl_a kernel:
> Dec  1 14:54:58 Republique_ncl_a kernel: Code: 0f 0b
> 5d 58 8b 3d f0 e2 32 c0 89 d8 29 f8 69 c0 b7 6d
>  db b6
> Dec  1 14:54:59 Republique_ncl_a ucd-snmp[12873]:
> Connection from 111.9.3.13
> Dec  1 14:55:30 Republique_ncl_a last message repeated
> 9 times
> Dec  1 14:56:31 Republique_ncl_a last message repeated
> 17 times
> 
> 
> 
> Can anyone explain me what does it mean? What the
> problem?   How can I resolve this problem?
> 
> Thanks.
> 
> Zine. 
> 
> 
> 	
> 
> 	
> 		
> ___________________________________________________________________________ 
> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
> Téléchargez cette version sur http://fr.messenger.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-- 
Dirk Henning Gerdes
Bönnersdyk 47
47803 Krefeld

Tel:  02151-755745
      0174-7776640
Mail: mail@dirk-gerdes.de