2003-06-21 23:52:35

by John Duthie

[permalink] [raw]
Subject: kswapd 2.4.2? ext3


I don't think kswap should be doing this ....

- ------->8
PID TTY STAT TIME COMMAND
1 ? S 0:12 init [3]
2 ? SW 0:00 [keventd]
3 ? SWN 0:03 [ksoftirqd_CPU0]
4 ? Z 0:14 [kswapd] <defunct>
5 ? SW 0:00 [bdflush]
6 ? SW 0:02 [kupdated]
7 ? SW 0:07 [kjournald]
23 ? SW 0:03 [kjournald]
24 ? SW 0:00 [kjournald]
25 ? SW 0:02 [kjournald]
26 ? SW 0:03 [kjournald]
27 ? SW 0:19 [kjournald]
- ------->8

ext3 fs under load for 24+ hours ( was not defunct 12 hours ago )

P100, 80 GB HDD

total used free shared buffers cached
Mem: 94992 93528 1464 0 9500 33264
-/+ buffers/cache: 50764 44228
Swap: 396600 15384 381216

this machine was stable until I upgraded to ext3 with the 80 gb hdd ..

2.4.20 and 2.4.21 both do this ..

--
John Duthie
E-Mail: <[email protected]>
Phone: +64 9 825 0325
Cell: +64 25 273 4832
ICQ: 14794755
Web: http://www.beyondhelp.co.nz/
please read http://www.beyondhelp.co.nz/contact.html _before_
contacting me with any Unsolicited Electronic Messages.


2003-06-22 00:18:12

by Jeff Sipek

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Same, here. 2.4.20-xfs and 2.4.21 (vanilla) both have some problem in kswapd.
This happened after about 4 days and 6 hours of uptime/load. I use this box
as a router with DHCP, DNS, NTP and SSH (for administration only.)

P100, 10GB HDD (ext3), 32MB RAM

I noticed the two oopses in syslog - see attachment.

Jeff.

- --
Penguin : Linux version 2.5.71 on an i686 machine (3932.16 BogoMips).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+9PkDwFP0+seVj/4RAo42AKC+VN9A8dEslFeFP1HsAMA9wDH/7ACdHxU0
0spiWwszGGrplAgmebO5St4=
=OsE0
-----END PGP SIGNATURE-----


Attachments:
(No filename) (630.00 B)
clearsigned data
oops-2.4.21 (2.24 kB)
Download all attachments

2003-06-22 02:51:54

by Andrew Morton

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

John Duthie <[email protected]> wrote:
>
>
> I don't think kswap should be doing this ....
>
> 4 ? Z 0:14 [kswapd] <defunct>

That means kswapd oopsed and then exitted. It should be in the logs
somewhere.

2003-06-22 17:33:16

by Jeff Sipek

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I almost forgot, here is what ksymoops had to say:

Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod
file?
Jun 21 06:25:19 raptor kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000028
Jun 21 06:25:19 raptor kernel: c01355d4
Jun 21 06:25:19 raptor kernel: *pde = 00000000
Jun 21 06:25:19 raptor kernel: Oops: 0002
Jun 21 06:25:19 raptor kernel: CPU: 0
Jun 21 06:25:19 raptor kernel: EIP: 0010:[cdput+4/64] Not tainted
Jun 21 06:25:19 raptor kernel: EFLAGS: 00010202
Jun 21 06:25:19 raptor kernel: eax: 00000020 ebx: c0e43be0 ecx: 00000020
edx: c0e43bf8
Jun 21 06:25:19 raptor kernel: esi: c10f3f5c edi: c05dd408 ebp: c10f3f64
esp: c10f3f28
Jun 21 06:25:19 raptor kernel: ds: 0018 es: 0018 ss: 0018
Jun 21 06:25:19 raptor kernel: Process kswapd (pid: 4, stackpage=c10f3000)
Jun 21 06:25:19 raptor kernel: Stack: c01419c1 00000020 c0e43be0 c0141a24
c0e43be0 c1588e08 c1588e00 c0141c72
Jun 21 06:25:19 raptor kernel: c10f3f5c 00000013 000001d0 00000020
0000035b c0e43a08 c1276468 00000006
Jun 21 06:25:19 raptor kernel: c0141caf 00000000 c012a429 00000006
000001d0 00000006 000001d0 00000006
Jun 21 06:25:19 raptor kernel: Call Trace: [clear_inode+185/212]
[dispose_list+72/96] [prune_icache+190/224] [shrink_icache_memory+27/48]
[shrink_caches+109/132]
Jun 21 06:25:19 raptor kernel: Code: ff 49 08 0f 94 c0 84 c0 74 26 8b 51 04 8b
01 89 50 04 89 02
Using defaults from ksymoops -t elf32-i386 -a i386


