54583 – [Ubuntu 12.04 LTS 32-bit] Occasional ATI Radeon 9800 Pro and Intel D815EEA2 Mainboard ACPI S3 State Resume Freeze

Bug 54583 - [Ubuntu 12.04 LTS 32-bit] Occasional ATI Radeon 9800 Pro and Intel D815EEA2 Mainboard ACPI S3 State Resume Freeze

Summary: [Ubuntu 12.04 LTS 32-bit] Occasional ATI Radeon 9800 Pro and Intel D815EEA2 M...

Status:	RESOLVED NOTABUG

Alias:	None

Product:	xorg
Classification:	Unclassified
Component:	Driver/Radeon (show other bugs)
Version:	unspecified
Hardware:	x86 (IA32) Linux (All)

Importance:	highest critical
Assignee:	xf86-video-ati maintainers
QA Contact:	Xorg Project Team

URL:	https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-09-06 06:55 UTC by mypersonalmailbox1
Modified:	2013-02-14 01:59 UTC (History)
CC List:	1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
BootDmesg.txt (37.67 KB, text/plain) 2012-09-06 06:56 UTC, mypersonalmailbox1	no flags	Details
CurrentDmesg.txt (9.22 KB, text/plain) 2012-09-06 06:57 UTC, mypersonalmailbox1	no flags	Details
Lspci.txt (7.19 KB, text/plain) 2012-09-06 06:58 UTC, mypersonalmailbox1	no flags	Details
XorgLog.txt (47.92 KB, text/plain) 2012-09-06 06:58 UTC, mypersonalmailbox1	no flags	Details
XorgLogOld.txt (45.79 KB, text/plain) 2012-09-06 06:59 UTC, mypersonalmailbox1	no flags	Details
dmesg.0.txt radeon.agpmode=-1 added (35.67 KB, text/plain) 2012-10-13 23:59 UTC, mypersonalmailbox1	no flags	Details
kern.log radeon.agpmode=-1 added (389.79 KB, text/plain) 2012-10-14 00:08 UTC, mypersonalmailbox1	no flags	Details
Xorg.0.log.old.txt radeon.agpmode=-1 added (49.03 KB, text/plain) 2012-10-14 00:09 UTC, mypersonalmailbox1	no flags	Details
pm-suspend.log radeon.agpmode=-1 added (28.91 KB, text/plain) 2012-10-14 00:12 UTC, mypersonalmailbox1	no flags	Details
pm-powersave.log radeon.agpmode=-1 added (30.61 KB, text/plain) 2012-10-14 00:13 UTC, mypersonalmailbox1	no flags	Details
kern.log radeon.agpmode=-1 finally working (437.67 KB, text/plain) 2012-11-16 12:24 UTC, mypersonalmailbox1	no flags	Details
View All

Description mypersonalmailbox1 2012-09-06 06:55:40 UTC

Hi,

I will like to report occasional instability of ATI Radeon 9800 Pro and Intel D815EEA2 mainboard when resuming from ACPI S3 state.
Roughly 9 out of 10 times, the computer resumes from ACPI S3 State fine, but once in a while, it will freeze.
This problem is pretty difficult to reproduce (happens randomly), but again, it happens about roughly 9 out of 10 tries.

System Configuration:

- Ubuntu 12.04 LTS 32-bit
- Intel Pentium III 1 GHz
- Intel D815EEA2 mainboard
  * BIOS Version P21-0039
  * Power -> ACPI -> ACPI: S3 State
  * Power -> ACPI -> Video RePOST: Off
- 512 MB PC133 SDRAM
  * 256MB module
  * 128MB module
  * 128MB module
- ATI Radeon 9800 Pro
  * AGP
  * 128MB
- Seagate ST320414A 20GB PATA hard drive
- Pioneer DVR-105 PATA DVD-RW drive
- Hitachi CDR-7930 PATA CD-ROM drive
- USB keyboard
- USB mouse


It is only that ACPI S3 State resume doesn't work 100% reliably.
Please fix this problem.

Regards,

fpgahardwareengineer

Comment 1 mypersonalmailbox1 2012-09-06 06:56:45 UTC

Created attachment 66705 [details]
BootDmesg.txt

Comment 2 mypersonalmailbox1 2012-09-06 06:57:31 UTC

Created attachment 66706 [details]
CurrentDmesg.txt

Comment 3 mypersonalmailbox1 2012-09-06 06:58:03 UTC

Created attachment 66707 [details]
Lspci.txt

Comment 4 mypersonalmailbox1 2012-09-06 06:58:31 UTC

Created attachment 66708 [details]
XorgLog.txt

Comment 5 mypersonalmailbox1 2012-09-06 06:59:06 UTC

Created attachment 66709 [details]
XorgLogOld.txt

Comment 6 mypersonalmailbox1 2012-09-06 07:04:12 UTC

I spend a fair amount of my personal time testing hardware for Linux and writing these reports.
Please, fix these serious bugs.

Comment 7 Alex Deucher 2012-09-06 13:09:04 UTC

Does disabling AGP help?  Try adding radeon.agpmode=-1 to the kernel command line in grub.

Comment 8 mypersonalmailbox1 2012-09-09 04:28:48 UTC

Hi Alex,

