Tetsuo Handa wrote: > > I'm sorry if this is a bit complicated but bisection down several > > regressions is one of the more advanced forms of regression > > bug hunt... You're quite cool if you can handle it :-) > > Sorry, I'm a beginner about git. I already know that 07c9249f is the cause of > "no console messages" and 5c49985c is the fix for "no console messages". > How can I setup a snapshot with 07c9249f and 5c49985c applied (I tried > > $ git reset --hard 07c9249f > $ git format-patch --stdout 5c49985c^..5c49985c | patch -p1 > > but patch does not apply cleanly) so that I can find the commit causing > "sym0: request irq 27 failure" which is between 07c9249f and 5c49985c?
I did a blind git bisection (i.e. starting $ qemu-system-arm -M versatilepb -hda hda.img -kernel arch/arm/boot/zImage -append "root=/dev/sda1 init=/bin/sh" -nographic and watching "top" for %CPU usage of qemu-system-arm , assuming that it goes to 100% only if detection of block device for / partition failed and kernel called panic(), goes to 0% otherwise) in two patterns. $ git bisect start HEAD b1112249 v3.7 v3.6 v3.5 v3.4 v3.3 v3.2 v3.1 v3.0 -- arch/arm drivers/scsi/sym53c8xx_2/ drivers/scsi/*.[ch] $ git bisect start v3.8-rc1 95e629b7 b8db6b8 810883f0 b10bca0b 14318efb 414a6750e b1112249 v3.7 v3.6 v3.5 v3.4 v3.3 v3.2 v3.1 v3.0 Both patterns resulted in that commit 07c9249f "ARM: 7554/1: VIC: use irq_domain_add_simple()" is the cause of PCI: enabling device 0000:00:0c.0 (0100 -> 0103) sym0: <895a> rev 0x0 at pci 0000:00:0c.0 irq 27 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym0: request irq 27 failure sym0: giving up ... message. Would you have a look? Regards. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