>>ebx; c0e43be0 <END_OF_CODE+b4eebc/????>
>>edx; c0e43bf8 <END_OF_CODE+b4eed4/????>
>>esi; c10f3f5c <END_OF_CODE+dff238/????>
>>edi; c05dd408 <END_OF_CODE+2e86e4/????>
>>ebp; c10f3f64 <END_OF_CODE+dff240/????>
>>esp; c10f3f28 <END_OF_CODE+dff204/????>

Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: ff 49 08 decl 0x8(%ecx)
Code; 00000003 Before first symbol
3: 0f 94 c0 sete %al
Code; 00000006 Before first symbol
6: 84 c0 test %al,%al
Code; 00000008 Before first symbol
8: 74 26 je 30 <_EIP+0x30> 00000030 Before first
symbol
Code; 0000000a Before first symbol
a: 8b 51 04 mov 0x4(%ecx),%edx
Code; 0000000d Before first symbol
d: 8b 01 mov (%ecx),%eax
Code; 0000000f Before first symbol
f: 89 50 04 mov %edx,0x4(%eax)
Code; 00000012 Before first symbol
12: 89 02 mov %eax,(%edx)

Jun 21 06:25:22 raptor kernel: <1>Unable to handle kernel NULL pointer
dereference at virtual address 00000028
Jun 21 06:25:22 raptor kernel: c01355d4
Jun 21 06:25:22 raptor kernel: *pde = 00000000
Jun 21 06:25:22 raptor kernel: Oops: 0002
Jun 21 06:25:22 raptor kernel: CPU: 0
Jun 21 06:25:22 raptor kernel: EIP: 0010:[cdput+4/64] Not tainted
Jun 21 06:25:22 raptor kernel: EFLAGS: 00010202
Jun 21 06:25:22 raptor kernel: eax: 00000020 ebx: c0eb3be0 ecx: 00000020
edx: c0eb3bf8
Jun 21 06:25:22 raptor kernel: esi: c0b69dbc edi: c1a79288 ebp: c0b69dc4
esp: c0b69d88
Jun 21 06:25:22 raptor kernel: ds: 0018 es: 0018 ss: 0018
Jun 21 06:25:22 raptor kernel: Process find (pid: 571, stackpage=c0b69000)
Jun 21 06:25:22 raptor kernel: Stack: c01419c1 00000020 c0eb3be0 c0141a24
c0eb3be0 c1a790a8 c1a790a0 c0141c72
Jun 21 06:25:22 raptor kernel: c0b69dbc 00000018 000001f0 00000020
00000439 c0eb3a08 c0ee0688 00000006
Jun 21 06:25:22 raptor kernel: c0141caf 00000000 c012a429 00000006
000001f0 00000006 000001f0 00000006
Jun 21 06:25:22 raptor kernel: Call Trace: [clear_inode+185/212]
[dispose_list+72/96] [prune_icache+190/224] [shrink_icache_memory+27/48]
[shrink_caches+109/132]
Jun 21 06:25:23 raptor kernel: Code: ff 49 08 0f 94 c0 84 c0 74 26 8b 51 04 8b
01 89 50 04 89 02


>>ebx; c0eb3be0 <END_OF_CODE+bbeebc/????>
>>edx; c0eb3bf8 <END_OF_CODE+bbeed4/????>
>>esi; c0b69dbc <END_OF_CODE+875098/????>
>>edi; c1a79288 <END_OF_CODE+1784564/????>
>>ebp; c0b69dc4 <END_OF_CODE+8750a0/????>
>>esp; c0b69d88 <END_OF_CODE+875064/????>

Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: ff 49 08 decl 0x8(%ecx)
Code; 00000003 Before first symbol
3: 0f 94 c0 sete %al
Code; 00000006 Before first symbol
6: 84 c0 test %al,%al
Code; 00000008 Before first symbol
8: 74 26 je 30 <_EIP+0x30> 00000030 Before first
symbol
Code; 0000000a Before first symbol
a: 8b 51 04 mov 0x4(%ecx),%edx
Code; 0000000d Before first symbol
d: 8b 01 mov (%ecx),%eax
Code; 0000000f Before first symbol
f: 89 50 04 mov %edx,0x4(%eax)
Code; 00000012 Before first symbol
12: 89 02 mov %eax,(%edx)


