kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #114580
[Bug 1449299] [NEW] BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
Public bug reported:
Freshly installed 14.04.1-Ubuntu Desktop. First-time installation, no
legacy from prior versions.
Hardware: Asus P4C800 Deluxe, latest BIOS 1021.005 08/04/2005
Easily reproducible. Immediately after installing Ubuntu Desktop,
started getting freezes in the GUI. Usually happens within a minute or
so of using the GUI after boot-up. The system is unusable this way.
I am willing to make the machine available for remote or local (in
silicon valley) debugging.
ADDITIONAL INFORMATION:
Anecdotally, I noticed that if upon boot-up, I first launch the command-line console (CTL-ALT-F1), log into the console, then switch back to the graphical console (CTL-ALT-F7), then I am able to use the GUI for a couple of hours through normal shutdown without kernel crash. I observed this all of the 3 or so times that I did CTL-ALT-F1 and CTL-ALT-F7.
Here is the stack trace from syslog:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932232] BUG: unable to handle kernel paging request at f80f0000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932488] IP: [<c1326150>] iowrite32+0x30/0x40
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932585] *pdpt = 0000000001af5001 *pde = 000000003441c067 *pte = 0000000000000000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932787] Oops: 0002 [#1] SMP
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932865] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc snd_wavefront snd_cs4236 snd_opl3_lib snd_hwdep snd_wss_lib snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_intel8x0 snd_rawmidi snd_ac97_codec ac97_bus serio_raw snd_pcm snd_seq snd_seq_device snd_timer snd lpc_ich nouveau ns558 mxm_wmi wmi gameport soundcore video ttm drm_kms_helper drm i2c_algo_bit i82875p_edac edac_core shpchp parport_pc mac_hid ppdev lp parport hid_generic usbhid hid uas usb_storage firewire_ohci skge firewire_core pata_acpi crc_itu_t floppy
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934097] CPU: 1 PID: 1096 Comm: Xorg Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934234] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./P4C800, BIOS 1021.005 08/04/2005
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934389] task: eea92520 ti: f1a0e000 task.ti: f1a0e000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934487] EIP: 0060:[<c1326150>] EFLAGS: 00213292 CPU: 1
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934588] EIP is at iowrite32+0x30/0x40
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934681] EAX: 20000000 EBX: f80e0000 ECX: f80f0000 EDX: f80f0000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934813] ESI: 00003ffb EDI: ef88ad80 EBP: f1a0fd64 ESP: f1a0fd5c
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934907] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934991] CR0: 8005003b CR2: f80f0000 CR3: 2fecb000 CR4: 000007f0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935102] Stack:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935139] f90fd017 00000000 f1a0fd98 f90f9231 00000040 00000000 00000008 00000001
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935331] ef974800 0000ffec 00000000 ef88ad80 f6973000 eac9e800 00000000 f1a0fdf8
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935520] f9107a96 eac9e988 00f20000 00000000 00000000 00000000 00001c00 00000020
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935711] Call Trace:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935847] [<f90fd017>] ? nouveau_bo_wr32+0x27/0x30 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f9231>] nouveau_dma_wait+0x131/0x670 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f9107a96>] nouveau_crtc_page_flip+0x206/0x650 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c117910a>] ? kmem_cache_alloc_trace+0x17a/0x190
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d39cb>] drm_mode_page_flip_ioctl+0x15b/0x2c0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d3870>] ? drm_mode_gamma_get_ioctl+0xc0/0xc0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87c44ef>] drm_ioctl+0x1cf/0x530 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c108cf0d>] ? __enqueue_entity+0x6d/0x80
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d3870>] ? drm_mode_gamma_get_ioctl+0xc0/0xc0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c108e331>] ? set_next_entity+0xb1/0xe0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c10bbf8f>] ? ktime_get+0x4f/0x130
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c1438e41>] ? __pm_runtime_resume+0x51/0x70
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f7071>] nouveau_drm_ioctl+0x51/0x80 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f7020>] ? nouveau_pmops_thaw+0x20/0x20 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c119f5e2>] do_vfs_ioctl+0x2f2/0x4f0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c107d987>] ? hrtimer_start+0x27/0x30
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c105f7c0>] ? do_setitimer+0x200/0x270
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c10bc4b8>] ? ktime_get_ts+0x48/0x140
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c119f840>] SyS_ioctl+0x60/0x90
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c169461f>] sysenter_do_call+0x12/0x12
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] Code: 00 89 d1 77 26 81 fa 00 00 01 00 76 06 0f b7 d2 ef c3 90 55 ba 0d c8 8b c1 89 e5 89 c8 e8 49 fe ff ff 5d c3 8d b4 26 00 00 00 00 <89> 02 c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 3d ff ff 03 00
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] EIP: [<c1326150>] iowrite32+0x30/0x40 SS:ESP 0068:f1a0fd5c
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] CR2: 00000000f80f0000
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1449299
Title:
BUG: unable to handle kernel paging request at f80f0000 -
nouveau_bo_wr32+0x27/0x30
Status in linux package in Ubuntu:
Incomplete
Bug description:
Freshly installed 14.04.1-Ubuntu Desktop. First-time installation, no
legacy from prior versions.
Hardware: Asus P4C800 Deluxe, latest BIOS 1021.005 08/04/2005
Easily reproducible. Immediately after installing Ubuntu Desktop,
started getting freezes in the GUI. Usually happens within a minute or
so of using the GUI after boot-up. The system is unusable this way.
I am willing to make the machine available for remote or local (in
silicon valley) debugging.
ADDITIONAL INFORMATION:
Anecdotally, I noticed that if upon boot-up, I first launch the command-line console (CTL-ALT-F1), log into the console, then switch back to the graphical console (CTL-ALT-F7), then I am able to use the GUI for a couple of hours through normal shutdown without kernel crash. I observed this all of the 3 or so times that I did CTL-ALT-F1 and CTL-ALT-F7.
Here is the stack trace from syslog:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932232] BUG: unable to handle kernel paging request at f80f0000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932488] IP: [<c1326150>] iowrite32+0x30/0x40
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932585] *pdpt = 0000000001af5001 *pde = 000000003441c067 *pte = 0000000000000000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932787] Oops: 0002 [#1] SMP
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.932865] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc snd_wavefront snd_cs4236 snd_opl3_lib snd_hwdep snd_wss_lib snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_intel8x0 snd_rawmidi snd_ac97_codec ac97_bus serio_raw snd_pcm snd_seq snd_seq_device snd_timer snd lpc_ich nouveau ns558 mxm_wmi wmi gameport soundcore video ttm drm_kms_helper drm i2c_algo_bit i82875p_edac edac_core shpchp parport_pc mac_hid ppdev lp parport hid_generic usbhid hid uas usb_storage firewire_ohci skge firewire_core pata_acpi crc_itu_t floppy
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934097] CPU: 1 PID: 1096 Comm: Xorg Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934234] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./P4C800, BIOS 1021.005 08/04/2005
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934389] task: eea92520 ti: f1a0e000 task.ti: f1a0e000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934487] EIP: 0060:[<c1326150>] EFLAGS: 00213292 CPU: 1
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934588] EIP is at iowrite32+0x30/0x40
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934681] EAX: 20000000 EBX: f80e0000 ECX: f80f0000 EDX: f80f0000
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934813] ESI: 00003ffb EDI: ef88ad80 EBP: f1a0fd64 ESP: f1a0fd5c
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934907] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.934991] CR0: 8005003b CR2: f80f0000 CR3: 2fecb000 CR4: 000007f0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935102] Stack:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935139] f90fd017 00000000 f1a0fd98 f90f9231 00000040 00000000 00000008 00000001
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935331] ef974800 0000ffec 00000000 ef88ad80 f6973000 eac9e800 00000000 f1a0fdf8
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935520] f9107a96 eac9e988 00f20000 00000000 00000000 00000000 00001c00 00000020
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935711] Call Trace:
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.935847] [<f90fd017>] ? nouveau_bo_wr32+0x27/0x30 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f9231>] nouveau_dma_wait+0x131/0x670 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f9107a96>] nouveau_crtc_page_flip+0x206/0x650 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c117910a>] ? kmem_cache_alloc_trace+0x17a/0x190
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d39cb>] drm_mode_page_flip_ioctl+0x15b/0x2c0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d3870>] ? drm_mode_gamma_get_ioctl+0xc0/0xc0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87c44ef>] drm_ioctl+0x1cf/0x530 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c108cf0d>] ? __enqueue_entity+0x6d/0x80
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f87d3870>] ? drm_mode_gamma_get_ioctl+0xc0/0xc0 [drm]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c108e331>] ? set_next_entity+0xb1/0xe0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c10bbf8f>] ? ktime_get+0x4f/0x130
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c1438e41>] ? __pm_runtime_resume+0x51/0x70
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f7071>] nouveau_drm_ioctl+0x51/0x80 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<f90f7020>] ? nouveau_pmops_thaw+0x20/0x20 [nouveau]
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c119f5e2>] do_vfs_ioctl+0x2f2/0x4f0
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c107d987>] ? hrtimer_start+0x27/0x30
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c105f7c0>] ? do_setitimer+0x200/0x270
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c10bc4b8>] ? ktime_get_ts+0x48/0x140
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c119f840>] SyS_ioctl+0x60/0x90
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] [<c169461f>] sysenter_do_call+0x12/0x12
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] Code: 00 89 d1 77 26 81 fa 00 00 01 00 76 06 0f b7 d2 ef c3 90 55 ba 0d c8 8b c1 89 e5 89 c8 e8 49 fe ff ff 5d c3 8d b4 26 00 00 00 00 <89> 02 c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 3d ff ff 03 00
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] EIP: [<c1326150>] iowrite32+0x30/0x40 SS:ESP 0068:f1a0fd5c
Apr 27 11:16:24 vitaly-desktop kernel: [ 154.936020] CR2: 00000000f80f0000
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449299/+subscriptions
Follow ups
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Launchpad Bug Tracker, 2015-07-04
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Christopher M. Penalver, 2015-05-04
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-05-04
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Christopher M. Penalver, 2015-04-30
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Joseph Salisbury, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Alberto Salvia Novella, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Alberto Salvia Novella, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Alberto Salvia Novella, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-28
-
[Bug 1449299] WifiSyslog.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] UdevLog.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] UdevDb.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] PulseList.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] ProcModules.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] ProcInterrupts.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] ProcEnviron.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] ProcCpuinfo.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] Lsusb.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] Lspci.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] CurrentDmesg.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] CRDA.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] BootDmesg.txt
From: Vitaly, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-28
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-27
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-27
-
[Bug 1449299] Missing required logs.
From: Brad Figg, 2015-04-27
-
[Bug 1449299] Re: BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-27
-
[Bug 1449299] [NEW] BUG: unable to handle kernel paging request at f80f0000 - nouveau_bo_wr32+0x27/0x30
From: Vitaly, 2015-04-27
References