https://bugzilla.kernel.org/show_bug.cgi?id=19462

           Summary: Reproducible Kernel panic/oops during boot and startup
           Product: ACPI
           Version: 2.5
    Kernel Version: 2.6.32
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ACPICA-Core
        AssignedTo: acpi_acpica-c...@kernel-bugs.osdl.org
        ReportedBy: t...@awtrey.com
        Regression: Yes


I've got reproducible kernel panics on recent stable kernels (2.6.32.8/16/23
and 2.6.35.2 specifically), but not on 2.6.30.x kernels. The panic/oops are
occurring on two different hardware platforms; the Panasonic Toughbook CF-19
Mark 3 and and Toughbook CF-74 Mark 4. These are the latest revisions of these
hardware models and we have seen the issue on multiple units.

I'll attach the dmesg output from a few different panics / oops we've captured.
There are two or three variations of kernel panics that repeat, so I'll include
representatives from each type. All of the kernel panics I've seen occur during
 boot (initramfs or early init boot process). Once a system is up and running
fully, I've not seen a single lockup or oops of this type again. I've looked at
related bugs with the acpi subsystem, but haven't seen anything quite like our
issue, so I am opening a new issue here.

FYI, I build mainline kernels, using the Debian config and package process,
with some very minor config tweaks. My base OS is the Squeeze pre-release. My
local mirror has the following package versions for key related packages:

 * udev 160-1
 * module-init-tools 3.12-1
 * initramfs-tools 0.98.1

I have been *unable* to repeat this issue using either a Lenny baseline or a
Squeeze baseline running the 2.6.30 kernel. I'll include the full panic
messages to this ticket for each of the crashes, but here is a summary of the
fun.


The first type of issue reports bugs in the mm/slab.c or kernel/cred.c code.

kernel BUG at mm/slab.c:2972!
invalid opcode: 0000 [#1] SMP 
last sysfs file: /sys/devices/pci0000:00/0000:00:02.1/resource

kernel BUG at mm/slab.c:2974!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/class/net/lo/operstate

kernel BUG at mm/slab.c:2974!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/class/power_supply/BAT1/technology

kernel BUG at mm/slab.c:2974!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/class/power_supply/BAT1/technology

kernel BUG at kernel/cred.c:101!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/class/net/lo/operstate


Another type of issue is a report of an unable to handle kernel paging request

BUG: unable to handle kernel paging request at 52545346
IP: [<c11696af>] acpi_ut_update_object_reference+0x1d/0x11b
*pdpt = 00000000375f1001 *pde = 0000000000000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/class/net/lo/operstate


The the last type of issue we've seen are null pointer dereferences.

BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<(null)>] (null)
*pdpt = 000000003673e001 *pde = 0000000000000000
Oops: 0010 [#1] SMP
last sysfs file:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT1/energy_full

BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<c112dee8>] acpi_ds_build_internal_object+0x10/0x12f
*pdpt = 0000000036e03001 *pde = 0000000000000000
Oops: 0002 [#1] SMP
last sysfs file: /sys/module/processor/initstate

BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<c112dee8>] acpi_ds_build_internal_object+0x10/0x12f
*pdpt = 0000000036ddf001 *pde = 0000000000000000
Oops: 0002 [#1] SMP
last sysfs file: /sys/devices/virtual/net/lo/operstate



Now, it may seem like I'm cluttering up one bug report with too many different
bits of information, but this issue I'm seeing does not appear on any of the
other dozen or so different manufacturers / models I am testing this kernel on.
I've only had issues on these two models and on multiple, different hardware
units.

The steps to reproduce are not exactly easy, but it involves a soft reboot
after disk activity and/or fuse file system mounting. I can repeat this for
testing any patches you may be willing to supply.

Tony

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to