2 warnings issued. Results may not be reliable.

- --
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+9eudwFP0+seVj/4RAtMaAKC5aB56bLYk6luT5g0AcfzifPzErgCfaioT
sz4Di9Q7WkJRClkJihPZXlQ=
=/deJ
-----END PGP SIGNATURE-----

2003-06-22 17:47:35

by Jim Gifford

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

I get the same problem, but I never get a oops, because the system is
completely locked up. The wierd part about this is that if I leave a command
prompt open, I can type in a command, but it never gets executed. I even
tried to use the sysrq to get information and that doesn't even work,
because syslog is dead. Here is my system information. After about 20 hours
uptime server locks up.

Dell Poweredge 4200
2 - Pentium II - 333mhz
1 GIG ECC EDO RAM
Dell Perc2(Megaraid Controller) - Setup as WriteThru and DirectIO
Adaptec Duo Network Adapter

Using kernel 2.4.21 with the latest 1.18i driver from LSILogic for the
Megaraid, no other patches, built from source code only

I am a Linux From Scratch user, I have used the same config file since
kernel 2.4.17 with no problems, problems first appeared in kernel 2.4.20. I
have had the system checked, the memory tested, and changed raid
controllers. I have even checked cron events at the time it locks up

If you have a patch you would like me to test send it and I can report back
in 24 hours. I do have the capability of hooking up a laptop to the serial
port of the computer to collect statistics.

----- Original Message -----
From: "Andrew Morton" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Saturday, June 21, 2003 8:06 PM
Subject: Re: kswapd 2.4.2? ext3


> John Duthie <[email protected]> wrote:
> >
> >
> > I don't think kswap should be doing this ....
> >
> > 4 ? Z 0:14 [kswapd] <defunct>
>
> That means kswapd oopsed and then exitted. It should be in the logs
> somewhere.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

2003-06-22 22:23:45

by John Duthie

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

On Sat, 21 Jun 2003, Andrew Morton wrote:

yes there is one......

would it have somthign to do with a 50 Gb partition ?? (ext3)

spudgun@hades:/var/log$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda1 1015704 268580 694516 28% /
/dev/hda3 8131028 2991132 4720200 39% /usr
/dev/hda5 1523568 534240 910612 37% /tmp
/dev/hda8 54396016 47058196 4530064 92% /share
/dev/hda7 8130996 2646480 5064820 35% /home
/dev/hda6 4069296 2207180 1652068 58% /usr/local


Unable to handle kernel NULL pointer dereference at virtual address
00000028
c0161203
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0161203>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010207
eax: 00000000 ebx: 00000000 ecx: c1163f18 edx: 00000000
esi: c3cac860 edi: 00000000 ebp: c0286b90 esp: c1163f18
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 4, stackpage=c1163000)
Stack: 00000000 c10d7bb4 000001d0 000009f1 c0158622 c11fda60 c10d7bb4
000001d0
c013439a c10d7bb4 000001d0 000001d0 c10d7bb4 c012b4c8 c10d7bb4
000001d0
c1162000 00000101 000001d0 00000003 00000020 000001d0 00000020
00000006
Call Trace: [<c0158622>] [<c013439a>] [<c012b4c8>] [<c012b6b0>]
[<c012b710>]
[<c012b820>] [<c012b886>] [<c012b9ad>] [<c0105000>] [<c0105676>]
[<c012b910>]
Code: 8b 5b 28 f6 42 19 04 75 24 39 f3 75 f1 f7 44 24 1c 50 00 00


>>EIP; c0161203 <journal_try_to_free_buffers+23/a0> <=====

>>ecx; c1163f18 <_end+e56694/65517dc>
>>esi; c3cac860 <_end+399efdc/65517dc>
>>ebp; c0286b90 <contig_page_data+b0/340>
>>esp; c1163f18 <_end+e56694/65517dc>
Trace; c0158622 <ext3_releasepage+22/30>
Trace; c013439a <try_to_release_page+3a/50>
Trace; c012b4c8 <shrink_cache+258/300>
Trace; c012b6b0 <shrink_caches+50/80>
Trace; c012b710 <try_to_free_pages_zone+30/50>
Trace; c012b820 <kswapd_balance_pgdat+50/a0>
Trace; c012b886 <kswapd_balance+16/30>
Trace; c012b9ad <kswapd+9d/c0>
Trace; c0105000 <_stext+0/0>
Trace; c0105676 <arch_kernel_thread+26/30>
Trace; c012b910 <kswapd+0/c0>

