PowerMac G5 Quad 2.5 panics at radeondrm

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
I just installed OpenBSD-current on my PowerMac11,2 which is the very
last generation of PowerMac G5 systems. My particular one is the quad
2.5GHz model.

As a sidenote, I tried installing an Intel 535 SSD and an OCZ Vertex 4
SSD and neither was detected by the SATA controller. I had read about
that being an issue on some SSDs and that Samsung SSDs did not have this
issue with older and slower SATA chipsets. I tried a Samsung 850 Pro and
it worked fine.

I was able to install just fine with the installer but when I rebooted
with bsd.mp, I get a panic right after cpu and memory detection due to
radeondrm. A boot -c and disable radeondrm allows the system to boot
fine but I would like to get this Radeon X1950 that I bought for this
purpose working since in theory I could have a decent Xorg experience.
Here is the panic transcribed by hand:

...snip...
memc0 at mainbus0: u4 rev 0x42
kiic0 at memc0 offset 0xf8001000
iic0 at kiic0
lmtemp0 at iic0 addr 0x4a: ds1775
maxds0 at iic0 addr 0x4b: ds1631
maxtmp0 at iic0 addr 0x4c: max6690
maxtmp1 at iic0 addr 0x4e: max6690
"dart" at memc0 offset 0xf8033000 not configured
openpic0 at memc0 offset 0xf8040000: version 0x4614 feature 7b0302 BE
mpcpcibr0 at mainbus0 pci: u4-pcie
pci0 at mpcpcibr0 bus 0
radeondrm0 at pci0 dev 0 function 0 "ATI Radeon X1950" rev 0x00
drm0 at radeondrm0
radeondrm0: irq 3
kern dsi on addr ffffffff iar 57c218
panic: trap type 300 at 57c218 (pci_conf_write+0x1c) lr 590f50
Stopped at      Debugger+0x10:  lwz r0,36(41)
   TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*    0      0      0     0x10000      0x200    0  swapper
Debugger() at Debugger+0xc
End of kernel: 0x904700
end trace frame: 0x904700, count: 14


I did not grab the dmesg from booting with radeondrm disabled (I can
grab it later today if need be) but the dmesg from bsd.rd is at the
bottom before I installed the Samsung SSD. Any idea what might be
causing the panic?

Bryan



console out [ATY,Prionace_A] console in [keyboard], using USB
using parent ATY,PrionaceParent:: memaddr 98000000, size 8000000 : consaddr 98008000 : ioaddr 90020000, size 20000: width 2560 linebytes 2560 height 1600 depth 8
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2016 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.0-current (RAMDISK) #10: Wed Dec  7 13:15:46 MST 2016
    [hidden email]:/usr/src/sys/arch/macppc/compile/RAMDISK
