On Tue, 18 Dec 2007, Stefan Richter wrote:
It's a 100% reproducible oops on Sparc (with FireWire controller) for
2.6.23 and 2.6.24 kernels, but not 2.6.22. The reporter confirmed that
the bug also happens
How do you achieve a sparc system with firewire ?
AFAIK there is no SBUS firewire card.
Markus Dahms wrote:
Hello again,
David Miller wrote:
When we boot the firmware provides a vector of function
pointers, and this is prom_nodeops. So prom_nodeops->no_nextprop()
is a routine inside the PROM.
Thanks. So there is no real chance to fix it but to override this
function?
T
Sorry, I did not make myself clear.
Linus Torvalds wrote:
On Fri, 25 May 2007, Chris Newport wrote:
Maybe we should take a hint from Solaris.
No. Solaris is shit. They make their decisions based on "we control the
hardware" kind of setup.
Not really a Solaris featur
Ingo Molnar wrote:
A BUG_ON() has a (much) lower likelyhood of being reported back - for
most users it is a "X just hung hard, there was nothing in the syslog, i
had to switch back to the older kernel" experience, and they do not have
a serial console to hook up (newer hardware often doesnt ev
4 matches
Mail list logo
