Strange QLA1040 firmaware load error with 2.6.30 from testing

[Uwe Schindler]

After upgrading to linux-image-2.6.30-alpha-generic I get the following
trace in the kernel log. The qlogic firmware package is installed, as
initramfs complained about missing bin files.

The driver loads and the system works as expected, all disks are reported:

[    4.416013] qla1280 0000:00:09.0: firmware: requesting qlogic/1040.bin
[    4.416013] ------------[ cut here ]------------
[    4.416013] WARNING: at
/build/buildd-linux-2.6_2.6.30-5-alpha-u828kA/linux-2
.6-2.6.30/debian/build/source_alpha_none/kernel/softirq.c:141
_local_bh_enable_i
p+0x4c/0xa4()
[    4.416013] Modules linked in: tulip(+) bitrev qla1280(+) scsi_mod
usbcore(+)
 de2104x crc32
[    4.416013] fffffc000f0479f8 0000000000000005 fffffc000103bef0
fffffc000e86d7
c0
[    4.416013]        0000000000000000 fffffc000c652c00 fffffc000e86d7c0
fffffff
f00000010
[    4.416013]        fffffc00011eb2d4 0000000000000001 fffffc00011ff958
fffffc0
00c652c00
[    4.416013]        fffffc000c652c18 fffffc000e86d7c0 fffffc000114baec
fffffc0
00c76e030
[    4.416013]        0000000000000007 fffffc000e86d7c0 fffffc000c76e000
fffffc0
00e8113c0
[    4.416013]        fffffc00013c66e8 fffffc00012bfdab 0000000000000001
0000000
000000000
[    4.416013] Trace:
[    4.416013] [<fffffc000103bef0>] _local_bh_enable_ip+0x4c/0xa4
[    4.416013] [<fffffc00011eb2d4>] sk_filter+0xcc/0x104
[    4.416013] [<fffffc00011ff958>] netlink_broadcast+0x1e0/0x3bc
[    4.416013] [<fffffc000114baec>] kobject_uevent_env+0x384/0x4a0
[    4.416013] [<fffffc00011b4ad0>] _request_firmware+0x468/0x57c
[    4.416013] [<fffffc000116485c>] local_pci_probe+0x24/0x38
[    4.416013] [<fffffc0001164b4c>] pci_device_probe+0x64/0xa0
[    4.416013] [<fffffc00011af048>] driver_probe_device+0xcc/0x1e0
[    4.416013] [<fffffc00011af1e4>] __driver_attach+0x88/0xd4
[    4.416013] [<fffffc00011ae5dc>] bus_for_each_dev+0x68/0xd0
[    4.416013] [<fffffc00011af15c>] __driver_attach+0x0/0xd4
[    4.416013] [<fffffc00011aee00>] driver_attach+0x2c/0x40
[    4.416013] [<fffffc00011adb28>] bus_add_driver+0xd8/0x304
[    4.416013] [<fffffc00011af69c>] driver_register+0x108/0x1d4
[    4.416013] [<fffffc000116501c>] __pci_register_driver+0x5c/0x120
[    4.416013] [<fffffc00010100bc>] do_one_initcall+0x74/0x1cc
[    4.416013] [<fffffc000105fb68>] SyS_init_module+0xf0/0x2c0
[    4.416013] [<fffffc000105fb50>] SyS_init_module+0xd8/0x2c0
[    4.416013] [<fffffc0001010de4>] entSys+0xa4/0xc0
[    4.416013]
[    4.416013] ---[ end trace b7134e8cc61d5fa9 ]---

Anybody has seen this, too?

Just one question: Is the firmware always needed or can I uninstall the
qlogic-firmware package again? Does the controller has an eprom or does it
only works with driver-provided firmware? As the firmware does not seem to
be loaded correctly, is it really needed?

I do not want to try this out, as I have no physical access to the machine
currently.

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@...



--
To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Uwe Schindler]

I found a bug report about this in the bts. I will forward.

