Hi all,
It seems that revision 2288 broke something in the tyan/s2881 build; 2289 and 2290 are also bad. 2287 is ok.
Boot log attached; it just keeps rebooting after the 'Jumping to LinuxBIOS' line. This is gcc 3.4.
Suggestions?
Thanks, Ward.
* Ward Vandewege ward@gnu.org [060504 00:39]:
Hi all,
It seems that revision 2288 broke something in the tyan/s2881 build; 2289 and 2290 are also bad. 2287 is ok.
Boot log attached; it just keeps rebooting after the 'Jumping to LinuxBIOS' line. This is gcc 3.4.
Suggestions?
Yes, I suggest I owe you a beer next time we meet and you try 2291.
Yinghai Lu has sent a patch that is more complete but also more intrusive, which will go in later I guess. Until then this should work fine.
This one is a good reason for automated testing on hardware.. 8)
Stefan
On Thu, May 04, 2006 at 01:12:08AM +0200, Stefan Reinauer wrote:
- Ward Vandewege ward@gnu.org [060504 00:39]:
Hi all,
It seems that revision 2288 broke something in the tyan/s2881 build; 2289 and 2290 are also bad. 2287 is ok.
Boot log attached; it just keeps rebooting after the 'Jumping to LinuxBIOS' line. This is gcc 3.4.
Suggestions?
Yes, I suggest I owe you a beer next time we meet and you try 2291.
:) all right, will do so on Friday; not in the office tomorrow. I'll put a note on the s2881 build page that 2288 through 2290 are known bad.
Yinghai Lu has sent a patch that is more complete but also more intrusive, which will go in later I guess. Until then this should work fine.
This one is a good reason for automated testing on hardware.. 8)
Yes. I was thinking about that today while trying different revisions to see which one was the culprit. Would there be an easier way to do automated testing than having lots of boxes with some sort of software switchable BIOSsavior (actually, that would be a nice thing to have in any case)? Emulation, perhaps?
Ward.
* Ward Vandewege ward@gnu.org [060504 02:10]:
This one is a good reason for automated testing on hardware.. 8)
Yes. I was thinking about that today while trying different revisions to see which one was the culprit. Would there be an easier way to do automated testing than having lots of boxes with some sort of software switchable BIOSsavior (actually, that would be a nice thing to have in any case)? Emulation, perhaps?
It will come.
On Wed, May 03, 2006 at 08:10:13PM -0400, Ward Vandewege wrote:
On Thu, May 04, 2006 at 01:12:08AM +0200, Stefan Reinauer wrote:
- Ward Vandewege ward@gnu.org [060504 00:39]:
Hi all,
It seems that revision 2288 broke something in the tyan/s2881 build; 2289 and 2290 are also bad. 2287 is ok.
Boot log attached; it just keeps rebooting after the 'Jumping to LinuxBIOS' line. This is gcc 3.4.
Suggestions?
Yes, I suggest I owe you a beer next time we meet and you try 2291.
:) all right, will do so on Friday; not in the office tomorrow. I'll put a note on the s2881 build page that 2288 through 2290 are known bad.
Cool; 2298 works. Thanks.
Ward.
-
Stefan Reinauer -
Ward Vandewege