Is it possible you can give me detailed instructions on how to do this?
I have gone to grub by pressing shift key during boot, and furthermore pressed e key to edit the boot script.
I don't know how to make the change permanent from grub's simple editor.
How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP mode?
    Also, I have provided more information about Bug 52952 (Ubuntu 10.04.4 LTS 32-bit and ATI Technologies Radeon Xpress 200 for Intel (RC410) ACPI S3 State Resume Failure).
Please respond to that inquiry.

Regards,

fpgahardwareengineer

Comment 9 Alex Deucher 2012-09-09 14:28:52 UTC

(In reply to comment #8)
> Is it possible you can give me detailed instructions on how to do this?
> I have gone to grub by pressing shift key during boot, and furthermore pressed
> e key to edit the boot script.

That's correct.  Just append radeon.agpmode=-1 to the kernel line.

> I don't know how to make the change permanent from grub's simple editor.
> How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP
> mode?

To make it permanent, edit the /etc/grub2.cfg and manually make the change.  You can check the radeon dmesg messages to see whether the card is loaded in AGP or non-AGP mode.

Comment 10 mypersonalmailbox1 2012-09-22 05:51:50 UTC

(In reply to comment #9)
> (In reply to comment #8)
> > Is it possible you can give me detailed instructions on how to do this?
> > I have gone to grub by pressing shift key during boot, and furthermore pressed
> > e key to edit the boot script.
> 
> That's correct.  Just append radeon.agpmode=-1 to the kernel line.
> 
> > I don't know how to make the change permanent from grub's simple editor.
> > How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP
> > mode?
> 
> To make it permanent, edit the /etc/grub2.cfg and manually make the change. 
> You can check the radeon dmesg messages to see whether the card is loaded in
> AGP or non-AGP mode.

I don't see grub2.cfg file under /etc
Again, I am using Ubuntu 12.04.1 LTS 32-bit.
Is there an alternative way to permanently alter the grub options?

Regards,

fpgahardwareengineer

Comment 11 mypersonalmailbox1 2012-10-13 23:59:56 UTC

Created attachment 68542 [details]
dmesg.0.txt radeon.agpmode=-1 added

Comment 12 mypersonalmailbox1 2012-10-14 00:08:03 UTC

Created attachment 68543 [details]
kern.log radeon.agpmode=-1 added

Note the time jump between Oct 13 16:38, Oct 13 16:44, and Oct 13 16:49.
I believe the computer froze during one of those times.

Comment 13 mypersonalmailbox1 2012-10-14 00:09:05 UTC

Created attachment 68544 [details]
Xorg.0.log.old.txt radeon.agpmode=-1 added

Comment 14 mypersonalmailbox1 2012-10-14 00:12:17 UTC

Created attachment 68545 [details]
pm-suspend.log radeon.agpmode=-1 added

Comment 15 mypersonalmailbox1 2012-10-14 00:13:18 UTC

Created attachment 68546 [details]
pm-powersave.log radeon.agpmode=-1 added

Comment 16 mypersonalmailbox1 2012-10-14 00:21:27 UTC

(In reply to comment #9)
> (In reply to comment #8)
> > Is it possible you can give me detailed instructions on how to do this?
> > I have gone to grub by pressing shift key during boot, and furthermore pressed
> > e key to edit the boot script.
> 
> That's correct.  Just append radeon.agpmode=-1 to the kernel line.
> 
> > I don't know how to make the change permanent from grub's simple editor.
> > How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP
> > mode?
> 
> To make it permanent, edit the /etc/grub2.cfg and manually make the change. 
> You can check the radeon dmesg messages to see whether the card is loaded in
> AGP or non-AGP mode.

Hi Alex,

I postponed working on this issue for a while because I was not able to figure out how to permanently alter GRUB loader options.
I broke down, and decided to insert radeon.agpmode=-1 everytime I boot for testing purposes.
By the way, even after adding radeon.agpmode=-1, I still see random freezes and or instability with Radeon 9800 Pro.
Looking at the dmesg.0.txt messages, I think my Radeon 9800 Pro is still being considered an AGP device despite adding the radeon.agpmode=-1 option in GRUB.
Anyway, I added various log files related to power management to the bug report.
Note the time jump between Oct 13 16:38, Oct 13 16:44, and Oct 13 16:49.
I believe at one of those times, the computer froze (with a blank screen).
You can take a look at it to see what is going on.

Regards,

fpgahardwareengineer

Comment 17 mypersonalmailbox1 2012-10-14 00:23:36 UTC

(In reply to comment #16)

> By the way, even after adding radeon.agpmode=-1, I still see random freezes
> and or instability with Radeon 9800 Pro.

By the way, I meant random freezes and/or instability with Radeon 9800 Pro after I come out of ACPI S3 State.
If I don't enter standby, Radeon x.org display device driver is very stable.

Regards,

fpgahadwareengineer.

Comment 18 mypersonalmailbox1 2012-10-14 00:30:50 UTC

Hi Alex,

By the way, ATI Technologies Radeon 9800 Pro's ACPI S3 State resume works fine with ASUS P5VD1-X (VIA Technologies PT880 Ultra/VT8237R Plus chipset).
Although due to Linux 3.2's bug with USB, USB needs to be disabled in BIOS setup to get it working with ASUS P4S8X-MX (SiS 661GX/964 chipset).
As long as USB is disabled and BIOS Revision 0808 is used, ATI Technologies Radeon 9800 Pro's ACPI S3 State resume works fine with ASUS P4S8X-MX.
I wonder why Radeon 9800 Pro has so many problems with Intel 815E chipset?
Intel has fixed lots of ACPI S3 State related bugs according to Intel D815EAA2 mainboard BIOS update release notes.
Of course, I used their last release version of D815EAA2 BIOS for testing.

Regards,

fpgahardwareengineer

Comment 19 Michel Dänzer 2012-10-15 09:33:44 UTC

(In reply to comment #16)
> Looking at the dmesg.0.txt messages, I think my Radeon 9800 Pro is still
> being considered an AGP device despite adding the radeon.agpmode=-1 option
> in GRUB.

The 'Kernel command line:' line in dmesg doesn't show radeon.agpmode=-1, so you failed to effectively add it.

Comment 20 mypersonalmailbox1 2012-11-16 12:23:10 UTC

(In reply to comment #9)

Hi Alex,

I know I neglected this bug report for more than 2 months, but I finally made some progress on it.
Because I am a Linux beginner, I didn't know how to append "radeon.agpmode=-1" to grub, and that set me back for more than 2 months.
I was finally able to append it to grub on a permanent basis, and looked at the dmesg log messages to confirm that my Radeon 9800 Pro is running in PCI mode.
Still, I didn't see any improvement in the ACPI S3 State resume stability.
It crashes/freezes in the same fashion as with older Linux 3.2 kernel (The installed version I used was the latest as of right this moment, Linux 3.2.0-33-generic-pae.).
I will attach kern.log shortly, these are some of the interesting moments of the log.


...

Nov 16 02:55:15 PC13 kernel: [   17.559383] type=1400 audit(1353063315.276:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=549 comm="apparmor_parser"
Nov 16 02:55:15 PC13 kernel: [   17.813339] [drm] radeon defaulting to kernel modesetting.
Nov 16 02:55:15 PC13 kernel: [   17.813354] [drm] radeon kernel modesetting enabled.
Nov 16 02:55:15 PC13 kernel: [   17.813799] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
Nov 16 02:55:15 PC13 kernel: [   17.813816] radeon 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Nov 16 02:55:15 PC13 kernel: [   17.845743] [drm] initializing kernel modesetting (R350 0x1002:0x4E48 0x1002:0x0002).
Nov 16 02:55:15 PC13 kernel: [   17.845756] [drm] Forcing AGP to PCI mode
Nov 16 02:55:15 PC13 kernel: [   17.845808] [drm] register mmio base: 0xFF9F0000
Nov 16 02:55:15 PC13 kernel: [   17.845813] [drm] register mmio size: 65536
Nov 16 02:55:15 PC13 kernel: [   17.846332] [drm] Generation 1 PCI interface in multifunction mode

...

Nov 16 02:55:19 PC13 kernel: [   21.552572] vesafb: framebuffer at 0xe8000000, mapped to 0xe1380000, using 1216k, total 1216k
Nov 16 02:55:19 PC13 kernel: [   21.557079] fb1: VESA VGA frame buffer device
Nov 16 02:55:22 PC13 kernel: [   24.326889] init: plymouth-stop pre-start process (1068) terminated with status 1
Nov 16 02:55:28 PC13 kernel: [   31.016020] eth1: no IPv6 routers present
Nov 16 02:56:21 PC13 kernel: [   83.746521] PM: Syncing filesystems ... done.
Nov 16 02:56:21 PC13 kernel: [   83.752738] PM: Preparing system for mem sleep
Nov 16 02:56:38 PC13 kernel: [   83.875716] Freezing user space processes ... (elapsed 0.01 seconds) done.
Nov 16 02:56:38 PC13 kernel: [   83.892121] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Nov 16 02:56:38 PC13 kernel: [   83.908089] PM: Entering mem sleep
Nov 16 02:56:38 PC13 kernel: [   83.908137] Suspending console(s) (use no_console_suspend to debug)
Nov 16 02:56:38 PC13 kernel: [   83.908857] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov 16 02:56:38 PC13 kernel: [   83.909292] sd 0:0:0:0: [sda] Stopping disk
Nov 16 02:56:38 PC13 kernel: [   83.910247] parport_pc 00:0a: disabled
Nov 16 02:56:38 PC13 kernel: [   83.910380] serial 00:09: disabled
Nov 16 02:56:38 PC13 kernel: [   83.910505] serial 00:08: disabled
Nov 16 02:56:38 PC13 kernel: [   83.910557] serial 00:08: wake-up capability disabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   83.911099] e100 0000:01:08.0: PCI INT A disabled
Nov 16 02:56:38 PC13 kernel: [   83.911117] e100 0000:01:08.0: PME# enabled
Nov 16 02:56:38 PC13 kernel: [   83.911135] pci 0000:00:1e.0: wake-up capability enabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   83.914168] snd_intel8x0 0000:00:1f.5: PCI INT B disabled
Nov 16 02:56:38 PC13 kernel: [   83.924197] uhci_hcd 0000:00:1f.2: PCI INT D disabled
Nov 16 02:56:38 PC13 kernel: [   83.932097] uhci_hcd 0000:00:1f.4: PCI INT C disabled
Nov 16 02:56:38 PC13 kernel: [   84.966715] radeon 0000:02:00.0: PCI INT A disabled
Nov 16 02:56:38 PC13 kernel: [   84.980038] PM: suspend of drv:radeon dev:0000:02:00.0 complete after 1068.769 msecs
Nov 16 02:56:38 PC13 kernel: [   84.980081] PM: suspend of drv:pci dev:0000:00:01.0 complete after 1065.121 msecs
Nov 16 02:56:38 PC13 kernel: [   84.980116] PM: suspend of drv: dev:pci0000:00 complete after 1065.092 msecs
Nov 16 02:56:38 PC13 kernel: [   84.980136] PM: suspend of devices complete after 1071.723 msecs
Nov 16 02:56:38 PC13 kernel: [   84.980144] PM: suspend devices took 1.072 seconds
Nov 16 02:56:38 PC13 kernel: [   84.980551] uhci_hcd 0000:00:1f.4: wake-up capability enabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   84.980617] uhci_hcd 0000:00:1f.2: wake-up capability enabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   84.980743] PM: late suspend of devices complete after 0.591 msecs
Nov 16 02:56:38 PC13 kernel: [   84.980936] ACPI: Preparing to enter system sleep state S3
Nov 16 02:56:38 PC13 kernel: [   84.981495] PM: Saving platform NVS memory
Nov 16 02:56:38 PC13 kernel: [   84.981703] Disabling non-boot CPUs ...
Nov 16 02:56:38 PC13 kernel: [   84.981703] ACPI: Low-level resume complete
Nov 16 02:56:38 PC13 kernel: [   84.981703] PM: Restoring platform NVS memory
Nov 16 02:56:38 PC13 kernel: [   84.981703] ACPI: Waking up from system sleep state S3
Nov 16 02:56:38 PC13 kernel: [   84.981703] agpgart-intel 0000:00:00.0: restoring config space at offset 0x1 (was 0x20900006, writing 0x20900106)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:00:01.0: restoring config space at offset 0x9 (was 0xd6a0, writing 0xf6a0d6a0)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:00:01.0: restoring config space at offset 0x7 (was 0x2a0d0d0, writing 0x22a0d0d0)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:00:1e.0: restoring config space at offset 0x7 (was 0x2280c0c0, writing 0x280c0c0)
Nov 16 02:56:38 PC13 kernel: [   84.981703] uhci_hcd 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Nov 16 02:56:38 PC13 kernel: [   84.981703] uhci_hcd 0000:00:1f.2: wake-up capability disabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   84.981703] uhci_hcd 0000:00:1f.4: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Nov 16 02:56:38 PC13 kernel: [   84.981703] uhci_hcd 0000:00:1f.4: wake-up capability disabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   84.981703] snd_intel8x0 0000:00:1f.5: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:02:00.1: restoring config space at offset 0x5 (was 0x0, writing 0xff9e0000)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:02:00.1: restoring config space at offset 0x4 (was 0x8, writing 0xe0000008)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:02:00.1: restoring config space at offset 0x3 (was 0x0, writing 0x2008)
Nov 16 02:56:38 PC13 kernel: [   84.981703] pci 0000:02:00.1: restoring config space at offset 0x1 (was 0x2b00080, writing 0x2b00087)
Nov 16 02:56:38 PC13 kernel: [   84.981703] PM: early resume of devices complete after 0.777 msecs
Nov 16 02:56:38 PC13 kernel: [   84.984232] pci 0000:00:1e.0: setting latency timer to 64
Nov 16 02:56:38 PC13 kernel: [   84.984259] ata_piix 0000:00:1f.1: setting latency timer to 64
Nov 16 02:56:38 PC13 kernel: [   84.984307] uhci_hcd 0000:00:1f.2: PCI INT D -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Nov 16 02:56:38 PC13 kernel: [   84.984319] uhci_hcd 0000:00:1f.2: setting latency timer to 64
Nov 16 02:56:38 PC13 kernel: [   84.984346] usb usb1: root hub lost power or was reset
Nov 16 02:56:38 PC13 kernel: [   84.984376] uhci_hcd 0000:00:1f.4: PCI INT C -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10
Nov 16 02:56:38 PC13 kernel: [   84.984387] uhci_hcd 0000:00:1f.4: setting latency timer to 64
Nov 16 02:56:38 PC13 kernel: [   84.984410] usb usb2: root hub lost power or was reset
Nov 16 02:56:38 PC13 kernel: [   84.984433] snd_intel8x0 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 9 (level, low) -> IRQ 9
Nov 16 02:56:38 PC13 kernel: [   84.984444] snd_intel8x0 0000:00:1f.5: setting latency timer to 64
Nov 16 02:56:38 PC13 kernel: [   84.984504] radeon 0000:02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Nov 16 02:56:38 PC13 kernel: [   85.000950] [drm] radeon: 2 quad pipes, 1 Z pipes initialized.
Nov 16 02:56:38 PC13 kernel: [   85.009306] [drm] PCIE GART of 512M enabled (table at 0x0000000013800000).
Nov 16 02:56:38 PC13 kernel: [   85.012164] pci 0000:00:1e.0: wake-up capability disabled by ACPI
Nov 16 02:56:38 PC13 kernel: [   85.012178] e100 0000:01:08.0: PME# disabled
Nov 16 02:56:38 PC13 kernel: [   85.012424] sd 0:0:0:0: [sda] Starting disk
Nov 16 02:56:38 PC13 kernel: [   85.013002] radeon 0000:02:00.0: WB enabled
Nov 16 02:56:38 PC13 kernel: [   85.013048] [drm] radeon: ring at 0x00000000C8001000
Nov 16 02:56:38 PC13 kernel: [   85.013077] [drm] ring test succeeded in 1 usecs
Nov 16 02:56:38 PC13 kernel: [   85.013122] [drm] ib test succeeded in 0 usecs
Nov 16 02:56:38 PC13 kernel: [   85.094074] PM: resume of drv:radeon dev:0000:02:00.0 complete after 109.581 msecs
Nov 16 02:56:38 PC13 kernel: [   85.097550] serial 00:08: activated
Nov 16 02:56:38 PC13 kernel: [   85.098662] serial 00:09: activated
Nov 16 02:56:38 PC13 kernel: [   85.099850] parport_pc 00:0a: activated

...

Nov 16 02:56:38 PC13 kernel: [   85.815153] PM: resume of drv: dev:ep_00 complete after 771.916 msecs
Nov 16 02:56:38 PC13 kernel: [   85.815168] PM: resume of drv: dev:ep_81 complete after 772.029 msecs
Nov 16 02:56:38 PC13 kernel: [   86.056049] usb 2-2: reset low-speed USB device number 2 using uhci_hcd
Nov 16 02:56:38 PC13 kernel: [   86.363090] PM: resume of drv:usbhid dev:2-2:1.0 complete after 1269.129 msecs
Nov 16 02:56:38 PC13 kernel: [   86.363115] PM: resume of drv: dev:ep_00 complete after 1269.008 msecs
Nov 16 02:56:38 PC13 kernel: [   86.363131] PM: resume of drv: dev:ep_81 complete after 1269.041 msecs
Nov 16 02:56:38 PC13 kernel: [   86.890867] ACPI Error: Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.DRV0._GTF] (Node de426210), AE_AML_INFINITE_LOOP (20110623/psparse-536)
Nov 16 02:56:38 PC13 kernel: [   86.890907] ata1.00: _GTF evaluation failed (AE 0x3021)
Nov 16 02:56:38 PC13 kernel: [   87.052483] ata2.01: ACPI cmd ef/03:42:00:00:00:b0 (SET FEATURES) filtered out
Nov 16 02:56:38 PC13 kernel: [   87.052494] ata2.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
Nov 16 02:56:38 PC13 kernel: [   87.060317] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES) filtered out
Nov 16 02:56:38 PC13 kernel: [   87.060328] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
Nov 16 02:56:38 PC13 kernel: [   87.060339] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Nov 16 02:56:38 PC13 kernel: [   87.068188] ata2.00: configured for UDMA/33
Nov 16 02:56:38 PC13 kernel: [   87.076306] ata2.01: configured for UDMA/33
Nov 16 02:56:38 PC13 kernel: [   91.092170] ata1.00: configured for UDMA/100
Nov 16 02:56:38 PC13 kernel: [   91.108026] PM: resume of drv:sd dev:0:0:0:0 complete after 6095.602 msecs
Nov 16 02:56:38 PC13 kernel: [   91.108060] PM: resume of drv:scsi_device dev:0:0:0:0 complete after 6095.259 msecs
Nov 16 02:56:38 PC13 kernel: [   91.108078] PM: resume of drv:scsi_disk dev:0:0:0:0 complete after 6002.944 msecs
Nov 16 02:56:38 PC13 kernel: [   94.112010] 
Nov 16 02:56:38 PC13 kernel: [   94.112017] floppy driver state
Nov 16 02:56:38 PC13 kernel: [   94.112020] -------------------
Nov 16 02:56:38 PC13 kernel: [   94.112069] now=4294915824 last interrupt=4294892890 diff=22934 last called handler=reset_interrupt
Nov 16 02:56:38 PC13 kernel: [   94.112074] timeout_message=lock fdc
Nov 16 02:56:38 PC13 kernel: [   94.112078] last output bytes:
Nov 16 02:56:38 PC13 kernel: [   94.112083]  8 80 4294892885
Nov 16 02:56:38 PC13 kernel: [   94.112088]  8 80 4294892885
Nov 16 02:56:38 PC13 kernel: [   94.112092]  8 80 4294892885
Nov 16 02:56:38 PC13 kernel: [   94.112096]  8 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112101]  8 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112105]  8 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112109]  8 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112113]  e 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112118] 13 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112122]  0 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112126] 1a 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112130]  0 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112135] 12 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112139]  0 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112143] 14 90 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112147] 18 80 4294892889
Nov 16 02:56:38 PC13 kernel: [   94.112152]  8 80 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112156]  8 80 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112160]  8 80 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112164]  8 80 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112168] last result at 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112172] last redo_fd_request at 4294892890
Nov 16 02:56:38 PC13 kernel: [   94.112184] status=0
Nov 16 02:56:38 PC13 kernel: [   94.112187] fdc_busy=1
Nov 16 02:56:38 PC13 kernel: [   94.112197] do_floppy=reset_interrupt
Nov 16 02:56:38 PC13 kernel: [   94.112201] cont=e07ed290
Nov 16 02:56:38 PC13 kernel: [   94.112205] current_req=  (null)
Nov 16 02:56:38 PC13 kernel: [   94.112209] command_status=-1
Nov 16 02:56:38 PC13 kernel: [   94.112212] 
Nov 16 02:56:38 PC13 kernel: [   94.112218] floppy0: floppy timeout called
Nov 16 02:56:38 PC13 kernel: [   94.112251] PM: resume of drv:floppy dev:floppy.0 complete after 3004.128 msecs
Nov 16 02:56:38 PC13 kernel: [   94.112418] PM: resume of devices complete after 9128.352 msecs
Nov 16 02:56:38 PC13 kernel: [   94.112630] PM: resume devices took 9.128 seconds
Nov 16 02:56:38 PC13 kernel: [   94.112727] PM: Finishing wakeup.
Nov 16 02:56:38 PC13 kernel: [   94.112732] Restarting tasks ... done.
Nov 16 02:56:39 PC13 kernel: [   95.170528] show_signal_msg: 36 callbacks suppressed
Nov 16 02:56:39 PC13 kernel: [   95.170541] polkitd[707]: segfault at 1f7cfdc ip 00130467 sp bfa06db8 error 6 in libgio-2.0.so.0.3200.3[110000+153000]
Nov 16 02:56:41 PC13 kernel: [   97.360187] e100 0000:01:08.0: eth1: NIC Link is Up 100 Mbps Full Duplex
Nov 16 02:56:41 PC13 kernel: [   97.923682] nm-applet[1484]: segfault at 8 ip 00478406 sp bfd50c10 error 4 in libglib-2.0.so.0.3200.3[417000+f7000]
Nov 16 02:56:42 PC13 kernel: [   97.984948] gdbus[1558]: segfault at 75 ip 007b4de7 sp 007f840d error 4 in libgio-2.0.so.0.3200.3[78c000+153000]
Nov 16 02:56:51 PC13 kernel: [  107.568062] eth1: no IPv6 routers present
Nov 16 02:56:52 PC13 kernel: [  108.241154] BUG: unable to handle kernel NULL pointer dereference at   (null)
Nov 16 02:56:53 PC13 kernel: [  108.244024] IP: [<c112072f>] unlink_anon_vmas+0x3f/0x170
Nov 16 02:56:53 PC13 kernel: [  108.244024] *pdpt = 0000000012772001 *pde = 000000001e61e067 *pte = 0000000000000000 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Oops: 0000 [#1] SMP 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Modules linked in: vesafb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq radeon snd_timer snd_seq_device snd psmouse ttm drm_kms_helper serio_raw soundcore snd_page_alloc drm bnep rfcomm bluetooth parport_pc ppdev i2c_algo_bit binfmt_misc mac_hid shpchp lp parport usbhid e100 hid floppy
Nov 16 02:56:53 PC13 kernel: [  108.244024] 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Pid: 2462, comm: indicator-print Not tainted 3.2.0-33-generic-pae #52-Ubuntu                  /D815EEA2                       
Nov 16 02:56:53 PC13 kernel: [  108.244024] EIP: 0060:[<c112072f>] EFLAGS: 00210206 CPU: 0
Nov 16 02:56:53 PC13 kernel: [  108.244024] EIP is at unlink_anon_vmas+0x3f/0x170
Nov 16 02:56:53 PC13 kernel: [  108.244024] EAX: fffffff8 EBX: cc5e0084 ECX: 80aa009c EDX: cc5e008c
Nov 16 02:56:53 PC13 kernel: [  108.244024] ESI: fffffff8 EDI: 00000000 EBP: d2427e90 ESP: d2427e74
Nov 16 02:56:53 PC13 kernel: [  108.244024]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov 16 02:56:53 PC13 kernel: [  108.244024] Process indicator-print (pid: 2462, ti=d2426000 task=cf45b2c0 task.ti=d2426000)
Nov 16 02:56:53 PC13 kernel: [  108.244024] Stack:
Nov 16 02:56:53 PC13 kernel: [  108.244024]  dc1637a8 cc5eaa50 cc5eaa8c dc1637a8 cc5eaa50 cf67af78 00110000 d2427eb4
Nov 16 02:56:53 PC13 kernel: [  108.244024]  c1114e3a c12c491e 00000020 00000000 d2427ec8 cf467840 dbcd8960 bfb51000
Nov 16 02:56:53 PC13 kernel: [  108.244024]  d2427f14 c111d251 00000000 d2427f04 00000000 dbcd8960 d2427f03 00000001
Nov 16 02:56:53 PC13 kernel: [  108.244024] Call Trace:
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c1114e3a>] free_pgtables+0x7a/0xe0
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c12c491e>] ? __percpu_counter_add+0x7e/0xb0
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c111d251>] exit_mmap+0xb1/0x120
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c15a6efd>] ? _raw_spin_lock_irqsave+0x2d/0x40
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c10585c9>] mmput.part.21+0x39/0xf0
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c10586a2>] mmput+0x22/0x30
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c105e4e8>] exit_mm+0xe8/0x100
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c105e639>] do_exit+0x139/0x3c0
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c1053f9f>] ? wake_up_state+0xf/0x20
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c106bdc8>] ? signal_wake_up+0x28/0x40
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c105ea18>] do_group_exit+0x38/0xa0
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c105ea98>] sys_exit_group+0x18/0x20
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c15a70a4>] syscall_call+0x7/0xb
Nov 16 02:56:53 PC13 kernel: [  108.244024]  [<c15a0000>] ? net_generic.isra.14.part.15+0x2/0xa
Nov 16 02:56:53 PC13 kernel: [  108.244024] Code: 40 3c 83 c2 3c 89 55 ec 39 c2 8b 30 8d 58 f8 0f 84 fb 00 00 00 83 ee 08 c7 45 f0 00 00 00 00 eb 07 8d 76 00 89 f3 89 c6 8b 7b 04 <8b> 0f 39 4d f0 74 1c 8b 45 f0 85 c0 0f 85 db 00 00 00 8d 41 04 
Nov 16 02:56:53 PC13 kernel: [  108.244024] EIP: [<c112072f>] unlink_anon_vmas+0x3f/0x170 SS:ESP 0068:d2427e74
Nov 16 02:56:53 PC13 kernel: [  108.244024] CR2: 0000000000000000
Nov 16 02:56:53 PC13 kernel: [  108.667075] ---[ end trace 79ea307c9f554b3d ]---
Nov 16 02:56:53 PC13 kernel: [  108.667085] Fixing recursive fault but reboot is needed!
Nov 16 02:56:54 PC13 kernel: [  110.926147] compiz[2506] general protection ip:68b658 sp:bfeb7d40 error:0 in libccp.so[685000+13000]
Nov 16 02:56:56 PC13 kernel: [  112.001479] NetworkManager[697]: segfault at 0 ip 0082ac40 sp bfa5056c error 6 in libnl-route-3.so.200.3.0[820000+3f000]
Nov 16 02:56:57 PC13 kernel: [  113.477069] init: network-manager main process (697) killed by SEGV signal
Nov 16 02:56:57 PC13 kernel: [  113.477186] init: network-manager main process ended, respawning
Nov 16 02:56:58 PC13 kernel: [  114.855732] unity-panel-ser[2444]: segfault at 10 ip 0036fc18 sp bfacd6d0 error 4 in libgobject-2.0.so.0.3200.3[33f000+4d000]
Nov 16 02:57:14 PC13 kernel: [  130.176020] eth1: no IPv6 routers present
Nov 16 02:57:45 PC13 kernel: [  161.038063] gdbus[2110]: segfault at b7b3d060 ip 006dfde0 sp b733106c error 6 in libgio-2.0.so.0.3200.3[6b7000+153000]
Nov 16 02:57:45 PC13 kernel: [  161.038397] gdbus[1981]: segfault at b7be9060 ip 00748de0 sp b737406c error 6 in libgio-2.0.so.0.3200.3[720000+153000]
Nov 16 02:57:45 PC13 kernel: [  161.038562] gdbus[1681]: segfault at b85d4fa0 ip 00d15de0 sp b7792fac error 6 in libgio-2.0.so.0.3200.3[ced000+153000]
Nov 16 02:57:45 PC13 kernel: [  161.038741] gdbus[1669]: segfault at b843dfe0 ip 00b7dde0 sp b7793fec error 6 in libgio-2.0.so.0.3200.3[b55000+153000]
Nov 16 03:39:10 PC13 kernel: imklog 5.8.6, log source = /proc/kmsg started.
Nov 16 03:39:10 PC13 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov 16 03:39:10 PC13 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov 16 03:39:10 PC13 kernel: [    0.000000] Linux version 3.2.0-33-generic-pae (buildd@lamiak) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #52-Ubuntu SMP Thu Oct 18 16:39:21 UTC 2012 (Ubuntu 3.2.0-33.52-generic-pae 3.2.31)
Nov 16 03:39:10 PC13 kernel: [    0.000000] KERNEL supported cpus:
Nov 16 03:39:10 PC13 kernel: [    0.000000]   Intel GenuineIntel
Nov 16 03:39:10 PC13 kernel: [    0.000000]   AMD AuthenticAMD

