Bug 327841 - Kernel panic in quirk_e100_interrupt
Summary: Kernel panic in quirk_e100_interrupt
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: ppc64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-11 15:50 UTC by Milan Broz
Modified: 2013-03-01 04:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-11 23:31:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Boot log (5.19 KB, text/plain)
2007-10-11 15:50 UTC, Milan Broz 		no flags Details
View All

Description Milan Broz 2007-10-11 15:50:59 UTC 
Description of problem:

Booting Fedora-7.92-ppc-DVD.iso cause kernel panic on OpenPower720

Linux version 2.6.23-0.214.rc8.git2.fc8 (kojibuilder@) (gcc version 4.1.2 
20070925 (Red Hat 4.1.2-28)) #1 SMP Fri Sep 28 17:14:38 EDT 2007
...

Unable to handle kernel paging request for data at address 0xd000080080000003
Faulting instruction address: 0xc0000000001e8cb0
cpu 0x1: Vector: 300 (Data Access) at [c000000002dbba70]
    pc: c0000000001e8cb0: .quirk_e100_interrupt+0x188/0x264
    lr: c0000000001e8c4c: .quirk_e100_interrupt+0x124/0x264
    sp: c000000002dbbcf0
   msr: 8000000000009032
   dar: d000080080000003
 dsisr: 40000000
  current = 0xc00000002ffda000
  paca    = 0xc000000000655380
    pid   = 1, comm = swapper
enter ? for help
[c000000002dbbd90] c0000000001e7724 .pci_fixup_device+0xec/0x11c
[c000000002dbbe20] c0000000001e5644 .pci_init+0x20/0x5c
[c000000002dbbea0] c00000000059ed50 .kernel_init+0x294/0x458
[c000000002dbbf90] c000000000028b60 .kernel_thread+0x4c/0x68

Full log attached.
Comment 1 Milan Broz 2007-10-11 15:50:59 UTC 
Created attachment 224511 [details]
Boot log
Comment 2 Milan Broz 2007-10-11 18:27:12 UTC 
Seems that kernel-2.6.23-0.224.rc9.git6.fc8 boots without problem here.
Comment 3 Chuck Ebbert 2007-10-11 23:31:00 UTC 
Fixed by 1bef7dc00caa7bcbff4fdb55e599e2591461fafa
Note You need to log in before you can comment on or make changes to this bug.