You are not logged in.

#1 2010-01-12 20:06:59

adrians
Member
From: Latvia
Registered: 2009-05-05
Posts: 16
Website

Unable to handle kernel paging request -- hardware problem?

I have experienced random system freezes for some time on my home computer with different Linux systems. These crashes are rather a rare thing but last two or three days it happens every day so I am finally posting this problem here. I know nothing really about kernel logs but it looks for me like video card problem.

I have NVIDIA 8600GT video card. Runs with proprietary NVIDIA driver.

I have to note that system has crashed also with no proprietary NVIDIA driver -- once I had a crash (system freeze) installing Fedora with GUI installer, same has happened with Ubuntu. Though maybe these problems are not related.

So could it be that my video card is broken?

kernel.log

Jan 12 21:08:34 barch kernel: BUG: unable to handle kernel paging request at 7f45402d
Jan 12 21:08:34 barch kernel: IP: [<f931a2e3>] _nv005990rm+0x4/0x7 [nvidia]
Jan 12 21:08:34 barch kernel: *pde = 00000000 
Jan 12 21:08:34 barch kernel: Oops: 0000 [#1] PREEMPT SMP 
Jan 12 21:08:34 barch kernel: last sysfs file: /sys/devices/system/cpu/cpu1/online
Jan 12 21:08:34 barch kernel: Modules linked in: vboxdrv ipv6 fuse joydev usbhid hid wacom arc4 ecb rtl8187 mac80211 led_class cfg80211 rfkill eeprom_93cx6 snd_hda_codec_analog snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_hda_intel snd_hda_codec snd_seq_device snd_pcm_oss snd_hwdep snd_mixer_oss snd_pcm snd_timer nvidia(P) snd i2c_viapro soundcore uhci_hcd via_agp r8169 ppdev ehci_hcd shpchp snd_page_alloc parport_pc psmouse agpgart asus_atk0110 mii i2c_core fan pci_hotplug usbcore serio_raw evdev thermal processor pcspkr button lp parport sg battery ac rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod cdrom sd_mod sata_via ahci pata_jmicron pata_via ata_generic pata_acpi floppy libata scsi_mod
Jan 12 21:08:34 barch kernel: 
Jan 12 21:08:34 barch kernel: Pid: 2034, comm: X Tainted: P           (2.6.32-ARCH #1) System Product Name
Jan 12 21:08:34 barch kernel: EIP: 0060:[<f931a2e3>] EFLAGS: 00013202 CPU: 0
Jan 12 21:08:34 barch kernel: EIP is at _nv005990rm+0x4/0x7 [nvidia]
Jan 12 21:08:34 barch kernel: EAX: 7f45402d EBX: 7f45402d ECX: 00000001 EDX: 00000000
Jan 12 21:08:34 barch kernel: ESI: 00000000 EDI: 7f454025 EBP: f7077d78 ESP: f6441d9c
Jan 12 21:08:34 barch kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 12 21:08:34 barch kernel: Process X (pid: 2034, ti=f6440000 task=f6becb60 task.ti=f6440000)
Jan 12 21:08:34 barch kernel: Stack:
Jan 12 21:08:34 barch kernel: f931a0e1 7f45402d 7f454025 00000000 f6660000 f931a11c 7f454025 00000009
Jan 12 21:08:34 barch kernel: <0> 00000001 00000000 f6660000 00000000 f6043000 f931a11c f6660000 00000009
Jan 12 21:08:34 barch kernel: <0> 00000001 00000000 00000009 f63cc000 00000009 f931a1a8 f6043000 00000009
Jan 12 21:08:34 barch kernel: Call Trace:
Jan 12 21:08:34 barch kernel: [<f931a0e1>] ? _nv005987rm+0x15/0x70 [nvidia]
Jan 12 21:08:34 barch kernel: [<f931a11c>] ? _nv005987rm+0x50/0x70 [nvidia]
Jan 12 21:08:34 barch kernel: [<f931a11c>] ? _nv005987rm+0x50/0x70 [nvidia]
Jan 12 21:08:34 barch kernel: [<f931a1a8>] ? _nv005985rm+0x2f/0x4a [nvidia]
Jan 12 21:08:34 barch kernel: [<f92d9404>] ? _nv014970rm+0x59/0x190 [nvidia]
Jan 12 21:08:34 barch kernel: [<f92bd2bc>] ? _nv003670rm+0x105/0x26dc [nvidia]
Jan 12 21:08:34 barch kernel: [<f92b53ab>] ? _nv007308rm+0x5a/0xf0 [nvidia]
Jan 12 21:08:34 barch kernel: [<f90dd04b>] ? _nv003830rm+0x1c7/0x541 [nvidia]
Jan 12 21:08:34 barch kernel: [<f9336973>] ? rm_ioctl+0x3e/0x6d [nvidia]
Jan 12 21:08:34 barch kernel: [<f940457a>] ? nv_kern_ioctl+0x13a/0x490 [nvidia]
Jan 12 21:08:34 barch kernel: [<c10e35d5>] ? do_sync_read+0xd5/0x120
Jan 12 21:08:34 barch kernel: [<c105e1f7>] ? enqueue_hrtimer+0x67/0xd0
Jan 12 21:08:34 barch kernel: [<f9404908>] ? nv_kern_unlocked_ioctl+0x18/0x20 [nvidia]
Jan 12 21:08:34 barch kernel: [<f94048f0>] ? nv_kern_unlocked_ioctl+0x0/0x20 [nvidia]
Jan 12 21:08:34 barch kernel: [<c10f15db>] ? vfs_ioctl+0x1b/0xa0
Jan 12 21:08:34 barch kernel: [<c10f17c9>] ? do_vfs_ioctl+0x79/0x5c0
Jan 12 21:08:34 barch kernel: [<c10e3686>] ? rw_verify_area+0x66/0xe0
Jan 12 21:08:34 barch kernel: [<c10e438e>] ? vfs_read+0x11e/0x190
Jan 12 21:08:34 barch kernel: [<c10f1d86>] ? sys_ioctl+0x76/0x90
Jan 12 21:08:34 barch kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Jan 12 21:08:34 barch kernel: Code: 83 c4 04 89 c6 8b 44 24 10 ff 70 5c 6a 01 8b 44 24 1c ff 34 98 56 e8 64 3b 02 00 83 c4 10 43 39 fb 72 e2 5b 5e 5f c3 8b 44 24 04 <8b> 00 c3 8b 44 24 04 83 c0 08 50 e8 ec ff ff ff 83 c4 04 c3 8b 
Jan 12 21:08:34 barch kernel: EIP: [<f931a2e3>] _nv005990rm+0x4/0x7 [nvidia] SS:ESP 0068:f6441d9c
Jan 12 21:08:34 barch kernel: CR2: 000000007f45402d
Jan 12 21:08:34 barch kernel: ---[ end trace 9971709b053ec152 ]---

Last edited by adrians (2010-01-12 20:13:58)

Offline

#2 2010-04-05 12:34:12

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

I am experiencing the same problem. Did you figure out your problem? I do not have the same video driver as you. So, I do not think that it is a video driver problem.

Well, basically, the problem seems to be that the kernel chokes on some kind of paging request. Now, I know that page faults happen when the virtual memory exceeds the physical memory. But, is there any reason that the kernel would not be able to handle some kind of paging request?

I want to learn why this could be happening because this seems to be a persistent problem with my machine. And I do not think that any particular service is causing this error. I think that I will start to keep my own collection of these logs so that I can try to find some commonality among them.

Last edited by mgangav (2010-04-05 12:57:41)

Offline

#3 2010-04-06 16:59:02

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

Ok, I got a page fault today here are the logs:

Apr  6 12:25:51 Treadstone kernel: BUG: unable to handle kernel paging request at f76fe000
Apr  6 12:25:51 Treadstone kernel: IP: [<c10b4967>] get_page_from_freelist+0x277/0x550
Apr  6 12:25:51 Treadstone kernel: *pde = 00007067 *pte = 399ee700 
Apr  6 12:25:51 Treadstone kernel: Oops: 0002 [#1] PREEMPT SMP 
Apr  6 12:25:51 Treadstone kernel: last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C0A:00/power_supply/BAT1/charge_full
Apr  6 12:25:51 Treadstone kernel: Modules linked in: iwl3945 iwlcore mac80211 cfg80211 ndiswrapper ipv6 ext2 snd_hda_codec_realtek snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_hda_intel snd_seq snd_seq_device snd_hda_codec arc4 snd_hwdep i915 snd_pcm_oss ecb uvcvideo snd_pcm vboxnetflt snd_mixer_oss b44 drm_kms_helper snd_timer videodev yenta_socket vboxdrv ssb iTCO_wdt rsrc_nonstatic v4l1_compat drm snd sdhci_pci pcmcia joydev iTCO_vendor_support uhci_hcd intel_agp i2c_algo_bit sdhci ehci_hcd i2c_i801 soundcore container fuse mii pcmcia_core battery mmc_core usbcore ac sg snd_page_alloc agpgart i2c_core acer_wmi button video output rfkill pcspkr led_class wmi psmouse serio_raw evdev thermal processor rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod sd_mod cdrom pata_acpi ata_piix ata_generic libata scsi_mod [last unloaded: cfg80211]
Apr  6 12:25:51 Treadstone kernel: 
Apr  6 12:25:51 Treadstone kernel: Pid: 3989, comm: firefox Tainted: P           (2.6.32-ARCH #1) TravelMate 4230 
Apr  6 12:25:51 Treadstone kernel: EIP: 0060:[<c10b4967>] EFLAGS: 00010246 CPU: 1
Apr  6 12:25:51 Treadstone kernel: EIP is at get_page_from_freelist+0x277/0x550
Apr  6 12:25:51 Treadstone kernel: EAX: 00000000 EBX: f76fe000 ECX: 00000400 EDX: 00000003
Apr  6 12:25:51 Treadstone kernel: ESI: 00000000 EDI: f76fe000 EBP: c1c25fc0 ESP: f2403e50
Apr  6 12:25:51 Treadstone kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr  6 12:25:51 Treadstone kernel: Process firefox (pid: 3989, ti=f2402000 task=f2a229e0 task.ti=f2402000)

One thing that is apparent is that both me and and the above user might have been running virtual box at the time because we both have the modules specific to virtual box loaded.

Last edited by mgangav (2010-04-06 17:01:30)

Offline

#4 2010-04-06 17:50:17

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: Unable to handle kernel paging request -- hardware problem?

I would first run memtest and make sure that you ram is ok. Let this run over night. Then if the problem still persists you might want to post on the kernel bug tracker and see what they tell you.


Website - Blog - arch-home
Arch User since March 2005

Offline

#5 2010-04-08 09:55:13

adrians
Member
From: Latvia
Registered: 2009-05-05
Posts: 16
Website

Re: Unable to handle kernel paging request -- hardware problem?

I didn't solve the problem. Though I am sure it was hardware related.

I thought it was graphic card so I bought a new one. The new card didn't work altogether. The card was fine but didn't work with other parts (motherboard) – strange. After some other wrong guesses smile, I bought a new computer. It was time for new anyway. Since then no problems running Archlinux.

I didn't try memtest. Maybe it was RAM. But I would say it was motherboard (could be wrong as other guesses smile). I had some minor problems also with USB ports – randomly loosing connection with some ports.

Offline

#6 2010-04-09 01:21:03

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

Hey guys, I've been collecting logs for the few times that the computer has crashed. The reason is always of the format:

Treadstone kernel: BUG: unable to handle kernel paging request at f7*****
Treadstone kernel: IP: [<c10b4967>] get_page_from_freelist+0x277/0x550
Apr  7 17:24:57 Treadstone kernel: *pde = 00007067 *pte = 60000c00 
Apr  7 17:24:57 Treadstone kernel: Oops: 0002 [#1] PREEMPT SMP
Apr  7 17:24:57 Treadstone kernel: last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C0A:00/power_supply/BAT1/charge_full
Apr  7 17:24:57 Treadstone kernel: Modules linked in: iwl3945 iwlcore mac80211 cfg80211 ndiswrapper ipv6 ext2 snd_hda_codec_realtek snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_hda_intel snd_seq arc4 snd_seq_device snd_hda_codec snd_pcm_oss snd_hwdep ecb uvcvideo snd_mixer_oss snd_pcm videodev v4l1_compat b44 i915 snd_timer ssb drm_kms_helper yenta_socket snd pcmcia intel_agp rsrc_nonstatic drm soundcore sdhci_pci iTCO_wdt i2c_algo_bit i2c_i801 iTCO_vendor_support sdhci uhci_hcd joydev snd_page_alloc pcmcia_core mmc_core mii ehci_hcd agpgart evdev ac container i2c_core processor video battery acer_wmi pcspkr vboxnetflt button usbcore thermal rfkill output led_class wmi psmouse serio_raw sg vboxdrv fuse rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod sd_mod cdrom pata_acpi ata_piix ata_generic libata scsi_mod [last unloaded: cfg80211]
Apr  7 17:24:57 Treadstone kernel: 
Apr  7 17:24:57 Treadstone kernel: Pid: 2285, comm: firefox Tainted: P

It is always because of a different application, but the invalid paging request bug always occurs about the same memory address. What does this mean? I would run memtest, but how do I start it up before starting the operating system? Or this a normal application.

Note, there is no article on the arch wiki about memtest. I already have it installed on my system, but there is no man page for it.

I will keep searching the interwebz, but arch - specific pointers would be helpful.

Adrians, are you experiencing paging failures about the same address as well?

Offline

#7 2010-04-09 08:04:07

adrians
Member
From: Latvia
Registered: 2009-05-05
Posts: 16
Website

Re: Unable to handle kernel paging request -- hardware problem?

You can run memtest from Archlinux install CD.

All logs I have now about crashes is only previously posted kernel.log.

Offline

#8 2010-04-14 10:35:50

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

Well, I ran extensive memtests on my RAM, they came out clean. What could the problem be?

Could it be the hard disk?

Offline

#9 2010-04-14 14:13:49

Ber
Member
From: Belgium
Registered: 2006-07-05
Posts: 80
Website

Re: Unable to handle kernel paging request -- hardware problem?

What happens is that a driver (or any other kernel-space process) is trying to access virtual address 0xf7******, but this address cannot be translated by the VM to a valid physical address (because it's a user-space virtual address, not a kernel virtual address,  for example).  So I'd say there's no hardware problem, you probably don't need to buy a new computer :-)

As to say where it comes from... Can be a lot of things.  Maybe try a older/newer kernel compiled from source.


V=RI sweet V=RI

Offline

#10 2010-04-15 13:21:18

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

Ber wrote:

What happens is that a driver (or any other kernel-space process) is trying to access virtual address 0xf7******, but this address cannot be translated by the VM to a valid physical address (because it's a user-space virtual address, not a kernel virtual address,  for example).  So I'd say there's no hardware problem, you probably don't need to buy a new computer :-)

As to say where it comes from... Can be a lot of things.  Maybe try a older/newer kernel compiled from source.

Man, this is frustrating, but you know what is weird? I haven't had even one of those errors ever since I ran the memtests... Weird right? I will have to monitor my system for a few days to see how stable it is.

Offline

#11 2010-04-30 18:31:28

mgangav
Member
Registered: 2009-04-18
Posts: 21

Re: Unable to handle kernel paging request -- hardware problem?

Yep, I think that after I reseated my Memory Chips, the problem has been solved:

14:31:31 up 5 days, 16:00,  4 users,  load average: 0.20, 0.61, 0.38

Offline

#12 2010-05-03 07:48:19

Ber
Member
From: Belgium
Registered: 2006-07-05
Posts: 80
Website

Re: Unable to handle kernel paging request -- hardware problem?

Well good news then!  As I said, it can ba many different things, so why not a hardware problem messing with your memory management system...

Don't forget to mark it as solved


V=RI sweet V=RI

Offline

#13 2010-10-30 19:50:31

Dave Cohen
Member
Registered: 2008-09-27
Posts: 126

Re: Unable to handle kernel paging request -- hardware problem?

Doesn't sound solved to me.  I've noticed a similar/same problem on my computer. Started several weeks ago (maybe right after the multilib change).  Happens intermittently, maybe every 2-3 days.

I'm posting my error while I have it in front of me, will try the memtest next.

BUG: unable to handle kernel paging request at ffffc90000430000
IP: [<ffffffff811d91fb>] memcpy+0xb/0xb0
PGD 7f816067 PUD 7f817067 PMD 7c26a067 PTE 0
Oops: 0002 [#1] PREEMPT SMP 
last sysfs file: /sys/devices/platform/it87.3328/temp1_input
CPU 0 
Modules linked in: ipv6 it87 hwmon_vid radeon ttm drm_kms_helper rtc_cmos rtc_core snd_mpu401 snd_mpu401_uart drm rtc_lib snd_usb_audio parport_pc snd_intel8x0 ns558 i2c_algo_bit snd_hwdep snd_usbmidi_lib firewire_ohci snd_ac97_codec ac97_bus snd_rawmidi firewire_core crc_itu_t snd_seq_device snd_pcm snd_timer snd snd_page_alloc soundcore uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 thermal processor button usb_storage i2c_nforce2 shpchp i2c_core edac_core pci_hotplug edac_mce_amd ppdev analog gameport forcedeth lp parport k8temp sg pcspkr evdev fuse usbhid hid ext3 jbd mbcache floppy ohci_hcd ehci_hcd usbcore raid1 md_mod dm_mod sata_sil sr_mod cdrom sata_nv ata_generic sd_mod pata_amd pata_acpi libata scsi_mod

Pid: 3400, comm: X Tainted: G        W   2.6.35-ARCH #1 'K8N-E-Deluxe'/K8N-E-Deluxe
RIP: 0010:[<ffffffff811d91fb>]  [<ffffffff811d91fb>] memcpy+0xb/0xb0
RSP: 0018:ffff88006ecd1b20  EFLAGS: 00010246
RAX: ffffc90000430000 RBX: ffff88001eca6200 RCX: 0000000000000200
RDX: 0000000000000000 RSI: ffff88000006d000 RDI: ffffc90000430000
RBP: ffff88006ecd1b78 R08: 0000000000000006 R09: 0000000000000001
R10: ffffffffa05d6da8 R11: 0000000000000002 R12: ffff88006ecd1c88
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000
FS:  00007f56057d1840(0000) GS:ffff880001800000(0000) knlGS:00000000f699c800
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000430000 CR3: 000000006ec9b000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process X (pid: 3400, threadinfo ffff88006ecd0000, task ffff88007c3e7780)
Stack:
 ffffffffa05cb46b ffff88006400648c 0000000000000003 0000000000001000
<0> 0000000000000001 ffff88007bdcee50 0000000000000000 ffff88006ecd1c18
<0> ffff88006ecd1c88 ffff88001eca6200 0000000000000000 ffff88006ecd1bb8
Call Trace:
 [<ffffffffa05cb46b>] ? radeon_cs_update_pages+0xfb/0x130 [radeon]
 [<ffffffffa05d1756>] r100_cs_packet_parse+0x76/0x210 [radeon]
 [<ffffffffa05d6de1>] r100_cs_parse+0x61/0x1180 [radeon]
 [<ffffffffa05cac86>] ? radeon_cs_parser_relocs+0x236/0x270 [radeon]
 [<ffffffffa05cb2a4>] radeon_cs_ioctl+0x114/0x1e0 [radeon]
 [<ffffffffa04c4aec>] drm_ioctl+0x41c/0x4e0 [drm]
 [<ffffffffa05cb190>] ? radeon_cs_ioctl+0x0/0x1e0 [radeon]
 [<ffffffff811239a2>] ? do_sync_read+0xd2/0x110
 [<ffffffff81074de6>] ? enqueue_hrtimer+0x86/0x100
 [<ffffffff81133c2c>] vfs_ioctl+0x3c/0xd0
 [<ffffffff8113422c>] do_vfs_ioctl+0x7c/0x520
 [<ffffffff811241bd>] ? vfs_read+0x12d/0x190
 [<ffffffff81134751>] sys_ioctl+0x81/0xa0
 [<ffffffff8100c179>] ? do_device_not_available+0x9/0x10
 [<ffffffff81009e82>] system_call_fastpath+0x16/0x1b
Code: 43 4e 48 83 c4 08 5b c9 c3 0f 1f 80 00 00 00 00 e8 0b fd ff ff eb e1 90 90 90 90 90 90 90 90 90 48 89 f8 89 d1 c1 e9 03 83 e2 07 <f3> 48 a5 89 d1 f3 a4 c3 8b 1e 4c 8b 46 08 4c 89 1f 4c 89 47 08 
RIP  [<ffffffff811d91fb>] memcpy+0xb/0xb0
 RSP <ffff88006ecd1b20>
CR2: ffffc90000430000
---[ end trace 24c2ebb17fa3af26 ]---
[drm:drm_release] *ERROR* Device busy: 1

Also, right before this error in dmesg, I see these messages repeated over and over and over...

[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(5).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(7).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(8).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(9).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(10).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(13).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(14).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
[drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15).
[drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

Offline

#14 2010-11-01 17:47:37

Dave Cohen
Member
Registered: 2008-09-27
Posts: 126

Re: Unable to handle kernel paging request -- hardware problem?

Follow up.  I ran the memtest, it reported no problems.

Rebooted the computer and had no problem until today.  Now I get a different error.  So I suspect a software bug that causes the paging request error above, and also this one...

------------[ cut here ]------------
WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x376/0x3e0 [radeon]()
Hardware name: K8N-E-Deluxe
GPU lockup (waiting for 0x001DBFE7 last fence id 0x001DBFE6)
Modules linked in: usb_storage ipv6 it87 hwmon_vid radeon ttm rtc_cmos drm_kms_helper snd_mpu401 snd_mpu401_uart parport_pc rtc_core rtc_lib ns558 drm i2c_algo_bit snd_intel8x0 ppdev snd_usb_audio snd_hwdep snd_usbmidi_lib firewire_ohci snd_ac97_codec ac97_bus snd_rawmidi snd_seq_device firewire_core crc_itu_t snd_pcm thermal processor snd_timer button uvcvideo snd soundcore snd_page_alloc videodev v4l1_compat v4l2_compat_ioctl32 i2c_nforce2 lp i2c_core edac_core parport shpchp edac_mce_amd analog pci_hotplug sg gameport evdev forcedeth pcspkr k8temp fuse ext3 jbd usbhid mbcache hid floppy ohci_hcd ehci_hcd usbcore raid1 md_mod dm_mod sata_sil sr_mod cdrom sata_nv ata_generic sd_mod pata_amd pata_acpi libata scsi_mod
Pid: 3242, comm: X Not tainted 2.6.35-ARCH #1
Call Trace:
 [<ffffffff810528ba>] warn_slowpath_common+0x7a/0xb0
 [<ffffffff81052991>] warn_slowpath_fmt+0x41/0x50
 [<ffffffffa0580f86>] radeon_fence_wait+0x376/0x3e0 [radeon]
 [<ffffffffa0599e31>] ? radeon_cs_parser_init+0x171/0x420 [radeon]
 [<ffffffff810719b0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffffa05988fb>] radeon_ib_get+0x12b/0x250 [radeon]
 [<ffffffffa059a219>] radeon_cs_ioctl+0x89/0x1e0 [radeon]
 [<ffffffffa04b7aec>] drm_ioctl+0x41c/0x4e0 [drm]
 [<ffffffffa059a190>] ? radeon_cs_ioctl+0x0/0x1e0 [radeon]
 [<ffffffff811239a2>] ? do_sync_read+0xd2/0x110
 [<ffffffff81133c2c>] vfs_ioctl+0x3c/0xd0
 [<ffffffff8113422c>] do_vfs_ioctl+0x7c/0x520
 [<ffffffff811a2821>] ? security_file_permission+0x11/0x20
 [<ffffffff81124208>] ? vfs_read+0x178/0x190
 [<ffffffff81134751>] sys_ioctl+0x81/0xa0
 [<ffffffff81009e82>] system_call_fastpath+0x16/0x1b
---[ end trace 1c331266077df6b6 ]---

I look forward to any suggestions, thanks.

Offline

#15 2010-11-01 18:14:08

andr3as
Member
Registered: 2008-10-06
Posts: 51

Re: Unable to handle kernel paging request -- hardware problem?

Dave, I started experiencing a similar crash after upgrading to kernel 2.6.36. About every third boot aborts with a radeon related kernel panic, but a reboot (or two) always solved the problem temporarily.
Did you have the problem w/ kernel 2.6.35? With that kernel, things worked fine here.

Offline

#16 2010-11-01 18:21:56

Dave Cohen
Member
Registered: 2008-09-27
Posts: 126

Re: Unable to handle kernel paging request -- hardware problem?

I am still on 2.6.35.  I just did a pacman -Syu.

[dave@starbuck ~]$ uname -a
Linux starbuck 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 21:22:26 CEST 2010 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

Offline

#17 2010-11-10 02:04:50

Dave Cohen
Member
Registered: 2008-09-27
Posts: 126

Re: Unable to handle kernel paging request -- hardware problem?

The problem, or something similar, happened to me again today. Found a thread that suggested booting with

nohz=off

option.  So I'm trying that now.  Won't know for sure whether it helps.

Related reading:
https://bugs.launchpad.net/ubuntu/+sour … bug/586243
http://www.phoronix.com/scan.php?page=a … =651&num=1

Offline

#18 2011-03-28 11:46:02

FrankUndFrei
Member
From: Berlin
Registered: 2011-03-28
Posts: 4

Re: Unable to handle kernel paging request -- hardware problem?

I guess there is still no real solution to this problem, is there?
I am experiencing the same problem on my computer with an up-to-date Arch64 installation.

First of all, how do I activate kernel.log? My /var/log/kernel.log is an empty file.
I took screenshots instead...
http://db.tt/u35CNW2
http://db.tt/I5f9RmC
And the second freeze today:
http://db.tt/98PfSOl

The freeze is always related to "kworker" (happend about 10 times in the last week.

@Dave Cohen: Did the "nohz=off" option help? How do activate it?

Offline

#19 2011-03-28 19:03:02

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,110
Website

Re: Unable to handle kernel paging request -- hardware problem?

FrankUndFrei wrote:

I guess there is still no real solution to this problem, is there?
I am experiencing the same problem on my computer with an up-to-date Arch64 installation.

First of all, how do I activate kernel.log? My /var/log/kernel.log is an empty file.
I took screenshots instead...
http://db.tt/u35CNW2
http://db.tt/I5f9RmC
And the second freeze today:
http://db.tt/98PfSOl

The freeze is always related to "kworker" (happend about 10 times in the last week.

@Dave Cohen: Did the "nohz=off" option help? How do activate it?

This thread is a year old and related to proprietary binary graphics drivers throwing kernel panics. Your kernel panic is related your a network driver.

Offline

#20 2011-03-29 11:01:09

FrankUndFrei
Member
From: Berlin
Registered: 2011-03-28
Posts: 4

Re: Unable to handle kernel paging request -- hardware problem?

Ok, sorry. I thought the problems were related and it would be easier if all the info was in one place.
Opened a new thread here: https://bbs.archlinux.org/viewtopic.php?id=115898

Offline

#21 2011-07-15 20:33:41

longint
Member
Registered: 2011-06-15
Posts: 28

Re: Unable to handle kernel paging request -- hardware problem?

I might have a similar issue described in here: https://bbs.archlinux.org/viewtopic.php?id=122617

Any help or ideas? Started also suddenly, will try the memtest workaround...

Offline

#22 2011-07-16 19:17:24

longint
Member
Registered: 2011-06-15
Posts: 28

Re: Unable to handle kernel paging request -- hardware problem?

Please guys, could someone give me a hint? I tried to run memtest several times without any errors but no succes in preventing my machine from crashing. When we talk about memtest we are speaking about memtest86+?

This is my kernel message:

Jul 15 17:53:46 toral kernel: [  509.790018] BUG: unable to handle kernel paging request at ffffc9001153d000
Jul 15 17:53:46 toral kernel: [  509.790024] IP: [<ffffffff8121fb0b>] memcpy+0xb/0x120
Jul 15 17:53:46 toral kernel: [  509.790032] PGD 137020067 PUD 137021067 PMD 12a687067 PTE 0
Jul 15 17:53:46 toral kernel: [  509.790035] Oops: 0002 [#1] PREEMPT SMP 
Jul 15 17:53:46 toral kernel: [  509.790038] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/status
Jul 15 17:53:46 toral kernel: [  509.790041] CPU 1 
Jul 15 17:53:46 toral kernel: [  509.790042] Modules linked in: fpu aesni_intel cryptd aes_x86_64 aes_generic xts gf128mul dm_crypt dm_mod loop acpi_cpufreq freq_table mperf joydev snd_hda_codec_hdmi nvidia(P) snd_hda_codec_conexant qcserial usbhid snd_pcm_oss usb_wwan snd_mixer_oss hid btusb usbserial snd_hda_intel bluetooth arc4 ecb crc16 snd_hda_codec snd_hwdep snd_pcm iwlagn sdhci_pci snd_timer sdhci thinkpad_acpi serio_raw mac80211 iTCO_wdt evdev psmouse pcspkr i2c_i801 snd battery sg nvram intel_agp ac mmc_core iTCO_vendor_support cfg80211 soundcore video intel_gtt intel_ips snd_page_alloc i2c_core wmi thermal rfkill button processor e1000e btrfs zlib_deflate crc32c libcrc32c ext2 mbcache ehci_hcd usbcore sr_mod cdrom sd_mod ahci libahci libata scsi_mod
Jul 15 17:53:46 toral kernel: [  509.790082] 
Jul 15 17:53:46 toral kernel: [  509.790085] Pid: 1668, comm: btrfs-endio-1 Tainted: P            2.6.39-ARCH #1 LENOVO 25223FG/25223FG
Jul 15 17:53:46 toral kernel: [  509.790088] RIP: 0010:[<ffffffff8121fb0b>]  [<ffffffff8121fb0b>] memcpy+0xb/0x120
Jul 15 17:53:46 toral kernel: [  509.790090] RSP: 0018:ffff880103793c58  EFLAGS: 00010246
Jul 15 17:53:46 toral kernel: [  509.790092] RAX: ffffc9001153cff8 RBX: 0000000000001000 RCX: 00000000000001ff
Jul 15 17:53:46 toral kernel: [  509.790093] RDX: 0000000000000000 RSI: ffff8800b1d6c008 RDI: ffffc9001153d000
Jul 15 17:53:46 toral kernel: [  509.790095] RBP: ffff880103793d30 R08: 000000006fb3eeb1 R09: ffffc9001153b000
Jul 15 17:53:46 toral kernel: [  509.790096] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
Jul 15 17:53:46 toral kernel: [  509.790098] R13: ffff880129b16b58 R14: 000000006fb40ea9 R15: 000000006fb40eb1
Jul 15 17:53:46 toral kernel: [  509.790100] FS:  0000000000000000(0000) GS:ffff880137c80000(0000) knlGS:0000000000000000
Jul 15 17:53:46 toral kernel: [  509.790101] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul 15 17:53:46 toral kernel: [  509.790103] CR2: ffffc9001153d000 CR3: 0000000001693000 CR4: 00000000000006e0
Jul 15 17:53:46 toral kernel: [  509.790104] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 15 17:53:46 toral kernel: [  509.790106] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jul 15 17:53:46 toral kernel: [  509.790107] Process btrfs-endio-1 (pid: 1668, threadinfo ffff880103792000, task ffff88013167d4c0)
Jul 15 17:53:46 toral kernel: [  509.790109] Stack:
Jul 15 17:53:46 toral kernel: [  509.790110]  ffffffffa014f84b ffff880103793cb0 ffffffffa013316b ffff880103793fd8
Jul 15 17:53:46 toral kernel: [  509.790113]  000000006fb3eeb1 ffffc9001153b000 0000000000001000 0000000000000000
Jul 15 17:53:46 toral kernel: [  509.790115]  ffff88012f8bc780 0000000000000002 00000020a014ff66 ffff8800b1f9e000
Jul 15 17:53:46 toral kernel: [  509.790118] Call Trace:
Jul 15 17:53:46 toral kernel: [  509.790131]  [<ffffffffa014f84b>] ? lzo_decompress_biovec+0x27b/0x2f0 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790139]  [<ffffffffa013316b>] ? clear_state_bit+0xfb/0x170 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790145]  [<ffffffffa0150f58>] btrfs_decompress_biovec+0x68/0xa0 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790151]  [<ffffffffa01510ed>] end_compressed_bio_read+0x15d/0x240 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790158]  [<ffffffffa010d14b>] ? end_workqueue_fn+0x4b/0x140 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790163]  [<ffffffff8118392d>] bio_endio+0x1d/0x40
Jul 15 17:53:46 toral kernel: [  509.790169]  [<ffffffffa010d156>] end_workqueue_fn+0x56/0x140 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790176]  [<ffffffffa0140d25>] worker_loop+0x165/0x520 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790182]  [<ffffffffa0140bc0>] ? btrfs_queue_worker+0x2f0/0x2f0 [btrfs]
Jul 15 17:53:46 toral kernel: [  509.790187]  [<ffffffff8107d6ec>] kthread+0x8c/0xa0
Jul 15 17:53:46 toral kernel: [  509.790190]  [<ffffffff813e9fe4>] kernel_thread_helper+0x4/0x10
Jul 15 17:53:46 toral kernel: [  509.790192]  [<ffffffff8107d660>] ? kthread_worker_fn+0x190/0x190
Jul 15 17:53:46 toral kernel: [  509.790194]  [<ffffffff813e9fe0>] ? gs_change+0x13/0x13
Jul 15 17:53:46 toral kernel: [  509.790195] Code: 58 2a 43 50 88 43 4e 48 83 c4 08 5b 5d c3 66 90 e8 0b fd ff ff eb e6 90 90 90 90 90 90 90 90 90 48 89 f8 89 d1 c1 e9 03 83 e2 07 <f3> 48 a5 89 d1 f3 a4 c3 20 48 83 ea 20 4c 8b 06 4c 8b 4e 08 4c 
Jul 15 17:53:46 toral kernel: [  509.790214] RIP  [<ffffffff8121fb0b>] memcpy+0xb/0x120
Jul 15 17:53:46 toral kernel: [  509.790216]  RSP <ffff880103793c58>
Jul 15 17:53:46 toral kernel: [  509.790217] CR2: ffffc9001153d000
Jul 15 17:53:46 toral kernel: [  509.790219] ---[ end trace e610e9ec534eb542 ]---

Offline

#23 2011-07-16 21:42:50

litemotiv
Forum Fellow
Registered: 2008-08-01
Posts: 5,026

Re: Unable to handle kernel paging request -- hardware problem?

Please don't hijack other threads or cross-post longint, see:

https://wiki.archlinux.org/index.php/Fo … ss-Posting
https://wiki.archlinux.org/index.php/Fo … _Hijacking

Closing, the original topic starter can request reopening if needed.


ᶘ ᵒᴥᵒᶅ

Offline

Board footer

Powered by FluxBB