NetBSD Problem Report #49562

From jarle@festningen.uninett.no  Tue Jan 13 07:59:40 2015
Return-Path: <jarle@festningen.uninett.no>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 10031A65C1
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 13 Jan 2015 07:59:40 +0000 (UTC)
Message-Id: <20150113075936.2146D80ADA@festningen.uninett.no>
Date: Tue, 13 Jan 2015 08:59:36 +0100 (CET)
From: jarle@uninett.no
Reply-To: jarle@uninett.no
To: gnats-bugs@gnats.NetBSD.org
Subject: i915drmkms panic during boot
X-Send-Pr-Version: 3.95

>Number:         49562
>Category:       port-i386
>Synopsis:       i915drmkms panic during boot
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    riastradh
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 13 08:00:00 +0000 2015
>Closed-Date:    Mon Mar 02 18:11:37 +0000 2015
>Last-Modified:  Mon Mar 02 18:11:37 +0000 2015
>Originator:     Jarle Greipsland
>Release:        NetBSD 7.99.4
>Organization:

>Environment:


System: NetBSD singsaker.uninett.no 7.99.4 NetBSD 7.99.4 (GENERIC) #4: Mon Jan 12 23:54:58 CET 2015  jarle@singsaker.uninett.no:/usr/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
I tried to boot a -current GENERIC kernel built yesterday on my Lenovo
T400s.  It paniced during autoconfiguration.  Console messages (ten finger
copy):
[ ... ]
pchb0 at pci0 dev 0 function 0: vendor 8086 product 2a40 (rev. 0x07)
agp0 at pchb0: GX4-family chipset
agp0: detected 32252k stolen memory
agp0: aperture at 0xd0000000, size 0x10000000
i915drmkms0 at pci0 dev 2 function 0: vendor 80086 product 2a42 (rev. 0x07)
drm: Memory usable by graphics device = 512M
drm: Supports vblank timestamp caching Rev 2 (21.10.2013)
drm: Driver supports precise vblank timestamp query.
i915drmkms0: interrupting at ioapic0 pin 16 (i915)
DRM error in init_ring_common: render ring initialization failed ctl 0001f001 head c454d07c tail 00000000 start 00003000
warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/inten_pm.c:5734: !power_domains->domain_use_count[domain]
panic: cpu_switchto: switching above IPL_SCHED (8)
fatal breakpoint in supervisor mode
trap type 1 code 0 epi c02a4094 cs 8 eflags 246 cr2 0 ilevel 8 esp c125194c
curlwp 0xc105f2a0 pid 0 lid 1 lowest kstack 0xc124f2c0

> bt
breakpoint
vpanic
snprintf
cpu_switchto
sleepq_block
cv_wait
linux_flush_workqueue
flush_scheduled_work
intel_modeset_cleanup
i915_driver_load
drm_dev_register
drm_pci_attach
i915drmkms_attach
config_attach_loc
pci_probe_device
pci_enumerate_bus
pcirescan
pciattach
config_attach_loc
config_found_ia
mp_pci_scan
mainbus_rescan
mainbus_attach
config_attach_loc
config_rootfound
cpu_configure
main

See also the thread starting with
http://mail-index.netbsd.org/current-users/2014/11/18/msg026163.html
for some similar problems.

A curious fact is that I can boot and happily use the -current kernel
provided I first boot an older kernel (in my case a kernel of 6.99.44
vintage) to single user, reboot, and then boot the -current kernel without
an intermediate powerdown.  Maybe something is not correctly initialized
with the -current kernel?

>How-To-Repeat:
Boot a -current kernel on a similar system?

>Fix:


>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: port-i386-maintainer->riastradh
Responsible-Changed-By: riastradh@NetBSD.org
Responsible-Changed-When: Sat, 28 Feb 2015 15:18:05 +0000
Responsible-Changed-Why:
mine


State-Changed-From-To: open->feedback
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Sat, 28 Feb 2015 15:18:05 +0000
State-Changed-Why:
Can you please try again from HEAD?  I believe the following two changes
may have fixed it:

https://mail-index.netbsd.org/source-changes/2015/02/25/msg063403.html
https://mail-index.netbsd.org/source-changes/2015/02/25/msg063404.html


From: Jarle Greipsland <jarle@uninett.no>
To: gnats-bugs@NetBSD.org, riastradh@NetBSD.org
Cc: port-i386-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
 gnats-admin@netbsd.org
Subject: Re: port-i386/49562 (i915drmkms panic during boot)
Date: Mon, 02 Mar 2015 12:06:39 +0100 (CET)

 riastradh@NetBSD.org writes:
 > State-Changed-From-To: open->feedback
 > State-Changed-By: riastradh@NetBSD.org
 > State-Changed-When: Sat, 28 Feb 2015 15:18:05 +0000
 > State-Changed-Why:
 > Can you please try again from HEAD?  I believe the following two changes
 > may have fixed it:
 > 
 > https://mail-index.netbsd.org/source-changes/2015/02/25/msg063403.html
 > https://mail-index.netbsd.org/source-changes/2015/02/25/msg063404.html
 Much better.  I can now cold boot a -current kernel on that
 system, and I consider the problem as fixed.

 				-jarle
 -- 
 Of course there's no reason for it, it's just our policy.

State-Changed-From-To: feedback->closed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Mon, 02 Mar 2015 18:11:37 +0000
State-Changed-Why:
Fixed, thanks for testing!


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.