Re: 2.6.14-rc4: dma_timer_expiry [was 2.6.13-rc2 hangs at boot]

From: Mikael Pettersson
Date: Fri Jul 29 2005 - 08:27:20 EST


On Fri, 29 Jul 2005 11:35:09 +0300 (EEST), Tero Roponen wrote:
>On Fri, 29 Jul 2005, Andrew Morton wrote:
>
>> Tero Roponen <teanropo@xxxxxxxxx> wrote:
>> >
>> > Hi,
>> >
>> > I just tested 2.6.13-rc4. At boot it prints:
>> > "dma_timer_expiry: dma status == 0x61" many times.
>> > That's the same problem as in 2.6.13-rc2.
>> >
>> > If I apply the following patch, everything seems to be fine.
>> > I'm not sure if this is the right thing to do, but it works for me.
>> >
>> > -
>> > Tero Roponen
>> >
>> >
>> > --- 2.6.13-rc2/drivers/pci/setup-bus.c Thu Jul 7 01:32:43 2005
>> > +++ linux/drivers/pci/setup-bus.c Fri Jul 8 10:25:20 2005
>> > @@ -40,8 +40,8 @@
>> > * FIXME: IO should be max 256 bytes. However, since we may
>> > * have a P2P bridge below a cardbus bridge, we need 4K.
>> > */
>> > -#define CARDBUS_IO_SIZE (4096)
>> > -#define CARDBUS_MEM_SIZE (32*1024*1024)
>> > +#define CARDBUS_IO_SIZE (256)
>> > +#define CARDBUS_MEM_SIZE (32*1024*1024)
>> >
>>
>> hm, how did you come up with that fix? Those numbers have been like that
>> since forever.
>>
>> What's the latest 2.6 kernel which worked OK?
>>
>> Would it be possible for you to generate the `dmesg -s 100000' output for
>> both good and bad kernels, see what the differences are?
>>
>> Thanks.
>
>Hi,
>
>that patch was from Ivan Kokshaysky (http://lkml.org/lkml/2005/7/8/25)
>
>My original report is here: http://lkml.org/lkml/2005/7/6/174

The PCI changes in 2.6.13-rc2 caused a number of machines to
hang at boot, including my Athlon64 laptop. It was found that
reducing CARDBUS_IO_SIZE to 256 eliminated the hangs.

The LKML archives have the details.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/