| 1 |
For you information if you have not seen this. Looks like kernel |
| 2 |
2.6.29(-r4) has problems on SB2000 at least with the disk firmware. |
| 3 |
|
| 4 |
-------- Forwarded Message -------- |
| 5 |
From: David Miller <davem@×××××××××.net> |
| 6 |
To: joel.bertrand@××××××××.fr |
| 7 |
Cc: sparclinux@×××××××××××.org |
| 8 |
Subject: Re: [2.6.29.4] Blade 2000 |
| 9 |
Date: Thu, 11 Jun 2009 03:38:04 -0700 (PDT) |
| 10 |
|
| 11 |
From: BERTRAND Joël <joel.bertrand@××××××××.fr> |
| 12 |
Date: Fri, 29 May 2009 11:58:54 +0200 |
| 13 |
|
| 14 |
> BERTRAND Joël a écrit : |
| 15 |
>> Hello, |
| 16 |
>> I have made some minor modifications in bbc_i2c driver to add en entry |
| 17 |
>> in /proc directory. ALl mofications have been made against 2.6.29.4 |
| 18 |
>> but I haven't verified that this kernel was bootable. |
| 19 |
>> I have built my own bbc_i2c driver as a module. 2.6.29.4 kernel hangs |
| 20 |
>> just after qla2xxx initialization. I don't think that this driver try |
| 21 |
>> to upload firmware. This firmware is built into the kernel. |
| 22 |
>> CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" |
| 23 |
>> # CONFIG_STANDALONE is not set |
| 24 |
>> # CONFIG_PREVENT_FIRMWARE_BUILD is not set |
| 25 |
>> CONFIG_FW_LOADER=y |
| 26 |
>> CONFIG_FIRMWARE_IN_KERNEL=y |
| 27 |
>> CONFIG_EXTRA_FIRMWARE="ql2200_fw.bin" |
| 28 |
>> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" |
| 29 |
>> Root rayleigh:[/lib/firmware] > ls |
| 30 |
>> edgeport emi62 keyspan_pda ql2100_fw.bin ql2300_fw.bin ql2400_fw.bin |
| 31 |
>> emi26 ess korg ql2200_fw.bin ql2322_fw.bin yamaha |
| 32 |
>> Root rayleigh:[/lib/firmware] > |
| 33 |
>> Configuration: |
| 34 |
>> Blade 2000, 2 GB, 2*UIII+/900, Creator3D, internal NIC + 2*3Com NIC. |
| 35 |
>> Is it a known trouble ? |
| 36 |
> |
| 37 |
> Nobody ? I have tried 2.6.29.1 with exactly the same bug. 2.6.28.7 |
| 38 |
> worked fine. |
| 39 |
|
| 40 |
I just did a scan over the driver changes for qla2xxx from 2.6.28 |
| 41 |
and 2.6.29 and they were very extensive and complicated. |
| 42 |
|
| 43 |
What we need to do to narrow this down is do a GIT bisect. I hope |
| 44 |
that you have a GIT tree handy and can do this? |
| 45 |
|
| 46 |
Luckily it's pretty easy to only bisect through the qla2xxx changes. |
| 47 |
|
| 48 |
Once you have a tree checked out, start like this: |
| 49 |
|
| 50 |
bash$ git bisect start v2.6.29 v2.6.28 -- drivers/scsi/qla2xxx/ |
| 51 |
|
| 52 |
Configure and build that kernel, see if it shows the bug. |
| 53 |
|
| 54 |
If the bug is there go into the GIT tree and say: |
| 55 |
|
| 56 |
bash$ git bisect bad |
| 57 |
|
| 58 |
else if the bug is not there say: |
| 59 |
|
| 60 |
bash$ git bisect good |
| 61 |
|
| 62 |
Rebuild and retest. Repeat this process of testing and then |
| 63 |
running "git bisect good" or "git bisect bad" until the guilty |
| 64 |
changeset is found. At most you'll need to do this 6 times. |
| 65 |
|
| 66 |
Post the result here. |
| 67 |
|
| 68 |
We'll find a way to fix this, thanks! |
| 69 |
-- |
| 70 |
To unsubscribe from this list: send the line "unsubscribe sparclinux" in |
| 71 |
the body of a message to majordomo@×××××××××××.org |
| 72 |
More majordomo info at http://vger.kernel.org/majordomo-info.html |
| 73 |
-- |
| 74 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
| 75 |
Developer, Gentoo Linux (Sparc, Userrel, Trustees) |
Archives