Language Selection

English French German Italian Portuguese Spanish

Kernel space: kerneloops, read-mostly, and I/O port 80

Filed under
Linux

Kerneloops. Triage is an important part of a kernel developer's job. A project as large and as widely-used as the kernel will always generate more bug reports than can be realistically addressed in the amount of time which is available. So developers must figure out which reports are most deserving of their attention. Sometimes the existence of an irate, paying customer makes this decision easy. Other times, though, it is a matter of making a guess at which bugs are affecting the largest numbers of users. And that often comes down to how many different reports have come in for a given problem.

Of course, counting reports is not the easiest thing to do, especially if they are not all sent to the same place. In an attempt to make this process easier, Arjan van de Ven has announced a new site at kerneloops.org. Arjan has put together some software which scans certain sites and mailing lists for posted kernel oops output; whenever a crash is found, it is stuffed into a database. Then an attempt is made to associate reports with each other based on kernel version and the call trace; from that, a list of the most popular ways to crash can be created. As of this writing, the current fashion for kernel oopses would appear to be in ieee80211_tx() in current development kernels. Some other information is stored with the trace; in particular, it is possible to see what the oldest kernel version associated with the problem is.

More Here




More in Tux Machines

2014 Catalyst Linux Graphics Benchmarks Year-In-Review

With the year quickly coming to an end, it's time to do our year-end driver recap benchmarks from the year for the proprietary AMD and NVIDIA graphics drivers as well as the open-source drivers. To get things started, here's benchmarks done of the official AMD Catalyst Linux releases of 2014 and testing these drivers on three different graphics cards. Read more

From Red Hat's CEO: Reflecting on a 'great year,' looking to '15

It is confirmed: 2014 has been a great year for Red Hat. [On Dec. 18], we announced third quarter results of our fiscal year 2015 and, with that, celebrated our 51st consecutive quarter of revenue growth - more than 12 years of consecutive revenue growth. Thank you to the team of Red Hat customers, partners, open source contributors, and associates around the world, for helping us propel Red Hat to new heights. While 2014 has been a fantastic year for Red Hat, it has also been a banner year for open source. Read more Also: Red Hat Tech Exchange highlights: Architect, Implement, Enable

Open Source's 2014: MS 'cancer' embrace, NASDAQ listings, and a quiet dog

Ho hum. Another year, another slew of open source announcements that prove the once-maligned development methodology is now so mainstream as to be tedious. Running most of the world’s most powerful supercomputers? Been there, done that. Giving retailers the ability to deliver highly customized paper coupons to consumers based on warehouse inventory nearby? So 2013! And yet in 2014 we had a few events in open source that managed to surprise us, and suggest an even brighter future. Read more

How About 2014?

As for */Linux taking over the world, I think it’s inevitable. Android/Linux seems to be working on it’s third billion users perhaps by the end of 2015. At some point there will be saturation but the diversity is amazing. I saw a young lady with a Christmas gift of a CyanogenMod Android/Linux smartphone. CyanogenMod is a customization of Android/Linux which gives users more features and some independence from Google. She’s leaving a feature-phone behind as soon as she can switch “sim” cards. Within hours she’s learned to use a bunch of features including speech-to-text (It was nearly perfect)… Strangely, at about the same time her regular notebook PC (GNU/Linux) melted down (hard drive suspected). It will be interesting to see whether she even needs to replace it. This smartphone is just so powerful. Maybe I will get one and leave Beast to serving/storing stuff. Read more