On Sat, Feb 20, 2016 at 03:42:02AM +0000, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196944 > > --- Comment #2 from Andrew Daugherity <andrew.daugher...@gmail.com> --- > I've found the commit that breaks it: base r241438 (which was MFC into > stable/9 > as 243546). Reading the commit history between 9.1 and 9.2, I saw that > r248226 > (MFC onto 9-stable as r248858) claims to fix IPMI on a Sun X2200 that broke > with 241838, so my first test was to see if it was working just before that. > > I built a 9.2 kernel with sys/dev/bge/if_bge.c rolled back to the commit > before > the "bad" one, 243541 (MFC from 241436), and IPMI works! (I did not touch any > other files.) Also works for a stable/9 kernel (identified as 9.3-STABLE #1 > r243541:295788) with if_bge.c at 243541. > > If I update if_bge.c to the commit in question (241438 aka 243546), IPMI is > broken once more. I also tried r248858 (248226) which supposedly fixed IPMI > on > those Sun servers but it did not help here. I have not tried any other > commits, as it appears that for my hardware, it works on <=241436 and is > broken > for >=241438. > > I also fixed my 10.2 kernel in the same way by rolling back if_bge.c to > r241436. I had to merge r242426 and r242625 to get it to build; after doing > so > IPMI works in 10.2! > > Obviously rolling all the way back like this isn't the solution for everyone, > as there have been many other commits since then, but at least I found the > breakage point. I don't know the bge driver or kernel well enough to properly > fix it, but hopefully this is good information for someone who does.
Is there any chance that a patch for this bug will be available before 10.3 ? -- Laurent Frigault | Free.org _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
