Kernel 3.2.0-35-generic-pae does not boot

Asked by Gert de Boer on 2012-12-19

Yesterday I downloaded the new program versions with the Update Manager. Now my Samsung RF711 Notebook does not boot anymore. Using the previous kernel still works.

In the syslog, from here everything seems to go wrong:

Dec 19 11:43:21 Ubivompi kernel: [ 6.566485] BUG: unable to handle kernel NULL pointer dereference at 0000000c
Dec 19 11:43:21 Ubivompi kernel: [ 6.566488] IP: [<f8a0bd89>] nvc0_gpuobj_channel_init+0x109/0x180 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566503] *pdpt = 000000002f2d7001 *pde = 0000000000000000
Dec 19 11:43:21 Ubivompi kernel: [ 6.566506] Oops: 0000 [#1] SMP
Dec 19 11:43:21 Ubivompi kernel: [ 6.566508] Modules linked in: joydev rfcomm bnep parport_pc ppdev binfmt_misc snd_hda_intel(+) snd_hda_codec snd_hwdep snd_pcm psmouse snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device uvcvideo videodev snd lib80211_crypt_tkip btusb serio_raw bluetooth wl(P) i915(+) soundcore snd_page_alloc lib80211 mac_hid nouveau(+) ttm drm_kms_helper drm mxm_wmi wmi mei(C) i2c_algo_bit video lp parport usbhid hid r8169
Dec 19 11:43:21 Ubivompi kernel: [ 6.566531]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566533] Pid: 443, comm: modprobe Tainted: P C O 3.2.0-35-generic-pae #55-Ubuntu SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711/RF511/RF411/RF711
Dec 19 11:43:21 Ubivompi kernel: [ 6.566537] EIP: 0060:[<f8a0bd89>] EFLAGS: 00010293 CPU: 1
Dec 19 11:43:21 Ubivompi kernel: [ 6.566546] EIP is at nvc0_gpuobj_channel_init+0x109/0x180 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566547] EAX: 00000000 EBX: f6e6fc00 ECX: f6e6fe24 EDX: efb03540
Dec 19 11:43:21 Ubivompi kernel: [ 6.566549] ESI: 00000000 EDI: eec78400 EBP: ef317cc8 ESP: ef317ca4
Dec 19 11:43:21 Ubivompi kernel: [ 6.566551] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Dec 19 11:43:21 Ubivompi kernel: [ 6.566552] Process modprobe (pid: 443, ti=ef316000 task=f6a2bf70 task.ti=ef316000)
Dec 19 11:43:21 Ubivompi kernel: [ 6.566554] Stack:
Dec 19 11:43:21 Ubivompi kernel: [ 6.566555] 00001000 00000000 ef317cb8 eed00000 f1c1e310 00000000 f6e6fc00 eed00548
Dec 19 11:43:21 Ubivompi kernel: [ 6.566559] eed00000 ef317d20 f8a0c29a 00000296 ee2f802c ef317cf8 00000000 f6e6fc00
Dec 19 11:43:21 Ubivompi kernel: [ 6.566564] ef317d20 c1134125 ee2f8000 ee2f8000 80000003 80000002 eec78400 efb03540
Dec 19 11:43:21 Ubivompi kernel: [ 6.566568] Call Trace:
Dec 19 11:43:21 Ubivompi kernel: [ 6.566577] [<f8a0c29a>] nouveau_gpuobj_channel_init+0x26a/0x550 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566582] [<c1134125>] ? kmem_cache_alloc_trace+0x105/0x140
Dec 19 11:43:21 Ubivompi kernel: [ 6.566591] [<f8a086f4>] nouveau_channel_alloc+0x164/0x3e0 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566601] [<f8a10c16>] ? nouveau_fence_init+0x106/0x130 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566611] [<f8a071c9>] nouveau_card_init+0x599/0x620 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566619] [<f8a076f6>] nouveau_load+0x376/0x670 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566629] [<f88f4b9b>] drm_get_pci_dev+0x14b/0x2a0 [drm]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566634] [<c15a804d>] ? _raw_spin_lock_irqsave+0x2d/0x40
Dec 19 11:43:21 Ubivompi kernel: [ 6.566648] [<f8a8ad85>] nouveau_pci_probe+0xd/0xf [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566652] [<c12d2347>] local_pci_probe+0x47/0xb0
Dec 19 11:43:21 Ubivompi kernel: [ 6.566655] [<c12d3848>] pci_device_probe+0x68/0x90
Dec 19 11:43:21 Ubivompi kernel: [ 6.566658] [<c11a89e7>] ? sysfs_create_link+0x17/0x20
Dec 19 11:43:21 Ubivompi kernel: [ 6.566662] [<c1385c2d>] really_probe+0x4d/0x150
Dec 19 11:43:21 Ubivompi kernel: [ 6.566665] [<c138f299>] ? pm_runtime_barrier+0x49/0xb0
Dec 19 11:43:21 Ubivompi kernel: [ 6.566668] [<c1385e6a>] driver_probe_device+0x3a/0x60
Dec 19 11:43:21 Ubivompi kernel: [ 6.566671] [<c1385f21>] __driver_attach+0x91/0xa0
Dec 19 11:43:21 Ubivompi kernel: [ 6.566674] [<c1385e90>] ? driver_probe_device+0x60/0x60
Dec 19 11:43:21 Ubivompi kernel: [ 6.566677] [<c1384fa9>] bus_for_each_dev+0x49/0x70
Dec 19 11:43:21 Ubivompi kernel: [ 6.566680] [<c1385a61>] driver_attach+0x21/0x30
Dec 19 11:43:21 Ubivompi kernel: [ 6.566682] [<c1385e90>] ? driver_probe_device+0x60/0x60
Dec 19 11:43:21 Ubivompi kernel: [ 6.566685] [<c138573f>] bus_add_driver+0x17f/0x260
Dec 19 11:43:21 Ubivompi kernel: [ 6.566688] [<c12d3870>] ? pci_device_probe+0x90/0x90
Dec 19 11:43:21 Ubivompi kernel: [ 6.566690] [<c13863f6>] driver_register+0x66/0x110
Dec 19 11:43:21 Ubivompi kernel: [ 6.566693] [<c12d35f2>] __pci_register_driver+0x42/0xc0
Dec 19 11:43:21 Ubivompi kernel: [ 6.566700] [<f88f4ded>] drm_pci_init+0xfd/0x110 [drm]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566710] [<f88c2048>] nouveau_init+0x48/0x1000 [nouveau]
Dec 19 11:43:21 Ubivompi kernel: [ 6.566713] [<c1003035>] do_one_initcall+0x35/0x170
Dec 19 11:43:21 Ubivompi kernel: [ 6.566716] [<f88c2000>] ? 0xf88c1fff
Dec 19 11:43:21 Ubivompi kernel: [ 6.566719] [<c10962ec>] sys_init_module+0xac/0x210
Dec 19 11:43:21 Ubivompi kernel: [ 6.566722] [<c15af21f>] sysenter_do_call+0x12/0x28
Dec 19 11:43:21 Ubivompi kernel: [ 6.566724] Code: 00 00 e8 8b f3 ff ff 8b 45 e8 81 78 08 cf 00 00 00 77 48 8b 87 18 02 00 00 8d 8b 24 02 00 00 8b 93 6c 01 00 00 8b 80 40 08 00 00 <8b> 40 0c e8 df 41 00 00 85 c0 89 c6 75 22 8b 87 18 02 00 00 8d

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Last query:
2013-01-19
Last reply:
2012-12-19

This question was reopened

Thomas Kr├╝ger (thkrueger) said : #1

You should report this as a bug. Use the "Create bug report" link below!

Gert de Boer (gert-de-boer) said : #2

OK. Created bug Bug #1092479.

Gert de Boer (gert-de-boer) said : #3

I made my boot partition rather small, which means I have to delete older kernels manually. Now I am afraid of installing newest kernel version, as I have no idea the bug is solved or not. I assume it isn't, as there are no further comments on the related bug, except of somebody else who has the same problem. Please advice.

Can you help with this problem?

Provide an answer of your own, or ask Gert de Boer for more information if necessary.

To post a message you must log in.