Contributed by marco on from the angry-bob-is-scary-bob dept.
Updated at the bottom.
I start digging through the issue, talk to Toby, dig some more, screw around on Bob's box, call Jordan, screw around some more etc As I am closing in on the issue Jordan shows up on my doorstep with lunch and he immediately points out what's wrong. Poop, just spent hours looking for some stupid spec interpretation thing. Sun did it one way and Dell another way. We were reading a byte too early and discarding it so all the data we got from the sun was garbled; worked fine on the other boxes we tested on. Anyway we patch the box, build a new kernel, and reboot. Voila! it sprouts all kinds of stuff over the serial console. And it sprouts, and it sprouts, and it sprouts...
30 minutes later...
Hoorah! we are booting... And we are sprouting again... Damn it the ipmi poll is printing all kinds of debug goo I put in. And to top all this I forgot to set ddb.console=1.
I start working on acpi with Jordan and in between the polls I manage to log in to the box and type reboot. Hah, take that you stupid box! Needless to say that it never stopped spewing debug information until Bob power cycled it in the morning.
I did get a chance to test this on his IBM as well. We install it and are all hopeful just to see it crapping out completely differently. hey wait a minute I have seen this before. Hmmmm... Didn't we commit a patch for this weeks ago? We sure did! The IBM box has invalid values in it's SMBIOS and per the spec we have to use them. But when we start poking the ports nothing happens. We spent some time on the web looking for solutions but found none. There has to be some sort of quirk on these boxes, if anyone knows let me know.
Today I committed the fix for both sun issues. See cvs commit.
(Comments are closed)