mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO
@ 2003-01-18 17:28 ghugh Song
  0 siblings, 0 replies; 3+ messages in thread
From: ghugh Song @ 2003-01-18 17:28 UTC (permalink / raw)
  To: linux-kernel


I wrote:

> Anthony Lau (anthony@greyweasel.com) wrote:
> 
> > It took awhile for the next oops to appear. I modifed my boot
> > procedure by turning off swap with "swapoff -a" and allowed the
> > system to run. I waited until all of my 1.5GB of physical RAM was
> > allocated (cached or in use), and let the system to contiue to
> > run. The system ran stably for 2 days with normal use. I then
> > switch swap back on with "swapon -a".
> 
> Well. In my case, I tried without swap enabled.
> It still crashed when I issued "tar cf usr.tar /usr"
> 
> Regards,
> 
> G. H. S.
> 

Sorry.  My problem and many others' problem with 2.4.21-pre3-ac2 are 
not quite related to that of the original poster.
I was confused when I saw swap-related posting.

Sorry again.

G. H. S.

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO
@ 2003-01-17 22:17 ghugh Song
  0 siblings, 0 replies; 3+ messages in thread
From: ghugh Song @ 2003-01-17 22:17 UTC (permalink / raw)
  To: linux-kernel


Anthony Lau (anthony@greyweasel.com) wrote:

> It took awhile for the next oops to appear. I modifed my boot
> procedure by turning off swap with "swapoff -a" and allowed the
> system to run. I waited until all of my 1.5GB of physical RAM was
> allocated (cached or in use), and let the system to contiue to
> run. The system ran stably for 2 days with normal use. I then
> switch swap back on with "swapon -a".

Well.  In my case, I tried without swap enabled.
It still crashed when I issued "tar cf usr.tar /usr"

Regards,

G. H. S.

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Kernel Oops with HIMEM+VM in 2.4.19,20
@ 2003-01-10  8:37 Anthony Lau
  2003-01-16  8:34 ` Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO Anthony Lau
  0 siblings, 1 reply; 3+ messages in thread
From: Anthony Lau @ 2003-01-10  8:37 UTC (permalink / raw)
  To: linux-kernel

Hello,

I am getting reproducible kernel oops and random segmentation
faults whenever the kernel starts using VM. Without any VM pages
being used, the system is stable.

I have tested kernels compiled with and without HIMEM support
(all other kernel config options identical). Without HIMEM 4GB
support, the system is stable for weeks. With HIMEM 4GB support,
the system starts oops'ing and seg. faulting when VM starts
being used.

My system info:

1.5GB physical RAM (MemTest86 run for 2 times, no errors)
2.0GB VM on a partition
Aopen AX34u with Via Apollo Pro 133T chipset

Sample Oops from logs:
Jan  8 08:53:59 kimagure kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000317
Jan  8 08:53:59 kimagure kernel:  printing eip:
Jan  8 08:53:59 kimagure kernel: c0146053
Jan  8 08:53:59 kimagure kernel: *pde = 00000000
Jan  8 08:53:59 kimagure kernel: Oops: 0000
Jan  8 08:53:59 kimagure kernel: CPU:    0
Jan  8 08:53:59 kimagure kernel: EIP:    0010:[free_kiovec+83/108]    Not tainted
Jan  8 08:53:59 kimagure kernel: EFLAGS: 00010202
Jan  8 08:53:59 kimagure kernel: eax: 00000000   ebx: df7dcc34   ecx: df7dcc44   edx: df7dcc44
Jan  8 08:53:59 kimagure kernel: esi: f6784800   edi: 00000307   ebp: 00000c59   esp: c222df4c
Jan  8 08:53:59 kimagure kernel: ds: 0018   es: 0018   ss: 0018
Jan  8 08:53:59 kimagure kernel: Process kswapd (pid: 5, stackpage=c222d000)
Jan  8 08:53:59 kimagure kernel: Stack: de765b48 de765b30 df7dcc34 c0144226 df7dcc34 00000011 000001d0 00000020 
Jan  8 08:53:59 kimagure kernel:        00000006 c01444eb 000056a6 c012d760 00000006 000001d0 00000006 000001d0 
Jan  8 08:53:59 kimagure kernel:        c03180c8 00000000 c03180c8 c012d7af 00000020 c03180c8 00000002 c222c000 
Jan  8 08:53:59 kimagure kernel: Call Trace:    [destroy_inode+22/44] [sync_inodes_sb+159/468] [rw_swap_page_base+32/296]
[rw_swap_p
age_base+111/296] [rw_swap_page_base+259/296]
Jan  8 08:53:59 kimagure kernel:   [rw_swap_page+54/72] [__free_pages_ok+109/612] [kernel_thread+40/56]
Jan  8 08:53:59 kimagure kernel: 
Jan  8 08:53:59 kimagure kernel: Code: 8b 47 10 85 c0 74 06 53 ff d0 83 c4 04 ff 4b 2c 0f 94 c0 84 

Because of the symptoms, I think that there could be some
incompatibility between Himem and the VM subsystem. Of course
I may have just configured my kernel incorrectly.

Any help is appreciated and I will gladly supply more logs
if I knew which ones would be useful.

Thanks,

Anthony Lau

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-01-18 17:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-18 17:28 Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO ghugh Song
  -- strict thread matches above, loose matches on Subject: below --
2003-01-17 22:17 ghugh Song
2003-01-10  8:37 Kernel Oops with HIMEM+VM in 2.4.19,20 Anthony Lau
2003-01-16  8:34 ` Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO Anthony Lau

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome