Bug#579125: linux-headers-2.6.32-4-amd64: problem initializing LSI controller
Hi Moritz,
On Tue, 06.07.2010 at 01:16:18 +0200, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> tags 579125 moreinfo
> thanks
>
> On Sun, Apr 25, 2010 at 04:38:16PM +0200, Toni Mueller wrote:
> > Package: linux-headers-2.6.32-4-amd64
> > Version: 2.6.32-11~bpo50+1
> > Severity: normal
> >
> >
> > Hi,
> >
> > I'm not quite sure that this is the right package to report against.
> > Please reassign as you see fit.
>
> [...]
> >
> > This renders the card unusable.
>
> This seems to have been fixed in 2.6.32.12, which we pulled in
> upload 2.6.32-12:
>
> commit 3def5de896ab77232d1cb35fa63dbf627d1db328
> Author: Kashyap, Desai <kashyap.desai@lsi.com>
> Date: Wed Oct 7 11:27:40 2009 +0530
>
> mptspi: Fix for incorrect data underrun errata
>
> Could you try this kernel and see verify it's fixed there?
I've now booted
ii linux-image-2.6.32-bpo.5-amd64 2.6.32-15~bpo50+1 Linux 2.6.32 for 64-bit PCs
and get this in my /var/log/dmesg:
[ 23.172818] ------------[ cut here ]------------
[ 23.172871] WARNING: at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/page_alloc.c:1806 __alloc_pages_nodemask+0x167/0x5d0()
[ 23.172930] Hardware name: System Product Name
[ 23.172972] Modules linked in: pata_amd sata_nv usbhid hid mptspi mptscsih mptbase scsi_transport_spi e1000e forcedeth firewire_ohci ata_generic firewire_core crc_itu_t ohci_hcd ehci_hcd libata usbcore nls_base scsi_mod thermal fan thermal_sys
[ 23.173797] Pid: 760, comm: scsi_scan_9 Not tainted 2.6.32-bpo.5-amd64 #1
[ 23.173842] Call Trace:
[ 23.173886] [<ffffffff810b97cb>] ? __alloc_pages_nodemask+0x167/0x5d0
[ 23.173932] [<ffffffff810b97cb>] ? __alloc_pages_nodemask+0x167/0x5d0
[ 23.173979] [<ffffffff8104dc40>] ? warn_slowpath_common+0x77/0xa3
[ 23.174025] [<ffffffff810b97cb>] ? __alloc_pages_nodemask+0x167/0x5d0
[ 23.174074] [<ffffffff81015af6>] ? dma_generic_alloc_coherent+0x9a/0x120
[ 23.174124] [<ffffffffa010a3e5>] ? mptspi_write_spi_device_pg1+0xa1/0x1ce [mptspi]
[ 23.174179] [<ffffffff811965b6>] ? __bitmap_weight+0x3a/0x7e
[ 23.174227] [<ffffffffa010a576>] ? mptspi_write_width+0x64/0x69 [mptspi]
[ 23.174275] [<ffffffffa010adb5>] ? mptspi_target_alloc+0x18c/0x1a1 [mptspi]
[ 23.174327] [<ffffffffa001fd47>] ? scsi_alloc_target+0x1e5/0x260 [scsi_mod]
[ 23.174376] [<ffffffffa0020fa5>] ? __scsi_scan_target+0x5a/0x593 [scsi_mod]
[ 23.174423] [<ffffffff8100f5e7>] ? __switch_to+0xd0/0x297
[ 23.174471] [<ffffffffa002152b>] ? scsi_scan_channel+0x4d/0x78 [scsi_mod]
[ 23.174520] [<ffffffffa0021633>] ? scsi_scan_host_selected+0xdd/0x11d [scsi_mod]
[ 23.174577] [<ffffffffa00216e4>] ? do_scan_async+0x0/0x13a [scsi_mod]
[ 23.174625] [<ffffffffa00216fa>] ? do_scan_async+0x16/0x13a [scsi_mod]
[ 23.174674] [<ffffffffa00216e4>] ? do_scan_async+0x0/0x13a [scsi_mod]
[ 23.174720] [<ffffffff81064819>] ? kthread+0x79/0x81
[ 23.174765] [<ffffffff81011baa>] ? child_rip+0xa/0x20
[ 23.174810] [<ffffffff810647a0>] ? kthread+0x0/0x81
[ 23.174854] [<ffffffff81011ba0>] ? child_rip+0x0/0x20
[ 23.174898] ---[ end trace 131c10636b3743aa ]---
This doesn't look comforting.
I'm also under the impression that the bug should be assigned to
linux-image instead of linux-headers... right?
Kind regards,
--Toni++
Reply to: