RE: 2.6.4-mm1

Nakajima, Jun
2004-03-14T08:05:11Z

I checked and tried several things, and I think CONFIG_PCI_USE_VECTOR is
a red herring. 2.6.4-mm1 did boot with CONFIG_PCI_USE_VECTOR = Y or N as
long as kernel preemption is disabled. It did not boot regardless of
CONFIG_PCI_USE_VECTOR if kernel preemption is enabled. I see the
complaints
bad: scheduling while atomic!
at various spots.

2.6.4 does not have this problem; kernel preemption seems to work fine.
I encourage people to check kernel preemption in 2.6.4-mm1.

Jun
>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
>owner@vger.kernel.org] On Behalf Of SUBODH SHRIVASTAVA
>Sent: Saturday, March 13, 2004 5:13 AM
>To: Andrew Morton
>Cc: linux-kernel@vger.kernel.org
>Subject: Re: 2.6.4-mm1
>
> --- Andrew Morton <akpm@osdl.org> wrote: > Subodh
>Shrivastava <subodh@btopenworld.com> wrote:
>> >
>> > I am able to boot vanilla kernel without the
>> following option enabled
>> >
>> > CONFIG_PCI_USE_VECTOR
>> >
>> > If i don't enable the above mentioned option
>> 2.6.4-mm1 won't boot on my
>>
>> ^^^^^ "do", I assume?
>
>Let me try to put it correct again.
>
>2.6.4 boots fine with the following option set as
>CONFIG_PCI_USE_VECTOR=N
>
>2.6.4-mm1 will not boot with the following option set
>as.
>CONFIG_PCI_USE_VECTOR=N
>2.6.4-mm1 will boot with the following option set as
>CONFIG_PCI_USE_VECTOR=Y
>
>>
>> > Laptop
>>
>> Is this unique to 2.6.4-mm1 or does 2.6.4 do the
>> same thing?
>Yes its unique to 2.6.4-mm1.
>
>Subodh
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/