| Summary: | OOPS | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | gcarter | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-01 23:49:56 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Both oopses shown in the photo have the D taint flag set, which means the kernel was already dying when they happened. Perhaps the first oops scrolled off the screen? Can you look in /var/log/messages to see if there is one listed in there? Yes I see that. I have a number of removables that due give me problems. One is my SDCARD, the other is a rather finicky express card eSata adapter which as of late doesn't seem to work any more. My USB tends too time out during bootup for my SDCARD. So there are timeouts in the init phase of the kernel boot up for the device. That might be a bug in the driver code, not sure I am too busy looking at why pass through isn't working with my USB wireless at the moment. I am forwarding you the entire messages log. I would attach it here, but there is not facility to do so, and pasting it doesn't work for some reason. I am going to pick up a new SDCARD and eSata express card, see if that fixes my timeout issues. -gc I could not fit the message file in this message so I forwarded it to jwboyer. It would appear that with further investigation my smart card reader built into my W840 machine is not correctly initializing at startup. I think that is why abrt fires up sometimes, but it displays nothing. It doesn't happen all the time though. In either case, once the machine boots up I don't have any more issues, so I am wondering if the SDCARD reader needs more time to initialize during the bootup process. According to lspci this is a SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter So I might tinker with the initialization code and see if I can get it to stop timing out on my machine, assuming there is no hardware issues. I will have a look at that today, post later my results. -gc mmc issue is related to bug id 772474. Closing. -gc |
Created attachment 555633 [details] Camera off my Phone shot of the OOPS screen Description of problem: OOPS, looks like ACPI issue. Version-Release number of selected component (if applicable): menuentry 'Fedora (3.1.9-1.fc16.x86_64)' --class fedora --class gnu-linux --class gnu --class os { load_video insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root c8ae474a-1473-4ab8-8a04-f64db4b5c535 echo 'Loading Fedora (3.1.9-1.fc16.x86_64)' linux /vmlinuz-3.1.9-1.fc16.x86_64 root=UUID=a18f7c65-dc51-47ce-975f-b66eda77b415 intel_iommu=on ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.1.9-1.fc16.x86_64.img } [gcarter@kali log]$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 00:1f.5 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) 01:00.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:00.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:04.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:05.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 03:00.0 VGA compatible controller: ATI Technologies Inc Device 9509 06:00.0 VGA compatible controller: ATI Technologies Inc Device 9509 06:00.1 Audio device: ATI Technologies Inc Radeon HD 3870 Audio device 08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12) 0b:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) 0c:00.0 SATA controller: JMicron Technology Corp. JMB360 AHCI Controller (rev 02) 0e:07.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 0e:07.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 0e:07.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) [ How reproducible: Not sure. Steps to Reproduce: 1. 2. 3. Actual results: OOPS Expected results: No OOPS Additional info: I took a photo with my Sprint EVO 3D. See attached screen.