| Summary: | [Regression nv 0de9 ]System boot fails with -fixes kernel | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | lu hua <huax.lu> | ||||||
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | high | CC: | ben, chris, daniel, jbarnes, xunx.fang | ||||||
| Version: | unspecified | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
lu hua
2012-10-26 02:29:13 UTC
Created attachment 69100 [details]
messages
I have no idea what's going wrong here ... details surely appreciated. And attaching the entire messages file without cutting out irrelevant parts (your log spans multiple days) is not too useful. Also, the good/bad commit range spans the forward-rolling from 3.6 to 3.7-rc2, so this could very well be a unrelated regression in mainline. Since this is likely blocking further testing, please bisect and handle the bisect with top priority. Bisect shows: 4196faa8623264b79279a06fd186654c959f2767 is the first bad commit. commit 4196faa8623264b79279a06fd186654c959f2767 Author: Ben Skeggs <bskeggs@redhat.com> AuthorDate: Tue Jul 10 14:36:38 2012 +1000 Commit: Ben Skeggs <bskeggs@redhat.com> CommitDate: Wed Oct 3 13:12:46 2012 +1000 drm/nouveau/i2c: port to subdev interfaces v2/v3: Ben Skeggs <bskeggs@redhat.com> - fix typo in default bus selection - fix accidental loss of destructor v4: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com> - fix typo causing incorrect default i2c port settings when no BMP data Signed-off-by: Ben Skeggs <bskeggs@redhat.com> Hm, can you try latest upstream (Linus) git? It also happens on upstream tree. Test on commit 6f0c0580b70c89094b3422ba81118c7b959c7556. Can you please attach lspci -nn and dmesg with drm.debug=0xe from the last working kernel? Created attachment 69217 [details]
dmesg with drm.debug=0xe
#lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Ivy Bridge DRAM Controller [8086:0154] (rev 09) 00:01.0 PCI bridge [0604]: Intel Corporation Ivy Bridge PCI Express Root Port [8086:0151] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0166] (rev 09) 00:14.0 USB Controller [0c03]: Intel Corporation Panther Point USB xHCI Host Controller [8086:1e31] (rev 04) 00:16.0 Communication controller [0780]: Intel Corporation Panther Point MEI Controller #1 [8086:1e3a] (rev 04) 00:1a.0 USB Controller [0c03]: Intel Corporation Panther Point USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation Panther Point High Definition Audio Controller [8086:1e20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root Port 1 [8086:1e10] (rev c4) 00:1c.1 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root Port 2 [8086:1e12] (rev c4) 00:1c.3 PCI bridge [0604]: Intel Corporation Panther Point PCI Express Root Port 4 [8086:1e16] (rev c4) 00:1d.0 USB Controller [0c03]: Intel Corporation Panther Point USB Enhanced Host Controller #1 [8086:1e26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation Panther Point LPC Controller [8086:1e59] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation Panther Point 6 port SATA AHCI Controller [8086:1e03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation Panther Point SMBus Controller [8086:1e22] (rev 04) 01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0de9] (rev a1) 03:00.0 Network controller [0280]: Atheros Communications Inc. AR9485 Wireless Network Adapter [168c:0032] (rev 01) 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5289] (rev 01) 04:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 0a) Fixed on commit 4a8dece21eea0ad6aca442272673d48693cd93b4. Verified.Fixed. |
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.