kernel 2.6.30.1

[Antonio Olivares]

> > I hear you and I am applying the patch from 2.6.30 to
> 2.6.30.1 as of now.
> > I know your frustrations, but Fedora is staying a bit
> behind as of now
> > because apparently many things were changed from
> 2.6.29 to 2.6.30?
> >
> I think that sums it up, with any new release there will be
> a surge of issues, most minor, as new users migrate. Better
> to fix most of these before adding the features of a new
> kernel to the mix.
> 
> > I don't know the exact reasons, but I understand where
> you are coming from
> > and I agree with you. Is Fedora countering the saying
> "Latest and Greatest"? I
> > knowthat on rawhide a 2.6.31.rcX kernel is being run,
> that is where the latest
> > and greatest always is, but Fedora Stable should not
> be so far behind? Should
> > it?
> > 
> Remember that "latest" and "greatest" are not synonyms,
> there were many changes in 2.6.30, and a little time for
> shakeout is a good thing. People are just getting used to
> ext4, adding a number of new filesystem types is likely to
> cause more questions, and probably will mean updates of the
> utilities for the filesystems as well.
> 
> I think Fedora is moving at the right speed on this one,
> you can build your own, or pull from testing, or rawhide, or
> koji, depending on your tolerance for learning experiences.
> 
> -- Bill Davidsen <davidsen at tmr.com>
>   "We have more to fear from the bungling of the
> incompetent than from
> the machinations of the wicked."  - from Slashdot
> 
> -- fedora-list mailing list


Just as an example, I tried to update to 2.6.30.1 kernel on a Fedora 11 system and I get the following:


[olivares at black-amd64-home linux-2.6.30]$ cat /etc/fedora-release 
Fedora release 11 (Leonidas)
[olivares at black-amd64-home linux-2.6.30]$ uname -r
2.6.30

.......


include/linux/backing-dev.h:205: warning: ‘struct page’ declared inside parameter list
include/linux/backing-dev.h:205: warning: its scope is only this definition or declaration, which is probably not what you want
In file included from include/linux/blkdev.h:17,
                 from include/scsi/scsi_device.h:9,
                 from drivers/scsi/qla4xxx/ql4_def.h:32,
                 from drivers/scsi/qla4xxx/ql4_init.c:10:
include/linux/bio.h: In function ‘bio_data’:
include/linux/bio.h:232: warning: passing argument 1 of ‘lowmem_page_address’ from incompatible pointer type
include/linux/mm.h:597: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’
In file included from include/linux/blkdev.h:17,
                 from include/scsi/scsi_device.h:9,
                 from drivers/scsi/qla4xxx/ql4_def.h:32,
                 from drivers/scsi/qla4xxx/ql4_init.c:10:
include/linux/bio.h: In function ‘__bio_kmap_irq’:
include/linux/bio.h:492: warning: passing argument 1 of ‘lowmem_page_address’ from incompatible pointer type
include/linux/mm.h:597: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’
In file included from include/scsi/scsi_device.h:9,
                 from drivers/scsi/qla4xxx/ql4_def.h:32,
                 from drivers/scsi/qla4xxx/ql4_init.c:10:
include/linux/blkdev.h: In function ‘blk_run_backing_dev’:
include/linux/blkdev.h:825: warning: passing argument 2 of ‘bdi->unplug_io_fn’ from incompatible pointer type
include/linux/blkdev.h:825: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’
In file included from include/scsi/scsi_device.h:9,
                 from drivers/scsi/qla4xxx/ql4_def.h:32,
                 from drivers/scsi/qla4xxx/ql4_init.c:10:
include/linux/blkdev.h: In function ‘put_dev_sector’:
include/linux/blkdev.h:1019: warning: passing argument 1 of ‘put_page’ from incompatible pointer type
include/linux/mm.h:323: note: expected ‘struct ��ދ� *’ but argument is of type ‘struct page *’
drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_free_ddb_list’:
drivers/scsi/qla4xxx/ql4_init.c:81: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_get_ddb_entry’:
drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c:344: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c: In function ‘qla4xxx_reinitialize_ddb_list’:
drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c:800: error: ‘struct list_head’ has no member named ‘next’
drivers/scsi/qla4xxx/ql4_init.c:1250: confused by earlier errors, bailing out
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [drivers/scsi/qla4xxx/ql4_init.o] Error 1
make[2]: *** [drivers/scsi/qla4xxx] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
[olivares at black-amd64-home linux-2.6.30]$ 


I have not encountered these before, so I will see what I can do about it?  

Regards,

Antonio