> -----Original Message-----
> From: Uwe Schindler [mailto:uwe@...]
> Sent: Saturday, August 22, 2009 7:06 PM
> To: debian-alpha@...
> Subject: Strange QLA1040 firmaware load error with 2.6.30 from testing
>
> After upgrading to linux-image-2.6.30-alpha-generic I get the following
> trace in the kernel log. The qlogic firmware package is installed, as
> initramfs complained about missing bin files.
>
> The driver loads and the system works as expected, all disks are reported:
>
> [    4.416013] qla1280 0000:00:09.0: firmware: requesting qlogic/1040.bin
> [    4.416013] ------------[ cut here ]------------
> [    4.416013] WARNING: at
> /build/buildd-linux-2.6_2.6.30-5-alpha-u828kA/linux-2
> .6-2.6.30/debian/build/source_alpha_none/kernel/softirq.c:141
> _local_bh_enable_i
> p+0x4c/0xa4()
> [    4.416013] Modules linked in: tulip(+) bitrev qla1280(+) scsi_mod
> usbcore(+)
>  de2104x crc32
> [    4.416013] fffffc000f0479f8 0000000000000005 fffffc000103bef0
> fffffc000e86d7
> c0
> [    4.416013]        0000000000000000 fffffc000c652c00 fffffc000e86d7c0
> fffffff
> f00000010
> [    4.416013]        fffffc00011eb2d4 0000000000000001 fffffc00011ff958
> fffffc0
> 00c652c00
> [    4.416013]        fffffc000c652c18 fffffc000e86d7c0 fffffc000114baec
> fffffc0
> 00c76e030
> [    4.416013]        0000000000000007 fffffc000e86d7c0 fffffc000c76e000
> fffffc0
> 00e8113c0
> [    4.416013]        fffffc00013c66e8 fffffc00012bfdab 0000000000000001
> 0000000
> 000000000
> [    4.416013] Trace:
> [    4.416013] [<fffffc000103bef0>] _local_bh_enable_ip+0x4c/0xa4
> [    4.416013] [<fffffc00011eb2d4>] sk_filter+0xcc/0x104
> [    4.416013] [<fffffc00011ff958>] netlink_broadcast+0x1e0/0x3bc
> [    4.416013] [<fffffc000114baec>] kobject_uevent_env+0x384/0x4a0
> [    4.416013] [<fffffc00011b4ad0>] _request_firmware+0x468/0x57c
> [    4.416013] [<fffffc000116485c>] local_pci_probe+0x24/0x38
> [    4.416013] [<fffffc0001164b4c>] pci_device_probe+0x64/0xa0
> [    4.416013] [<fffffc00011af048>] driver_probe_device+0xcc/0x1e0
> [    4.416013] [<fffffc00011af1e4>] __driver_attach+0x88/0xd4
> [    4.416013] [<fffffc00011ae5dc>] bus_for_each_dev+0x68/0xd0
> [    4.416013] [<fffffc00011af15c>] __driver_attach+0x0/0xd4
> [    4.416013] [<fffffc00011aee00>] driver_attach+0x2c/0x40
> [    4.416013] [<fffffc00011adb28>] bus_add_driver+0xd8/0x304
> [    4.416013] [<fffffc00011af69c>] driver_register+0x108/0x1d4
> [    4.416013] [<fffffc000116501c>] __pci_register_driver+0x5c/0x120
> [    4.416013] [<fffffc00010100bc>] do_one_initcall+0x74/0x1cc
> [    4.416013] [<fffffc000105fb68>] SyS_init_module+0xf0/0x2c0
> [    4.416013] [<fffffc000105fb50>] SyS_init_module+0xd8/0x2c0
> [    4.416013] [<fffffc0001010de4>] entSys+0xa4/0xc0
> [    4.416013]
> [    4.416013] ---[ end trace b7134e8cc61d5fa9 ]---
>
> Anybody has seen this, too?
>
> Just one question: Is the firmware always needed or can I uninstall the
> qlogic-firmware package again? Does the controller has an eprom or does it
> only works with driver-provided firmware? As the firmware does not seem to
> be loaded correctly, is it really needed?
>
> I do not want to try this out, as I have no physical access to the machine
> currently.
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@...
>
>
>
> --
> To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@...

--
To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Michael Cree]

