On Tue, 2012-02-28 at 00:29 +0100, Flavio Stanchina wrote: > Package: linux-2.6 > Version: 3.2.4-1 > Severity: normal > > The kernel oopsed on me after I added a bitmap to a RAID1 md device with: > > mdadm --grow /dev/md2 --bitmap=internal > > This happened to me during normal operation -- twice, because I hoped the > first time it was just bad luck. Then I booted with init=/bin/bash, i.e. > nothing but the bare kernel, built a RAID1 on two spare partitions, added a > bitmap as described above and it oopsed again as soon as I tried to write > something to the device. I was able to capture some traces with my phone's > camera; this is my home computer so I'm not able to get a better trace with > netconsole or a serial port. Might however try at work if necessary. > > The first picture (27022012040-25%-gray.png) is the bottom part of a trace; > the rest scrolled away while I opened the phone, so I tried again and got > the second picture (27022012041-25%-gray.png) but it looks like there's no > overlap in the functions listed. [...] Please use netconsole <http://www.kernel.org/doc/Documentation/networking/netconsole.txt> or serial console <http://www.kernel.org/doc/Documentation/serial-console.txt> to capture the full oops or BUG message. The kernel developers are likely to have trouble tracking this down based on just the end of the call stack. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Attachment:
signature.asc
Description: This is a digitally signed message part