Attachment 53317 Details for Bug 41114 – nouveau crash

nouveau crash

nouveau-crash (text/plain), 5.50 KB, created by Xavier Bru on 2011-11-09 00:34:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Xavier Bru

Created: 2011-11-09 00:34:36 UTC

Size: 5.50 KB

patch

obsolete

>[drm] nouveau 0000:02:00.0: Detected an NVc0 generation card (0x0c8880a1)
>[drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PRAMIN
>[drm] nouveau 0000:02:00.0: ... BIOS signature not found
>[drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PROM
>[drm] nouveau 0000:02:00.0: ... appears to be valid
>[drm] nouveau 0000:02:00.0: BIT BIOS found
>[drm] nouveau 0000:02:00.0: Bios version 70.10.40.00
>[drm] nouveau 0000:02:00.0: Pointer to BIT loadval table invalid
>[drm] nouveau 0000:02:00.0: TMDS table version 2.0
>[drm] nouveau 0000:02:00.0: Found Display Configuration Block version 4.0
>[drm] nouveau 0000:02:00.0: Raw DCB entry 0: 02000300 00000000
>[drm] nouveau 0000:02:00.0: Raw DCB entry 1: 0000000e 00020030
>[drm] nouveau 0000:02:00.0: DCB connector table: VHER 0x40 5 16 4
>[drm] nouveau 0000:02:00.0:   0: 0x00000000: type 0x00 idx 0 tag 0xff
>[drm] nouveau 0000:02:00.0: Adaptor not initialised, running VBIOS init tables.
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table 0 at offset 0x7204
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x717F: Failed parsing init table opcode: INIT_I2C_IF -19
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x71D3: i2c bus not found
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x71E3: i2c bus not found
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x71EA: i2c bus not found
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x71F1: i2c bus not found
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x71F8: i2c bus not found
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table 1 at offset 0x78C6
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>[drm] nouveau 0000:02:00.0: 0x8B83: Failed parsing init table opcode: INIT_I2C_LONG_IF -19
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table 2 at offset 0x8DBC
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table 3 at offset 0x8DC6
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table 4 at offset 0x903A
>[drm] nouveau 0000:02:00.0: Parsing VBIOS init table at offset 0x909F
>[drm] nouveau 0000:02:00.0: unknown i2c port 51
>BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
>IP: [<ffffffffa0094636>] i2c_transfer+0x16/0x140 [i2c_core]
>PGD 0 
>Oops: 0000 [#1] SMP 
>last sysfs file: /sys/module/ttm/initstate
>CPU 0 
>Modules linked in: nouveau(+) i2c_i801 sg iTCO_wdt iTCO_vendor_support shpchp ext4 jbd2 ttm drm_kms_helper drm i2c_algo_bit i2c_core video output sd_mod crc_t10dif ehci_hcd uhci_hcd dm_mod megaraid_sas aacraid ahci
>
>Modules linked in: nouveau(+) i2c_i801 sg iTCO_wdt iTCO_vendor_support shpchp ext4 jbd2 ttm drm_kms_helper drm i2c_algo_bit i2c_core video output sd_mod crc_t10dif ehci_hcd uhci_hcd dm_mod megaraid_sas aacraid ahci
>Pid: 1162, comm: work_for_cpu Tainted: G   M       ----------------   2.6.32-131.12.1.bl6.Bull.26.x86_64 #1 Thurley
>RIP: 0010:[<ffffffffa0094636>]  [<ffffffffa0094636>] i2c_transfer+0x16/0x140 [i2c_core]
>RSP: 0018:ffff880378fbb9d0  EFLAGS: 00010282
>RAX: ffff880378fbba4f RBX: 0000000000000000 RCX: 0000000000000b58
>RDX: 0000000000000002 RSI: ffff880378fbba20 RDI: 0000000000000000
>RBP: ffff880378fbba10 R08: 0000000000000000 R09: ffffffff81631ea0
>R10: 0000000000000001 R11: 0000000000000000 R12: ffffffffa013f030
>R13: ffff880378fbbab0 R14: 0000000000000000 R15: ffff8801f757a000
>FS:  0000000000000000(0000) GS:ffff880028200000(0000) knlGS:0000000000000000
>CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>CR2: 0000000000000010 CR3: 0000000001a06000 CR4: 00000000000006f0
>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>Process work_for_cpu (pid: 1162, threadinfo ffff880378fb8000, task ffff880378ef7100)
>Stack:
> ffff880378fbba90 0000000000000000 ffff8801f757a000 0000000000000000
><0> ffffffffa013f030 ffff880378fbbab0 0000000000000000 ffff8801f757a000
><0> ffff880378fbba50 ffffffffa01384fb ffff00010000002d ffff880378fbba4f
>Call Trace:
> [<ffffffffa013f030>] ? probe_monitoring_device+0x0/0xd0 [nouveau]
> [<ffffffffa01384fb>] nouveau_probe_i2c_addr+0x4b/0x60 [nouveau]
> [<ffffffffa0138d8b>] nouveau_i2c_identify+0x5b/0x140 [nouveau]
> [<ffffffffa013ec8d>] nouveau_temp_probe_i2c+0xdd/0xe0 [nouveau]
> [<ffffffffa013ecbd>] nouveau_temp_init+0x2d/0x3a0 [nouveau]
> [<ffffffffa013db37>] nouveau_pm_init+0x47/0x2a0 [nouveau]
> [<ffffffffa012ca30>] ? parse_bit_A_tbl_entry+0x0/0x110 [nouveau]
> [<ffffffffa01368df>] ? nouveau_bios_init+0x130f/0x24c0 [nouveau]
> [<ffffffff81121210>] ? __pte_alloc_kernel+0x80/0xc0
> [<ffffffffa01130f3>] nouveau_card_init+0x393/0x13d0 [nouveau]
> [<ffffffffa01146ed>] nouveau_load+0x46d/0x7c0 [nouveau]
> [<ffffffffa00b1f7f>] drm_get_pci_dev+0x19f/0x300 [drm]
> [<ffffffff8104cf42>] ? default_wake_function+0x12/0x20
> [<ffffffff81075c80>] ? do_work_for_cpu+0x0/0x30
> [<ffffffffa017757a>] nouveau_pci_probe+0x15/0x89 [nouveau]
> [<ffffffff812754f7>] local_pci_probe+0x17/0x20
> [<ffffffff81075c98>] do_work_for_cpu+0x18/0x30
> [<ffffffff8107acf6>] kthread+0x96/0xa0
> [<ffffffff810041aa>] child_rip+0xa/0x20
> [<ffffffff8107ac60>] ? kthread+0x0/0xa0
> [<ffffffff810041a0>] ? child_rip+0x0/0x20
>Code: 50 48 c7 c2 60 41 09 a0 e8 88 f6 27 e1 c9 c3 66 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 0f 1f 44 00 00 <48> 8b 47 10 48 89 fb 49 89 f5 41 89 d6 48 83 38 00 0f 84 c4 00 
>RIP  [<ffffffffa0094636>] i2c_transfer+0x16/0x140 [i2c_core]
> RSP <ffff880378fbb9d0>
>CR2: 0000000000000010
>---[ end trace 081c6e81bc93ceb2 ]---
>Kernel panic - not syncing: Fatal exception

Actions: View

Attachments on bug 41114: 51516 | 51517 | 51692 | 53317

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.