On Tue, Mar 21, 2017 at 10:02:56AM +0100, Frans van Berckel wrote: > And yes, because Debian sparc64 runs very well with a 3.16 kernel- > image. The sparc backported one to be clear. I extracted the package > and copied it manually into the new rootfs. And updated the silo.conf.
Are you talking about the driver or the firmware? > But maybe we just have to build a sparc64 package for it :-) No, we have to fix the actual bug. Jamming an old, unsupported kernel into a sparc64 package is a workaround, not a fix. > > I also saw your report in the mailing list archives. > > And a real bug post, so being able tracking it ... > > https://bugzilla.kernel.org/show_bug.cgi?id=110081 You should add some SPARC kernel people to the CC of this bug report and also post this to the sparclinux kernel mailing list so you get some attention. > > I applied the following patch to a vanilla 4.9.0 kernel, and it > > didn't work either. > > https://patchwork.kernel.org/patch/6533041/ This very much looks like the root of the cause. Are you sure you properly applied and booted the right kernel? Sorry for asking stupid questions, but I have made similar mistakes in the past myself, so sometimes this cannot be ruled out :). > > If anyone has any ideas, i would greatly appreciate their input, as > > it would be nice to use the controller given that i just got a batch > > of disks to use with the built in backplane. > > I am open for new ideas as well. I would talk Meelis Roos who wrote the above patch. He probably has some insight. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
