[Fwd: Re: [] Blade 2000]

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Fwd: Re: [] Blade 2000]

Ferris McCormick
For you information if you have not seen this.  Looks like kernel
2.6.29(-r4) has problems on SB2000 at least with the disk firmware.

-------- Forwarded Message --------
From: David Miller <[hidden email]>
To: [hidden email]
Cc: [hidden email]
Subject: Re: [] Blade 2000
Date: Thu, 11 Jun 2009 03:38:04 -0700 (PDT)

From: BERTRAND Joël <[hidden email]>
Date: Fri, 29 May 2009 11:58:54 +0200

> BERTRAND Joël a écrit :
>>     Hello,
>>     I have made some minor modifications in bbc_i2c driver to add en entry
>>     in /proc directory. ALl mofications have been made against
>>     but I haven't verified that this kernel was bootable.
>>     I have built my own bbc_i2c driver as a module. kernel hangs
>>     just after qla2xxx initialization. I don't think that this driver try
>>     to upload firmware. This firmware is built into the kernel.
>> CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
>> # CONFIG_STANDALONE is not set
>> CONFIG_EXTRA_FIRMWARE="ql2200_fw.bin"
>> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
>> Root rayleigh:[/lib/firmware] > ls
>> edgeport emi62 keyspan_pda ql2100_fw.bin ql2300_fw.bin ql2400_fw.bin
>> emi26     ess    korg         ql2200_fw.bin  ql2322_fw.bin  yamaha
>> Root rayleigh:[/lib/firmware] >
>> Configuration:
>> Blade 2000, 2 GB, 2*UIII+/900, Creator3D, internal NIC + 2*3Com NIC.
>>     Is it a known trouble ?
> Nobody ? I have tried with exactly the same bug.
> worked fine.
I just did a scan over the driver changes for qla2xxx from 2.6.28
and 2.6.29 and they were very extensive and complicated.

What we need to do to narrow this down is do a GIT bisect.  I hope
that you have a GIT tree handy and can do this?

Luckily it's pretty easy to only bisect through the qla2xxx changes.

Once you have a tree checked out, start like this:

bash$ git bisect start v2.6.29 v2.6.28 -- drivers/scsi/qla2xxx/

Configure and build that kernel, see if it shows the bug.

If the bug is there go into the GIT tree and say:

bash$ git bisect bad

else if the bug is not there say:

bash$ git bisect good

Rebuild and retest.  Repeat this process of testing and then
running "git bisect good" or "git bisect bad" until the guilty
changeset is found.  At most you'll need to do this 6 times.

Post the result here.

We'll find a way to fix this, thanks!
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Ferris McCormick (P44646, MI) <[hidden email]>
Developer, Gentoo Linux (Sparc, Userrel, Trustees)

signature.asc (205 bytes) Download Attachment