real mem = 0 (0MB)
avail mem = 1817899008 (1733MB)
mainbus0 at root: model PowerMac11,2
cpu0 at mainbus0: 970MP (Revision 0x101): 2500 MHz
cpu at mainbus0 not configured
cpu at mainbus0 not configured
cpu at mainbus0 not configured
mem at mainbus0 not configured
memc0 at mainbus0: u4 rev 0x42
kiic0 at memc0 offset 0xf8001000
iic0 at kiic0
"ds1775" at iic0 addr 0x4a not configured
"ds1631" at iic0 addr 0x4b not configured
"max6690" at iic0 addr 0x4c not configured
"max6690" at iic0 addr 0x4e not configured
"dart" at memc0 offset 0xf8033000 not configured
openpic0 at memc0 offset 0xf8040000: version 0x4614 feature 7b0302 BE
mpcpcibr0 at mainbus0 pci: u4-pcie
pci0 at mpcpcibr0 bus 0
vgafb0 at pci0 dev 0 function 0 "ATI Radeon X1950" rev 0x00, mmio
wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation)
ht0 at mainbus0: u3-ht, 10 devices
pci1 at ht0 bus 0
hpb0 at pci1 dev 7 function 0 "Apple Shasta PCI" rev 0x00: 85 sources
pci2 at hpb0 bus 2
ppb0 at pci1 dev 1 function 0 "ServerWorks HT-2000 PCIX" rev 0xa3
pci3 at ppb0 bus 4
ppb1 at pci1 dev 2 function 0 "ServerWorks HT-2000 PCIX" rev 0xa3
pci4 at ppb1 bus 5
bge0 at pci4 dev 4 function 0 "Broadcom BCM5780" rev 0x03, BCM5714 B3 (0x8003): irq 66, address 00:14:51:65:e6:96
brgphy0 at bge0 phy 1: BCM5780 10/100/1000baseT/SX PHY, rev. 0
bge1 at pci4 dev 4 function 1 "Broadcom BCM5780" rev 0x03, BCM5714 B3 (0x8003): irq 67, address 00:14:51:65:e6:97
brgphy1 at bge1 phy 1: BCM5780 10/100/1000baseT/SX PHY, rev. 0
ppb2 at pci1 dev 3 function 0 "ServerWorks HT-2000 PCIE" rev 0xa3
pci5 at ppb2 bus 6
ppb3 at pci1 dev 4 function 0 "ServerWorks HT-2000 PCIE" rev 0xa3
pci6 at ppb3 bus 7
ppb4 at pci1 dev 5 function 0 "ServerWorks HT-2000 PCIE" rev 0xa3
pci7 at ppb4 bus 8
ppb5 at pci1 dev 6 function 0 "ServerWorks HT-2000 PCIE" rev 0xa3
pci8 at ppb5 bus 9
ppb6 at pci1 dev 8 function 0 "Apple Shasta PCI" rev 0x00
pci9 at ppb6 bus 1
macobio0 at pci9 dev 7 function 0 "Apple Shasta" rev 0x00
macgpio0 at macobio0 offset 0x50
"smu-doorbell" at macgpio0 offset 0x12 not configured
"smu-interrupt" at macgpio0 offset 0xd not configured
"programmer-switch" at macgpio0 offset 0xc not configured
"chip-fault" at macgpio0 offset 0xe not configured
"slewing-done" at macgpio0 offset 0x38 not configured
"mlb-good" at macgpio0 offset 0x13 not configured
"vdnap0" at macgpio0 offset 0x14 not configured
"timebase-enable" at macgpio0 offset 0x26 not configured
"amp-mute" at macgpio0 offset 0x30 not configured
"dig-hw-reset-c" at macgpio0 offset 0x9 not configured
"codec-error-irq" at macgpio0 offset 0x32 not configured
"codec-clock-mux" at macgpio0 offset 0x31 not configured
"headphone-detect" at macgpio0 offset 0x2c not configured
"headphone-mute" at macgpio0 offset 0x2f not configured
"hw-reset" at macgpio0 offset 0xa not configured
"lineout-detect" at macgpio0 offset 0x28 not configured
"linein-detect" at macgpio0 offset 0x2a not configured
"lineout-mute" at macgpio0 offset 0x2e not configured
"escc-legacy" at macobio0 offset 0x12000 not configured
zs0 at macobio0 offset 0x13000: irq 23,24
zstty0 at zs0 channel 0
zstty1 at zs0 channel 1
"i2c" at macobio0 offset 0x18000 not configured
"i2s" at macobio0 offset 0x0 not configured
"timer" at macobio0 offset 0x15000 not configured
"Broadcom BCM4318" rev 0x02 at pci9 dev 1 function 0 not configured
ohci0 at pci9 dev 11 function 0 "NEC USB" rev 0x43: irq 70, version 1.0
ohci1 at pci9 dev 11 function 1 "NEC USB" rev 0x43: irq 70, version 1.0
ehci0 at pci9 dev 11 function 2 "NEC USB" rev 0x04: irq 70
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "NEC EHCI root hub" rev 2.00/1.00 addr 1
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "NEC OHCI root hub" rev 1.00/1.00 addr 1
usb2 at ohci1: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "NEC OHCI root hub" rev 1.00/1.00 addr 1
ppb7 at pci1 dev 9 function 0 "Apple Shasta PCI" rev 0x00
pci10 at ppb7 bus 3
pciide0 at pci10 dev 12 function 0 "ServerWorks K2 SATA" rev 0x00: DMA
pciide0: using irq 10 for native-PCI interrupt
pciide0: port 0: PHY offline
pciide0: port 1: PHY offline
kauaiata0 at pci10 dev 13 function 0 "Apple Shasta ATA" rev 0x00
wdc0 at kauaiata0 irq 38: DMA
atapiscsi0 at wdc0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, DVD-RW GWA-4165B, C006> ATAPI 5/cdrom removable
cd0(wdc0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 4
"Apple Shasta Firewire" rev 0x00 at pci10 dev 14 function 0 not configured
smu0 at mainbus0: too many fans
uhub3 at uhub1 port 1 configuration 1 interface 0 "Mitsumi Electric Hub in Apple Extended USB Keyboard" rev 1.10/4.10 addr 2
uhidev0 at uhub3 port 3 configuration 1 interface 0 "Mitsumi Electric Apple Extended USB Keyboard" rev 1.10/4.10 addr 3
uhidev0: iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0: console keyboard, using wsdisplay0
uhidev1 at uhub3 port 3 configuration 1 interface 1 "Mitsumi Electric Apple Extended USB Keyboard" rev 1.10/4.10 addr 3
uhidev1: iclass 3/0, 3 report ids
uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 3: input=3, output=0, feature=0
uhidev2 at uhub1 port 3 configuration 1 interface 0 "vendor 0x05ac product 0x1000" rev 2.00/19.65 addr 4
uhidev2: iclass 3/1
ukbd1 at uhidev2
wskbd1 at ukbd1 mux 1
wskbd1: connecting to wsdisplay0
uhidev3 at uhub1 port 3 configuration 1 interface 1 "vendor 0x05ac product 0x1000" rev 2.00/19.65 addr 4
uhidev3: iclass 3/1
uhid2 at uhidev3: input=3, output=0, feature=1
uhidev4 at uhub2 port 2 configuration 1 interface 0 "CHICONY USB Keyboard" rev 2.00/2.30 addr 2
uhidev4: iclass 3/1
ukbd2 at uhidev4
wskbd2 at ukbd2 mux 1
wskbd2: connecting to wsdisplay0
uhidev5 at uhub2 port 2 configuration 1 interface 1 "CHICONY USB Keyboard" rev 2.00/2.30 addr 2
uhidev5: iclass 3/0, 3 report ids
uhid3 at uhidev5 reportid 1: input=1, output=0, feature=0
uhid4 at uhidev5 reportid 2: input=1, output=0, feature=0
uhid5 at uhidev5 reportid 3: input=3, output=0, feature=0
softraid0 at root
scsibus1 at softraid0: 256 targets
bootpath: /ht/pci@9/ata-6/disk@0:/6.0/macppc/bsd.rd
root on rd0a swap on rd0b dump on rd0b
WARNING: unable to get date/time -- CHECK AND RESET THE DATE!

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
On Thu, Dec 08, 2016 at 11:54:55AM -0800, Bryan Vyhmeister wrote:

> I just installed OpenBSD-current on my PowerMac11,2 which is the very
> last generation of PowerMac G5 systems. My particular one is the quad
> 2.5GHz model.
>
> As a sidenote, I tried installing an Intel 535 SSD and an OCZ Vertex 4
> SSD and neither was detected by the SATA controller. I had read about
> that being an issue on some SSDs and that Samsung SSDs did not have this
> issue with older and slower SATA chipsets. I tried a Samsung 850 Pro and
> it worked fine.
>
> I was able to install just fine with the installer but when I rebooted
> with bsd.mp, I get a panic right after cpu and memory detection due to
> radeondrm. A boot -c and disable radeondrm allows the system to boot
> fine but I would like to get this Radeon X1950 that I bought for this
> purpose working since in theory I could have a decent Xorg experience.

Correction. The video card is actually a Radeon X1900 GT Mac G5 Edition,
not an X1950 as it is shown in the dmesg.

Bryan

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Mark Kettenis
In reply to this post by Bryan Vyhmeister-3
> Date: Thu, 8 Dec 2016 11:54:55 -0800
> From: Bryan Vyhmeister <[hidden email]>
>
> I just installed OpenBSD-current on my PowerMac11,2 which is the very
> last generation of PowerMac G5 systems. My particular one is the quad
> 2.5GHz model.
>
> As a sidenote, I tried installing an Intel 535 SSD and an OCZ Vertex 4
> SSD and neither was detected by the SATA controller. I had read about
> that being an issue on some SSDs and that Samsung SSDs did not have this
> issue with older and slower SATA chipsets. I tried a Samsung 850 Pro and
> it worked fine.
>
> I was able to install just fine with the installer but when I rebooted
> with bsd.mp, I get a panic right after cpu and memory detection due to
> radeondrm. A boot -c and disable radeondrm allows the system to boot
> fine but I would like to get this Radeon X1950 that I bought for this
> purpose working since in theory I could have a decent Xorg experience.
> Here is the panic transcribed by hand:
>
> ...snip...
> memc0 at mainbus0: u4 rev 0x42
> kiic0 at memc0 offset 0xf8001000
> iic0 at kiic0
> lmtemp0 at iic0 addr 0x4a: ds1775
> maxds0 at iic0 addr 0x4b: ds1631
> maxtmp0 at iic0 addr 0x4c: max6690
> maxtmp1 at iic0 addr 0x4e: max6690
> "dart" at memc0 offset 0xf8033000 not configured
> openpic0 at memc0 offset 0xf8040000: version 0x4614 feature 7b0302 BE
> mpcpcibr0 at mainbus0 pci: u4-pcie
> pci0 at mpcpcibr0 bus 0
> radeondrm0 at pci0 dev 0 function 0 "ATI Radeon X1950" rev 0x00
> drm0 at radeondrm0
> radeondrm0: irq 3
> kern dsi on addr ffffffff iar 57c218
> panic: trap type 300 at 57c218 (pci_conf_write+0x1c) lr 590f50
> Stopped at      Debugger+0x10:  lwz r0,36(41)
>    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
> *    0      0      0     0x10000      0x200    0  swapper
> Debugger() at Debugger+0xc
> End of kernel: 0x904700
> end trace frame: 0x904700, count: 14
>
>
> I did not grab the dmesg from booting with radeondrm disabled (I can
> grab it later today if need be) but the dmesg from bsd.rd is at the
> bottom before I installed the Samsung SSD. Any idea what might be
> causing the panic?

Does the diff below help?

Index: radeon_kms.c
===================================================================
RCS file: /cvs/src/sys/dev/pci/drm/radeon/radeon_kms.c,v
retrieving revision 1.48
diff -u -p -r1.48 radeon_kms.c
--- radeon_kms.c 8 Apr 2016 08:27:53 -0000 1.48
+++ radeon_kms.c 8 Dec 2016 20:07:37 -0000
@@ -478,7 +478,7 @@ radeondrm_attach_kms(struct device *pare
  int is_agp;
  pcireg_t type;
  uint8_t iobar;
-#if !defined(__sparc64__)
+#if !defined(__sparc64__) && !defined(__macppc__)
  pcireg_t addr, mask;
  int s;
 #endif
@@ -550,7 +550,7 @@ radeondrm_attach_kms(struct device *pare
  return;
  }
 
-#if !defined(__sparc64__)
+#if !defined(__sparc64__) && !defined(__macppc__)
  /*
  * Make sure we have a base address for the ROM such that we
  * can map it later.

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
On Thu, Dec 08, 2016 at 09:08:19PM +0100, Mark Kettenis wrote:
> Does the diff below help?

Thanks for your response. I will try the diff as soon as I can.
Apparently I spoke too soon about the Samsung 850 Pro SSD working just
fine. I am getting timeouts now for wd0 and git dumps core when I try to
checkout some files from GitHub. Perhaps I will order an OWC Electra 3G
SSD which they guarantee works fine with a PowerMac G5.

Bryan

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
In reply to this post by Mark Kettenis
On Thu, Dec 08, 2016 at 09:08:19PM +0100, Mark Kettenis wrote:
> Does the diff below help?

The SSD issues are due to some DMA issues with the SATA controller that
have not yet been ironed out apparently. I used an mfs filesystem for
/usr/src and /usr/obj and tried your diff. The first warm boot did not
end up in a panic but hung at wdc0 and the buffer went by too fast to
see radeondrm attach properly. A subsequent cold boot had the same panic
as before. Doing either a warm or cold boot makes no difference at this
point so the diff does not seem to solve the problem. Any other ideas?

Bryan

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
In reply to this post by Mark Kettenis
On Thu, Dec 08, 2016 at 09:08:19PM +0100, Mark Kettenis wrote:

> > Date: Thu, 8 Dec 2016 11:54:55 -0800
> > From: Bryan Vyhmeister <[hidden email]>
> >
> > I just installed OpenBSD-current on my PowerMac11,2 which is the very
> > last generation of PowerMac G5 systems. My particular one is the quad
> > 2.5GHz model.
> >
> > As a sidenote, I tried installing an Intel 535 SSD and an OCZ Vertex 4
> > SSD and neither was detected by the SATA controller. I had read about
> > that being an issue on some SSDs and that Samsung SSDs did not have this
> > issue with older and slower SATA chipsets. I tried a Samsung 850 Pro and
> > it worked fine.
> >
> > I was able to install just fine with the installer but when I rebooted
> > with bsd.mp, I get a panic right after cpu and memory detection due to
> > radeondrm. A boot -c and disable radeondrm allows the system to boot
> > fine but I would like to get this Radeon X1950 that I bought for this
> > purpose working since in theory I could have a decent Xorg experience.
> > Here is the panic transcribed by hand:
> >
> > ...snip...
> > memc0 at mainbus0: u4 rev 0x42
> > kiic0 at memc0 offset 0xf8001000
> > iic0 at kiic0
> > lmtemp0 at iic0 addr 0x4a: ds1775
> > maxds0 at iic0 addr 0x4b: ds1631
> > maxtmp0 at iic0 addr 0x4c: max6690
> > maxtmp1 at iic0 addr 0x4e: max6690
> > "dart" at memc0 offset 0xf8033000 not configured
> > openpic0 at memc0 offset 0xf8040000: version 0x4614 feature 7b0302 BE
> > mpcpcibr0 at mainbus0 pci: u4-pcie
> > pci0 at mpcpcibr0 bus 0
> > radeondrm0 at pci0 dev 0 function 0 "ATI Radeon X1950" rev 0x00
> > drm0 at radeondrm0
> > radeondrm0: irq 3
> > kern dsi on addr ffffffff iar 57c218
> > panic: trap type 300 at 57c218 (pci_conf_write+0x1c) lr 590f50
> > Stopped at      Debugger+0x10:  lwz r0,36(41)
> >    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
> > *    0      0      0     0x10000      0x200    0  swapper
> > Debugger() at Debugger+0xc
> > End of kernel: 0x904700
> > end trace frame: 0x904700, count: 14
> >
> >
> > I did not grab the dmesg from booting with radeondrm disabled (I can
> > grab it later today if need be) but the dmesg from bsd.rd is at the
> > bottom before I installed the Samsung SSD. Any idea what might be
> > causing the panic?
>
> Does the diff below help?
>
> Index: radeon_kms.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/drm/radeon/radeon_kms.c,v
> retrieving revision 1.48
> diff -u -p -r1.48 radeon_kms.c
> --- radeon_kms.c 8 Apr 2016 08:27:53 -0000 1.48
> +++ radeon_kms.c 8 Dec 2016 20:07:37 -0000
> @@ -478,7 +478,7 @@ radeondrm_attach_kms(struct device *pare
>   int is_agp;
>   pcireg_t type;
>   uint8_t iobar;
> -#if !defined(__sparc64__)
> +#if !defined(__sparc64__) && !defined(__macppc__)
>   pcireg_t addr, mask;
>   int s;
>  #endif
> @@ -550,7 +550,7 @@ radeondrm_attach_kms(struct device *pare
>   return;
>   }
>  
> -#if !defined(__sparc64__)
> +#if !defined(__sparc64__) && !defined(__macppc__)
>   /*
>   * Make sure we have a base address for the ROM such that we
>   * can map it later.
>

Do you have any further ideas on how to go about troubleshooting this?
Thanks for taking the time to generate this diff.

Bryan

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Mark Kettenis
> Date: Mon, 19 Dec 2016 11:06:31 -0800
> From: Bryan Vyhmeister <[hidden email]>
>
> On Thu, Dec 08, 2016 at 09:08:19PM +0100, Mark Kettenis wrote:
> > > Date: Thu, 8 Dec 2016 11:54:55 -0800
> > > From: Bryan Vyhmeister <[hidden email]>
> > >
> > > I just installed OpenBSD-current on my PowerMac11,2 which is the very
> > > last generation of PowerMac G5 systems. My particular one is the quad
> > > 2.5GHz model.
> > >
> > > As a sidenote, I tried installing an Intel 535 SSD and an OCZ Vertex 4
> > > SSD and neither was detected by the SATA controller. I had read about
> > > that being an issue on some SSDs and that Samsung SSDs did not have this
> > > issue with older and slower SATA chipsets. I tried a Samsung 850 Pro and
> > > it worked fine.
> > >
> > > I was able to install just fine with the installer but when I rebooted
> > > with bsd.mp, I get a panic right after cpu and memory detection due to
> > > radeondrm. A boot -c and disable radeondrm allows the system to boot
> > > fine but I would like to get this Radeon X1950 that I bought for this
> > > purpose working since in theory I could have a decent Xorg experience.
> > > Here is the panic transcribed by hand:
> > >
> > > ...snip...
> > > memc0 at mainbus0: u4 rev 0x42
> > > kiic0 at memc0 offset 0xf8001000
> > > iic0 at kiic0
> > > lmtemp0 at iic0 addr 0x4a: ds1775
> > > maxds0 at iic0 addr 0x4b: ds1631
> > > maxtmp0 at iic0 addr 0x4c: max6690
> > > maxtmp1 at iic0 addr 0x4e: max6690
> > > "dart" at memc0 offset 0xf8033000 not configured
> > > openpic0 at memc0 offset 0xf8040000: version 0x4614 feature 7b0302 BE
> > > mpcpcibr0 at mainbus0 pci: u4-pcie
> > > pci0 at mpcpcibr0 bus 0
> > > radeondrm0 at pci0 dev 0 function 0 "ATI Radeon X1950" rev 0x00
> > > drm0 at radeondrm0
> > > radeondrm0: irq 3
> > > kern dsi on addr ffffffff iar 57c218
> > > panic: trap type 300 at 57c218 (pci_conf_write+0x1c) lr 590f50
> > > Stopped at      Debugger+0x10:  lwz r0,36(41)
> > >    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
> > > *    0      0      0     0x10000      0x200    0  swapper
> > > Debugger() at Debugger+0xc
> > > End of kernel: 0x904700
> > > end trace frame: 0x904700, count: 14
> > >
> > >
> > > I did not grab the dmesg from booting with radeondrm disabled (I can
> > > grab it later today if need be) but the dmesg from bsd.rd is at the
> > > bottom before I installed the Samsung SSD. Any idea what might be
> > > causing the panic?
> >
> > Does the diff below help?
> >
> > Index: radeon_kms.c
> > ===================================================================
> > RCS file: /cvs/src/sys/dev/pci/drm/radeon/radeon_kms.c,v
> > retrieving revision 1.48
> > diff -u -p -r1.48 radeon_kms.c
> > --- radeon_kms.c 8 Apr 2016 08:27:53 -0000 1.48
> > +++ radeon_kms.c 8 Dec 2016 20:07:37 -0000
> > @@ -478,7 +478,7 @@ radeondrm_attach_kms(struct device *pare
> >   int is_agp;
> >   pcireg_t type;
> >   uint8_t iobar;
> > -#if !defined(__sparc64__)
> > +#if !defined(__sparc64__) && !defined(__macppc__)
> >   pcireg_t addr, mask;
> >   int s;
> >  #endif
> > @@ -550,7 +550,7 @@ radeondrm_attach_kms(struct device *pare
> >   return;
> >   }
> >  
> > -#if !defined(__sparc64__)
> > +#if !defined(__sparc64__) && !defined(__macppc__)
> >   /*
> >   * Make sure we have a base address for the ROM such that we
> >   * can map it later.
> >
>
> Do you have any further ideas on how to go about troubleshooting this?

Try to determine what pci_conf_write() call is failing, and with what
arguments it is being called.  Note that these calls may hide as
pci_write_config_dword(), pci_write_config_word() or
pci_write_config_byte() calls.

Reply | Threaded
Open this post in threaded view
|

Re: PowerMac G5 Quad 2.5 panics at radeondrm

Bryan Vyhmeister-3
On Mon, Dec 19, 2016 at 08:17:59PM +0100, Mark Kettenis wrote:
> Try to determine what pci_conf_write() call is failing, and with what
> arguments it is being called.  Note that these calls may hide as
> pci_write_config_dword(), pci_write_config_word() or
> pci_write_config_byte() calls.

I will see if I can figure out how to do this. Thank you for the
direction.

Bryan