Re: xrender build causes kernel panic on Intel Mac

On Aug 24, 2006, at 11:59 PM, Tabitha McNerney wrote:

> On 8/24/06, Eric Albert <[email protected]> wrote:
> On Aug 24, 2006, at 7:00 AM, Tabitha McNerney wrote:
>
> > The strangest thing happened today. I was twice able to repeat this
> > problem.
> >
> > I built and installed a potpourri of ports from Darwin Ports 1.3.2
> > on to an
> > Intel based Mac running Mac OS X Server 10.4.7 Universal Binary  
> (a new
> > release from Apple). I was installing on to a disc volume that  
> was UFS
> > formatted.
> >
> > The culprit that I was able to repeat was when I ran this command:
> >
> > $ sudo port -s install xrender
> >
> > before finishing the install it would cause my Intel Mac to kernel
> > panic
> > (actually the machine would totally freeze up and all I could do
> > was hold
> > the power button in for five seconds to power down). After booting
> > up, a
> > report was generated to be sent to Apple. Here's the juicy part  
> of the
> > report (not sure if it is helpful?):
> >
> > panic(cpu 0 caller 0x002E50A0): bad dir
> >> Backtrace, Format - Frame : Return Address (4 potential args on
> >> stack)
> >> 0xb55b9a8 : 0x128cdb (0x3c99c4 0xb55b9cc 0x131cdf 0x0)
> >> 0xb55b9e8 : 0x2e50a0 (0x3e39d8 0x22686a8 0x863b85 0x814)
> >> 0xb55ba18 : 0x2e565d (0x353e9ac 0x814 0x3e39f0 0x0)
> >> 0xb55bab8 : 0x1e3beb (0xb55bad8 0xb55baec 0xb55bf58 0x0)
> >> 0xb55bb08 : 0x1cb92a (0x28dcb58 0xb55bce0 0xb55bdf4 0xb55bf58)
> >> 0xb55bb78 : 0x1cc150 (0xb55bcc8 0x1d35c19 0x1d 0x400)
> >> 0xb55bc28 : 0x1de332 (0xb55bcc8 0x259d5e4 0x63 0xd)
> >> 0xb55bc78 : 0x1d621a (0xb55bcc8 0xb55be3c 0xb55be7c 0x2e3d000)
> >> 0xb55be58 : 0x1d667d (0x0 0xb55be7c 0x22e79e4 0x1ae4898)
> >> 0xb55bf68 : 0x378f9c (0x22fa3e8 0x22e79a0 0x22e79e4 0x0)
> >> 0xb55bfc8 : 0x19b0ee (0x23cc468 0x0 0x19e0b5 0x23cc468) No mapping
> >> exists
> >> for frame pointer
> >> Backtrace terminated-invalid frame pointer 0xbffff258
> >>
> >
> > Kernel version:
> > Darwin Kernel Version 8.7.2: Tue Jul 25 23:09:54 PDT 2006; root:
> > xnu-792.10.96.obj~3/RELEASE_I386
> >
> > Model: Macmini1,1, BootROM MM11.004B.B00, 2 processors, Intel Core
> > Duo, 1.66GHz, 512 MB
> >
> >
> > Any ideas on what may have happened? Has anyone able to get this to
> > repeat
> > on their Intel based Mac?
>
> Definitely file this as a bug report with Apple -- <http://
> bugreport.apple.com/>.  Include the panic log from above; it'll be  
> a big help.
>
>
> Eric, I most definitely will report it to Apple's bug reporting  
> system (in addition I also sent the kernel panic report -- twice --  
> to Apple from my Intel Mac). I have resorted back to using Xcode  
> 2.2.1 and so far so good although I have not yet tried to perform a  
> port install on xrender. I have noticed, however, that the gcc  
> tools that Apple provides for Xcode 2.4 seem to really take  
> advantage of the dual cores on Mac Intel (Im' not sure what they  
> have done to optimize, but maybe they're making good use of distcc  
> for example?). XFree86 on a Mac Mini Intel dual core ( 1.6 Ghz)  
> installed with Xcode 2.4 tools on the system in about 20 minutes  
> (in the past this has taken upwards of 60 minutes or more).
>
> Do you know, is there any advantage to using Xcode 2.3 tools on a  
> system for installing MacPorts? I reverted to 2.2.1 because that is  
> the version of Xcode that I used on the same machine running OS X  
> 10.4.7 Intel-only client (not 10.4.7 Server Universal Binary). From  
> reading about Xcode 2.3, it didn't seem to be a huge advantage over  
> 2.2.1 but I may have missed important details. Xcode 2.3 has been  
> out since mid May of this year so perhaps there are a few MacPorts  
> users who have build MacPorts (Darwin Ports 1.3.1 ?) using Xcode 2.3?

In general, each version of Xcode is better than the previous  
one...or at least that's the goal. :)  There are important bug fixes  
and performance improvements in every release.  I'd definitely  
suggest using Xcode 2.4.

-Eric