Kernel panic on Low-address protection (s390x)

Solution Verified - Updated -

Issue

  • Access via invalid TLB entries can cause a variety of problems, from simple crashes to subtle data consistency issues.
  • System kernel panics with the following 3270 console output:
Low-address protection: 0004 [#1]
CPU:
 1 Tainted: G      2.6.18-164.15.1.el5 #1
Process java (pid: 7327, 
task: 00000002f18b2be8, ksp: 000000024029fba8)
User PSW : 
0705e00180000000 0000020003bd56d8 (0x20003bd56d8)
User GPRS: 
000000000005d3e0 000000008002e378 0000000000000000 0000000000000000

          0000020009d35650 0000000000000d90 000000008002d9e8 
00000200053e2400
           0000000000036400 0000020009d35650 
000000000174f800 0000000000406c00
           00000047d6576000 
0000020003be08b8 0000020003bb067c 000002000b124768
User Code: a8 42 
00 00 a7 14 ff fe 07 fe 07 07 a7 29 00 00 07 fe 07 07

<0>Kernel panic - not syncing: Fatal exception: panic_on_oops

Environment

  • Red Hat Enterprise Linux 5
  • IBM System z

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.