Code; c0161203 <journal_try_to_free_buffers+23/a0>
00000000 <_EIP>:
Code; c0161203 <journal_try_to_free_buffers+23/a0> <=====
0: 8b 5b 28 mov 0x28(%ebx),%ebx <=====
Code; c0161206 <journal_try_to_free_buffers+26/a0>
3: f6 42 19 04 testb $0x4,0x19(%edx)
Code; c016120a <journal_try_to_free_buffers+2a/a0>
7: 75 24 jne 2d <_EIP+0x2d>
Code; c016120c <journal_try_to_free_buffers+2c/a0>
9: 39 f3 cmp %esi,%ebx
Code; c016120e <journal_try_to_free_buffers+2e/a0>
b: 75 f1 jne fffffffe <_EIP+0xfffffffe>
Code; c0161210 <journal_try_to_free_buffers+30/a0>
d: f7 44 24 1c 50 00 00 testl $0x50,0x1c(%esp,1)
Code; c0161217 <journal_try_to_free_buffers+37/a0>
14: 00




-> Date: Sat, 21 Jun 2003 20:06:17 -0700
-> From: Andrew Morton <[email protected]>
-> To: [email protected]
-> Cc: [email protected]
-> Subject: Re: kswapd 2.4.2? ext3
->
-> John Duthie <[email protected]> wrote:
-> >
-> >
-> > I don't think kswap should be doing this ....
-> >
-> > 4 ? Z 0:14 [kswapd] <defunct>
->
-> That means kswapd oopsed and then exitted. It should be in the logs
-> somewhere.
->
-> -
-> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
-> the body of a message to [email protected]
-> More majordomo info at http://vger.kernel.org/majordomo-info.html
-> Please read the FAQ at http://www.tux.org/lkml/
->

--
John Duthie
E-Mail: <[email protected]>
Phone: +64 9 825 0325
Cell: +64 25 273 4832
ICQ: 14794755
Web: http://www.beyondhelp.co.nz/
please read http://www.beyondhelp.co.nz/contact.html _before_
contacting me with any Unsolicited Electronic Messages.


Attachments:
.config (19.21 kB)

2003-06-22 22:37:44

by Andrew Morton

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

John Duthie <[email protected]> wrote:
>
> yes there is one......
>
> would it have somthign to do with a 50 Gb partition ?? (ext3)

More likely a random memory scribble or faulty memory. Suggest
you run memtest86 for 24 hours on that machines.

2003-06-23 12:49:19

by Torsten Wolf

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

On Son, 22 Jun 2003, John Duthie wrote:

>I don't think kswap should be doing this ....

The same here; I posted this a few weeks ago but as I was advised to
reproduce the error without the modules (that I need) loaded at that
time, the issue wasn't further investigated.

I also have 2.4.20 with several ext3 filesystems in use. Occasionally
(and only since 2.4.20) I get the error attached below. Perhaps Andrew's
suggestion (flaky hardware) aims in the right direction as I seldom
encounter problems with bzip2; however, memtest never found an error on
this machine.


Jun 21 09:07:16 b147 kernel: kernel BUG at page_alloc.c:102!
Jun 21 09:07:16 b147 kernel: invalid operand: 0000
Jun 21 09:07:16 b147 kernel: CPU: 0
Jun 21 09:07:16 b147 kernel: EIP: 0010:[<c0133bc3>] Tainted: PF
Using defaults from ksymoops -t elf32-i386 -a i386
Jun 21 09:07:16 b147 kernel: EFLAGS: 00010286
Jun 21 09:07:16 b147 kernel: eax: c13d854c ebx: c1959240 ecx:
00000000 edx: f7ecdd24
Jun 21 09:07:16 b147 kernel: esi: c1959240 edi: 00000000 ebp:
c02c7f00 esp: f7ef5f0c
Jun 21 09:07:16 b147 kernel: ds: 0018 es: 0018 ss: 0018
Jun 21 09:07:16 b147 kernel: Process kswapd (pid: 4, stackpage=f7ef5000)
Jun 21 09:07:16 b147 kernel: Stack: 00000282 00000003 f1e4d240 f1e4d240
f1e4d240 c1959240 c013f312 f1e4d240
Jun 21 09:07:16 b147 kernel: f7ecdd24 c1959240 00005a10 c02c7f00
c0133009 c1959240 000001d0 f7ef4000
Jun 21 09:07:16 b147 kernel: 00000200 000001d0 0000001e 00000020
000001d0 00000020 00000006 c01331e1
Jun 21 09:07:16 b147 kernel: Call Trace: [<c013f312>] [<c0133009>]
[<c01331e1>] [<c0133256>] [<c0133384>]
Jun 21 09:07:16 b147 kernel: [<c01333e9>] [<c013351d>] [<c0105000>]
[<c01072be>] [<c0133480>]
Jun 21 09:07:16 b147 kernel: Code: 0f 0b 66 00 db cc 28 c0 89 d8 2b 05
50 51 34 c0 c1 f8 04 69


>>EIP; c0133bc3 <__free_pages_ok+43/290> <=====

>>eax; c13d854c <_end+106ad74/385858a8>
>>ebx; c1959240 <_end+15eba68/385858a8>
>>edx; f7ecdd24 <_end+37b6054c/385858a8>
>>esi; c1959240 <_end+15eba68/385858a8>
>>ebp; c02c7f00 <contig_page_data+160/340>
>>esp; f7ef5f0c <_end+37b88734/385858a8>

Trace; c013f312 <try_to_free_buffers+82/100>
Trace; c0133009 <shrink_cache+279/300>
Trace; c01331e1 <shrink_caches+61/a0>
Trace; c0133256 <try_to_free_pages_zone+36/60>
Trace; c0133384 <kswapd_balance_pgdat+54/a0>
Trace; c01333e9 <kswapd_balance+19/30>
Trace; c013351d <kswapd+9d/c0>
Trace; c0105000 <_stext+0/0>
Trace; c01072be <arch_kernel_thread+2e/40>
Trace; c0133480 <kswapd+0/c0>

Code; c0133bc3 <__free_pages_ok+43/290>
00000000 <_EIP>:
Code; c0133bc3 <__free_pages_ok+43/290> <=====
0: 0f 0b ud2a <=====
Code; c0133bc5 <__free_pages_ok+45/290>
2: 66 data16
Code; c0133bc6 <__free_pages_ok+46/290>
3: 00 db add %bl,%bl
Code; c0133bc8 <__free_pages_ok+48/290>
5: cc int3
Code; c0133bc9 <__free_pages_ok+49/290>
6: 28 c0 sub %al,%al
Code; c0133bcb <__free_pages_ok+4b/290>
8: 89 d8 mov %ebx,%eax
Code; c0133bcd <__free_pages_ok+4d/290>
a: 2b 05 50 51 34 c0 sub 0xc0345150,%eax
Code; c0133bd3 <__free_pages_ok+53/290>
10: c1 f8 04 sar $0x4,%eax
Code; c0133bd6 <__free_pages_ok+56/290>
13: 69 00 00 00 00 00 imul $0x0,(%eax),%eax

Best wishes,
Torsten

2003-06-25 01:25:20

by Jim Gifford

[permalink] [raw]
Subject: Re: kswapd 2.4.2? ext3

I figured out what my problem was, and Andrew was right(as usual). It ended
up being my raid 5 controller and the a few settings.

First I updated the raid driver from Megaraid 1.18f to 1.18i. Then changed
the cache from writeback to writethru and changed the write mode from
cachedIO to directIO and now I have been up for 2 days 8 hours without a
lockup like I was getting before.

----- Original Message -----
From: "Torsten Wolf" <[email protected]>
To: <[email protected]>
Sent: Monday, June 23, 2003 3:16 AM
Subject: Re: kswapd 2.4.2? ext3