...


I believe I put the computer to sleep at Nov 16 02:56:21, and woke it up at Nov 16 02:56:38.
At Nov 16 03:39:10, I finally pressed the reset button because I finished taking a picture of the crash screen.
I didn't have a digital camera ready at the time of the crash, and that's why it took 40 minutes (Plus I was doing other stuff at the same time.).
The kernel is not completely frozen because mouse cursor will still move, and if I don't move the mouse for more than 10 or so minutes, it will still turn the screen off.
I do notice that at Nov 16 02:56:38 PC13 kernel: [   86.890867] there is an ACPI error.


Nov 16 02:56:38 PC13 kernel: [   86.890867] ACPI Error: Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.DRV0._GTF] (Node de426210), AE_AML_INFINITE_LOOP (20110623/psparse-536)


It looks like there is something wrong with the PATA/IDE controller of the mainboard, not the graphics card.
While the hard drive I used here is fairly old, I don't believe it is unreliable as a hard drive.
Afterwards, the kernel will crash.


Nov 16 02:56:39 PC13 kernel: [   95.170541] polkitd[707]: segfault at 1f7cfdc ip 00130467 sp bfa06db8 error 6 in libgio-2.0.so.0.3200.3[110000+153000]
Nov 16 02:56:41 PC13 kernel: [   97.360187] e100 0000:01:08.0: eth1: NIC Link is Up 100 Mbps Full Duplex
Nov 16 02:56:41 PC13 kernel: [   97.923682] nm-applet[1484]: segfault at 8 ip 00478406 sp bfd50c10 error 4 in libglib-2.0.so.0.3200.3[417000+f7000]
Nov 16 02:56:42 PC13 kernel: [   97.984948] gdbus[1558]: segfault at 75 ip 007b4de7 sp 007f840d error 4 in libgio-2.0.so.0.3200.3[78c000+153000]
Nov 16 02:56:51 PC13 kernel: [  107.568062] eth1: no IPv6 routers present
Nov 16 02:56:52 PC13 kernel: [  108.241154] BUG: unable to handle kernel NULL pointer dereference at   (null)
Nov 16 02:56:53 PC13 kernel: [  108.244024] IP: [<c112072f>] unlink_anon_vmas+0x3f/0x170
Nov 16 02:56:53 PC13 kernel: [  108.244024] *pdpt = 0000000012772001 *pde = 000000001e61e067 *pte = 0000000000000000 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Oops: 0000 [#1] SMP 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Modules linked in: vesafb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq radeon snd_timer snd_seq_device snd psmouse ttm drm_kms_helper serio_raw soundcore snd_page_alloc drm bnep rfcomm bluetooth parport_pc ppdev i2c_algo_bit binfmt_misc mac_hid shpchp lp parport usbhid e100 hid floppy
Nov 16 02:56:53 PC13 kernel: [  108.244024] 
Nov 16 02:56:53 PC13 kernel: [  108.244024] Pid: 2462, comm: indicator-print Not tainted 3.2.0-33-generic-pae #52-Ubuntu                  /D815EEA2                       
Nov 16 02:56:53 PC13 kernel: [  108.244024] EIP: 0060:[<c112072f>] EFLAGS: 00210206 CPU: 0
Nov 16 02:56:53 PC13 kernel: [  108.244024] EIP is at unlink_anon_vmas+0x3f/0x170


Looking at the above error messages, I am wondering if this is actually an Intel ICH2 PATA/IDE related device driver bug.
I do have to admit that Radeon 9800 Pro does come out of ACPI S3 State very reliably with ASUS P4S8X-MX mainboard (SiS 661GX/964 chipset) on Ubuntu 12.04 LTS 32-bit.

Regards,

fpgahardwareengineer


> (In reply to comment #8)
> > Is it possible you can give me detailed instructions on how to do this?
> > I have gone to grub by pressing shift key during boot, and furthermore pressed
> > e key to edit the boot script.
> 
> That's correct.  Just append radeon.agpmode=-1 to the kernel line.
> 
> > I don't know how to make the change permanent from grub's simple editor.
> > How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP
> > mode?
> 
> To make it permanent, edit the /etc/grub2.cfg and manually make the change. 
> You can check the radeon dmesg messages to see whether the card is loaded in
> AGP or non-AGP mode.

Comment 21 mypersonalmailbox1 2012-11-16 12:24:07 UTC

Created attachment 70157 [details]
kern.log radeon.agpmode=-1 finally working

Comment 22 mypersonalmailbox1 2012-11-16 12:27:41 UTC

Hi,

I will attach a screen shot of the monitor when the crash has happened a little bit later.
I did attach kern.log which contains the identical crash error messages that was displayed on the screen.
Again, even after the crash, monitor did work and mouse cursor still works.

Regards,

fpgahardwareengineer

Comment 23 mypersonalmailbox1 2012-11-16 12:37:36 UTC

Hi,

Should I temporarily try to install Canonical compiled Linux 3.7-rc5 to the same hard drive that currently contains Ubuntu 12.04 LTS 32-bit?
I know that many upstream developers won't deal with bug reports unless it is tested with the latest kernel.
I personally don't like doing this because it tends to break ubuntu-bug command when I install the latest kernel (Breaking ubuntu-bug command in this case means that it won't upload a bug report to launchpad.net after I go back to the original kernel, and run ubuntu-bug command from the terminal or Alt-F2.).
If anybody can tell me how I can avoid breaking ubuntu-bug command after I go back to the older kernel (in this case, 3.2.0-x.generic.pae), I will appreciate.

Regards,

fpgahardwareengineer

Comment 24 mypersonalmailbox1 2012-12-22 11:39:09 UTC

HI,

Can someone from Radeon x.org display device driver team take a look at the kern.log?

Regards,

fpgahardwareengineer

Comment 25 mypersonalmailbox1 2013-02-14 01:59:18 UTC

Hi,

I have not commented on this bug for some time, but I will like to provide the final analysis so that it can be closed up for good.
After not seeing any crashes/freezes when I used Toshiba 256 MB SDRAM modules (Toshiba module with Toshiba DRAM devices), I tried playing around with different combinations of the original 2 (two) 128 MB SDRAM modules and 1 (one) 256 MB SDRAM module.
It turns out one of the no brand 128 MB SDRAM module with Mosel Vitelic DRAM devices seems to cause crashes/freezes when I put the computer into ACPI S3 State and wake it up.
It appears that the self refresh mode of this 128 MB SDRAM module with Mosel Vitelic DRAM device causes memory content corruption, and this leads Ubuntu to freeze/crash at some point (i.e., After putting the computer in and out of ACPI S3 State so many times.).
Just for the record, the marking of the DRAM device says V54C3128804VAT7 with a date code 0213 (13th week of 2002).
I assume I just got a bad memory module.
I didn't notice this until now, and insisted that memtest86+ didn't catch any memory read/write error, but if I think about it, memtest86+ is powerless as a tool against this type of a failure is because it doesn't have the means to put the memory into self refresh mode and bring it out to check the content of the memory array.
While this case is specific to SDRAM, this type of failure can occur on any DRAM type since SDRAM because all of them now have self refresh mode.
So if there is anyone reading this analysis, remember that the memory array can get corrupted if for some reason self refresh mode no longer works correctly (i.e., due to aging), and this can lead to seemingly random crashes/freezes after waking the computer up from ACPI S3 State.
Since this bug was a deteriorating hardware issue, I will close the case as a resolved case.

Regards,

fpgahardwareengineer

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.