Uwe Schindler wrote:

>> After upgrading to linux-image-2.6.30-alpha-generic I get the following
>> trace in the kernel log. The qlogic firmware package is installed, as
>> initramfs complained about missing bin files.
>>
>> The driver loads and the system works as expected, all disks are reported:
>>
>> [    4.416013] qla1280 0000:00:09.0: firmware: requesting qlogic/1040.bin
>> [    4.416013] ------------[ cut here ]------------
>> [    4.416013] WARNING: at
>> /build/buildd-linux-2.6_2.6.30-5-alpha-u828kA/linux-2
>> .6-2.6.30/debian/build/source_alpha_none/kernel/softirq.c:141
>> _local_bh_enable_i
>>
>>
>> Anybody has seen this, too?
>>    

Yes.  I normally run my own kernel from kernel.org but the Debian kernel
has finally caught up to the leading edge and I thought I'd give it a
go.  With the Debian kernel I also see the warning and backtrace.  The
2.6.30.5 kernel I compiled from kernel.org source does not give the
warning.  That might be because I select the kernel config option to
include the firmwire in the kernel binary.

>> Just one question: Is the firmware always needed or can I uninstall the
>> qlogic-firmware package again? Does the controller has an eprom or does it
>> only works with driver-provided firmware? As the firmware does not seem to
>> be loaded correctly, is it really needed?
>>    

When I first tried the Debian 2.6.30 kernel the kernel locked up when
initialising the qlogic driver as I had completely forgotten about the
firmware.  After installing qlogic-firmware driver it then booted fine.  
Given I was running a kernel that included the firmware prior to running
the Debian kernel that is suggestive that the firmware is reloaded on
every boot.

Cheers
Michael.


--
To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Uwe Schindler]

> >> Just one question: Is the firmware always needed or can I uninstall the
> >> qlogic-firmware package again? Does the controller has an eprom or does
> it
> >> only works with driver-provided firmware? As the firmware does not seem
> to
> >> be loaded correctly, is it really needed?
> >>
>
> When I first tried the Debian 2.6.30 kernel the kernel locked up when
> initialising the qlogic driver as I had completely forgotten about the
> firmware.  After installing qlogic-firmware driver it then booted fine.
> Given I was running a kernel that included the firmware prior to running
> the Debian kernel that is suggestive that the firmware is reloaded on
> every boot.

Which is strange, because the SRM console and its I/O functions used by
aboot also use the SCSI controller to boot the kernel/initrd from my SCSI
ZIP disk (the root partition is on a large SATA disk with a SIL controller
initialized later from the initrd. Because of that, I think the system would
start without a firmware, but /boot and the CD-ROM mounts would be
unusable).

Maybe the firmware gets lost, when the PCI bus and the device is reset.

This is why I asked.

Uwe


--
To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Uwe Schindler]

With the latest testing 2.6.30-2 kernel package, the error disappeared, the
firmware loads correctly.

> > >> Just one question: Is the firmware always needed or can I uninstall
> the
> > >> qlogic-firmware package again? Does the controller has an eprom or
> does
> > it
> > >> only works with driver-provided firmware? As the firmware does not
> seem
> > to
> > >> be loaded correctly, is it really needed?
> > >>
> >
> > When I first tried the Debian 2.6.30 kernel the kernel locked up when
> > initialising the qlogic driver as I had completely forgotten about the
> > firmware.  After installing qlogic-firmware driver it then booted fine.
> > Given I was running a kernel that included the firmware prior to running
> > the Debian kernel that is suggestive that the firmware is reloaded on
> > every boot.
>
> Which is strange, because the SRM console and its I/O functions used by
> aboot also use the SCSI controller to boot the kernel/initrd from my SCSI
> ZIP disk (the root partition is on a large SATA disk with a SIL controller
> initialized later from the initrd. Because of that, I think the system
> would
> start without a firmware, but /boot and the CD-ROM mounts would be
> unusable).
>
> Maybe the firmware gets lost, when the PCI bus and the device is reset.
>
> This is why I asked.

--
To UNSUBSCRIBE, email to debian-alpha-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...