Date: Fri, 31 Jul 2015 04:48:18 +0000 From: mailinglists@debank.tv To: "Glen Barber" <gjb@freebsd.org>, "Larry Rosenman" <ler@lerctr.org> Cc: "Benno Rice" <benno@freebsd.org>, freebsd-current@freebsd.org Subject: Re: pmspcv panic on boot on this box Message-ID: <866ce0ab91b71ca7c04599c041b90906@roundcube.debank.tv> In-Reply-To: <20150731042114.GP90754@FreeBSD.org> References: <20150731042114.GP90754@FreeBSD.org> <20150728210109.GA6424@oldtbh.lerctr.org> <04E640B9-423C-4C30-BF90-D3DD148C930D@FreeBSD.org> <765D2BB8-F101-4D8C-BF1D-BB896904FB29@FreeBSD.org> <e510aec2b8d394cccf166ecabcad9785@thebighonker.lerctr.org> <20150730201351.GH90754@FreeBSD.org> <20150730201517.GI90754@FreeBSD.org> <ef34a26f9f5ba7ca413f79fd914c6b86@thebighonker.lerctr.org> <20150730221728.GK90754@FreeBSD.org> <452d406c68674df3834c75bd3736e6dc@thebighonker.lerctr.org> <20150731041815.GO90754@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
July 31 2015 4:21 PM, "Glen Barber" <gjb@freebsd.org> wrote:=0A> On Fri, =
Jul 31, 2015 at 04:18:15AM +0000, Glen Barber wrote:=0A> =0A>> On Thu, Ju=
l 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote:=0A>>> On 2015-07-30=
17:17, Glen Barber wrote:=0A>>>> On Thu, Jul 30, 2015 at 03:20:46PM -050=
0, Larry Rosenman wrote:=0A>>>>> Kernel compiling -- give mr a bit and I'=
ll boot it and make sure it=0A>>>>> comes=0A>>>>> up.=0A>>>>> =0A>>>> =0A=
>>>> Larry, have you had any luck with this patch applied? If it resolves=
=0A>>>> your issue, I want to make sure it is included in the 10.2-RC2 bu=
ild.=0A>>>> =0A>>>> Thanks.=0A>>>> =0A>>> [...]=0A>>> =0A>>> There are 3 =
pictures from the CURRENT panic.=0A>>> =0A>>> it STILL fails. :(=0A>>> =
=0A>> =0A>> Larry, I am sorry this is causing headaches for you, and I ce=
rtainly=0A>> appreciate the prompt (and detailed) report, and assistance =
debugging=0A>> this.=0A>> =0A>> Would you be able to try one more test ca=
se?=0A>> =0A>> I'm interested in the behavior without the 'nodevice pmsdr=
v' addition to=0A>> your kernel configuration (effectively, removing the =
device from the=0A>> GENERIC kernel), and *without* the patch provided fr=
om Benno?=0A> =0A> To be more specific on what I'm interested in, 'nodevi=
ce pmsdrv' and=0A> 'device pmsdrv' should *both* be removed from the kern=
el configuration,=0A> and the pms(4) should only be available as a .ko mo=
dule.=0A> =0A>> In particular, I'm interested in if ahd(4) attaches or if=
loader(8)=0A>> auto-loads pms(4) after the PCI IDs are detected.=0A>> =
=0A>> As this issue also affects the upcoming 10.2-RELEASE, your willingn=
ess=0A>> to help debug this is greatly appreciated, as you've tripped ove=
r=0A>> something that would have caused a great deal of pain after 10.2 w=
as=0A>> release.=0A>> =0A>> I owe you several beers.=0A> =0A> Glen=0A=0A=
=0AHi All,=0A=0AI've experienced the same bug although with a mvs(4) devi=
ce on 10.2-PRERELEASE, once the pms driver is removed from the kernel con=
fig the problem disappears, I haven't had time to try the suggested patch=
as I only found this thread after removing the pms driver from the kerne=
l.=0A=0A=0ARob Evers=0A=0AP.S. some info from the machine=0A=0Aworking sy=
stem:=0A=0A# pciconf -l | grep mvs1=0Amvs1@pci0:5:0:0: class=3D0x0=
10400 card=3D0x02439005 chip=3D0x02439005 rev=3D0x02 hdr=3D0x00=0A=0A=0AF=
ailed boot:=0Acib2: allocated memory range (0xd0400000-0xd04fffff) for ri=
d 10 of pci0:5:0:0=0A map[18]: type I/O Port, range 32, base 0x300=
0, size 8, enabled=0Apcib2: allocated I/O port range (0x3000-0x30ff) for=
rid 18 of pci0:5:0:0=0A map[1c]: type Memory, range 64, base 0xd0=
300000, size 20, enabled=0Apcib2: attempting to grow memory window for (0=
xd0300000-0xd03fffff,0x100000)=0A front candidate range: 0xd030000=
0-0xd03fffff=0Apci5: pci0:5:0:0 bar 0x1c failed to allocate=0Apcib2: matc=
hed entry for 5.0.INTA=0Apcib2: slot 0 INTA hardwired to IRQ 16=0Apmspcv0=
port 0x3000-0x30ff mem 0xd0400000-0xd04fffff irq 16 at device 0.0 on pci=
5=0A=0A=0AFatal trap 12: page fault while in kernel mode=0Acpuid =3D 0; a=
pic id =3D 00=0Afault virtual address =3D 0x28=0Afault code =
=3D supervisor read data, page not present=0Ainstruction pointer =
=3D 0x20:0xffffffff80a0d984=0Astack pointer =3D 0x28:0xffffffff=
821ac2c0=0Aframe pointer =3D 0x28:0xffffffff821ac2d0=0Acode seg=
ment =3D base 0x0, limit 0xfffff, type 0x1b=0A =
=3D DPL 0, pres 1, long 1, def32 0, gran 1=0Aprocessor eflags =
=3D interrupt enabled, resume, IOPL =3D 0=0Acurrent process =
=3D 0 (swapper)=0Atrap number =3D 12=0Apanic: page fault=0Acp=
uid =3D 0=0AKDB: stack backtrace:=0A#0 0xffffffff80a17a30 at kdb_backtrac=
e+0x60=0A#1 0xffffffff809db196 at vpanic+0x126=0A#2 0xffffffff809db063 at=
panic+0x43=0A#3 0xffffffff80dee3eb at trap_fatal+0x36b=0A#4 0xffffffff80=
dee6ed at trap_pfault+0x2ed=0A#5 0xffffffff80dedd8a at trap+0x47a=0A#6 0x=
ffffffff80dd4102 at calltrap+0x8=0A#7 0xffffffff806b7a20 at agtiapi_attac=
h+0x3a0=0A#8 0xffffffff80a0e6cd at device_attach+0x43d=0A#9 0xffffffff80a=
0f82c at bus_generic_attach+0x4c=0A#10 0xffffffff8038069c at acpi_pci_att=
ach+0x15c=0A#11 0xffffffff80a0e6cd at device_attach+0x43d=0A#12 0xfffffff=
f80a0f82c at bus_generic_attach+0x4c=0A#13 0xffffffff803827cc at acpi_pci=
b_attach+0x22c=0A#14 0xffffffff80383a2f at acpi_pcib_pci_attach+0x9f=0A#1=
5 0xffffffff80a0e6cd at device_attach+0x43d=0A#16 0xffffffff80a0f82c at b=
us_generic_attach+0x4c=0A#17 0xffffffff8038069c at acpi_pci_attach+0x15c=
=0AUptime: 1s
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?866ce0ab91b71ca7c04599c041b90906>