> On Son, 22 Jun 2003, John Duthie wrote:
>
> >I don't think kswap should be doing this ....
>
> The same here; I posted this a few weeks ago but as I was advised to
> reproduce the error without the modules (that I need) loaded at that
> time, the issue wasn't further investigated.
>
> I also have 2.4.20 with several ext3 filesystems in use. Occasionally
> (and only since 2.4.20) I get the error attached below. Perhaps Andrew's
> suggestion (flaky hardware) aims in the right direction as I seldom
> encounter problems with bzip2; however, memtest never found an error on
> this machine.
>
>
> Jun 21 09:07:16 b147 kernel: kernel BUG at page_alloc.c:102!
> Jun 21 09:07:16 b147 kernel: invalid operand: 0000
> Jun 21 09:07:16 b147 kernel: CPU: 0
> Jun 21 09:07:16 b147 kernel: EIP: 0010:[<c0133bc3>] Tainted: PF
> Using defaults from ksymoops -t elf32-i386 -a i386
> Jun 21 09:07:16 b147 kernel: EFLAGS: 00010286
> Jun 21 09:07:16 b147 kernel: eax: c13d854c ebx: c1959240 ecx:
> 00000000 edx: f7ecdd24
> Jun 21 09:07:16 b147 kernel: esi: c1959240 edi: 00000000 ebp:
> c02c7f00 esp: f7ef5f0c
> Jun 21 09:07:16 b147 kernel: ds: 0018 es: 0018 ss: 0018
> Jun 21 09:07:16 b147 kernel: Process kswapd (pid: 4, stackpage=f7ef5000)
> Jun 21 09:07:16 b147 kernel: Stack: 00000282 00000003 f1e4d240 f1e4d240
> f1e4d240 c1959240 c013f312 f1e4d240
> Jun 21 09:07:16 b147 kernel: f7ecdd24 c1959240 00005a10 c02c7f00
> c0133009 c1959240 000001d0 f7ef4000
> Jun 21 09:07:16 b147 kernel: 00000200 000001d0 0000001e 00000020
> 000001d0 00000020 00000006 c01331e1
> Jun 21 09:07:16 b147 kernel: Call Trace: [<c013f312>] [<c0133009>]
> [<c01331e1>] [<c0133256>] [<c0133384>]
> Jun 21 09:07:16 b147 kernel: [<c01333e9>] [<c013351d>] [<c0105000>]
> [<c01072be>] [<c0133480>]
> Jun 21 09:07:16 b147 kernel: Code: 0f 0b 66 00 db cc 28 c0 89 d8 2b 05
> 50 51 34 c0 c1 f8 04 69
>
>
> >>EIP; c0133bc3 <__free_pages_ok+43/290> <=====
>
> >>eax; c13d854c <_end+106ad74/385858a8>
> >>ebx; c1959240 <_end+15eba68/385858a8>
> >>edx; f7ecdd24 <_end+37b6054c/385858a8>
> >>esi; c1959240 <_end+15eba68/385858a8>
> >>ebp; c02c7f00 <contig_page_data+160/340>
> >>esp; f7ef5f0c <_end+37b88734/385858a8>
>
> Trace; c013f312 <try_to_free_buffers+82/100>
> Trace; c0133009 <shrink_cache+279/300>
> Trace; c01331e1 <shrink_caches+61/a0>
> Trace; c0133256 <try_to_free_pages_zone+36/60>
> Trace; c0133384 <kswapd_balance_pgdat+54/a0>
> Trace; c01333e9 <kswapd_balance+19/30>
> Trace; c013351d <kswapd+9d/c0>
> Trace; c0105000 <_stext+0/0>
> Trace; c01072be <arch_kernel_thread+2e/40>
> Trace; c0133480 <kswapd+0/c0>
>
> Code; c0133bc3 <__free_pages_ok+43/290>
> 00000000 <_EIP>:
> Code; c0133bc3 <__free_pages_ok+43/290> <=====
> 0: 0f 0b ud2a <=====
> Code; c0133bc5 <__free_pages_ok+45/290>
> 2: 66 data16
> Code; c0133bc6 <__free_pages_ok+46/290>
> 3: 00 db add %bl,%bl
> Code; c0133bc8 <__free_pages_ok+48/290>
> 5: cc int3
> Code; c0133bc9 <__free_pages_ok+49/290>
> 6: 28 c0 sub %al,%al
> Code; c0133bcb <__free_pages_ok+4b/290>
> 8: 89 d8 mov %ebx,%eax
> Code; c0133bcd <__free_pages_ok+4d/290>
> a: 2b 05 50 51 34 c0 sub 0xc0345150,%eax
> Code; c0133bd3 <__free_pages_ok+53/290>
> 10: c1 f8 04 sar $0x4,%eax
> Code; c0133bd6 <__free_pages_ok+56/290>
> 13: 69 00 00 00 00 00 imul $0x0,(%eax),%eax
>
> Best wishes,
> Torsten
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>