Bug#160631: SIGBUS on FFB1 Creator3D under 2.2.20-sun4u-9 only

2003-01-12 Thread Branden Robinson
On Sat, Jan 11, 2003 at 10:04:24PM +0200, Baurjan Ismagulov wrote: > I'm seeing similar symptoms on my Ultra1 140E with FFB1 Creator3D. > However, the same configuration works just fine under 2.4.19-sun4u-27, > which I can't use due to Ultra1 onboard hme bug. > > How can I verify that this is the

Bug#160631: SIGBUS on FFB1 Creator3D under 2.2.20-sun4u-9 only

2003-01-12 Thread Branden Robinson
On Sat, Jan 11, 2003 at 10:04:24PM +0200, Baurjan Ismagulov wrote: > I'm seeing similar symptoms on my Ultra1 140E with FFB1 Creator3D. > However, the same configuration works just fine under 2.4.19-sun4u-27, > which I can't use due to Ultra1 onboard hme bug. > > How can I verify that this is the

Bug#160631: SIGBUS on FFB1 Creator3D under 2.2.20-sun4u-9 only

2003-01-11 Thread Baurjan Ismagulov
Hello Branden, I'm seeing similar symptoms on my Ultra1 140E with FFB1 Creator3D. However, the same configuration works just fine under 2.4.19-sun4u-27, which I can't use due to Ultra1 onboard hme bug. How can I verify that this is the same bug? Thanks in advance, Baurjan. -- To UNSUBSCRIBE,

Bug#160631: SIGBUS on FFB1 Creator3D under 2.2.20-sun4u-9 only

2003-01-11 Thread Baurjan Ismagulov
Hello Branden, I'm seeing similar symptoms on my Ultra1 140E with FFB1 Creator3D. However, the same configuration works just fine under 2.4.19-sun4u-27, which I can't use due to Ultra1 onboard hme bug. How can I verify that this is the same bug? Thanks in advance, Baurjan.