kernel February 2011

kernel@lists.fedoraproject.org

11 participants
12 discussions

kernel-2.6.34.8-68.fc13 date for stable release
by Paoloni, Gabriele 28 Feb '11

28 Feb '11

Hi I saw this kernel still under testing and if I am not wrong it needs 2 Bodhi karmas to be released to stable. Is there anybody that could tell me if the release date is close or if it'll take a long time? Thanks Gabriele -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Tracking Rawhide's (released) kernel rpms through kernel.git
by Paul Bolle 28 Feb '11

28 Feb '11

Is it possible to track the (released) kernel rpms for Rawhide through kernel.git (git://pkgs.fedoraproject.org/kernel.git ) and build the (released) kernel rpms locally? The background is that I'd like to maintain a (small) set of patches on top of those releases and build my ".local" rpms from that repository. Currently I download (every now and then) the kernel SRPM with "yumdownloader --source", edit its specfile, rebuild it, etc., all by hand. That is often more work than I'd like it to be and error prone too. (Of course this is not Rawhide specific. One might want to do that for non-Rawhide releases too.) Paul Bolle

5 6

Re: 2.6.18 netlink_kernel_create() always returns NULL
by Kyle McMartin 22 Feb '11

22 Feb '11

On Tue, Feb 22, 2011 at 11:57:07PM +0800, 老杨 wrote: > I feel sad for that. My question is suggested to post here from centos > list because there has no such lists relevant to kernel. > For this problem,is there other reasons besides version? > If CentOS cannot provide you the support you need, maybe you shouldn't use CentOS. Posting your question here because they are incapable of providing you support is entirely inappropriate, like someone posting a question about Ubuntu on this list. --Kyle

1 0

2.6.18 netlink_kernel_create() always returns NULL
by YANG 22 Feb '11

22 Feb '11

My code fragment is below: "nl_sk = netlink_kernel_create(16, 0, nl_data_ready, THIS_MODULE);" It can be "make" and "insmod" correctly. But error mesage is printed into log. It indicates the netlink_kernel_create() returns NULL. Once I change the firt parameter to another(<32 && >16), system crash when I execute insmod. Is the protocol ID occupied? Why can't use another and how to define a new ID? I have tried to update net_link.h but fail also.

2 1

[PATCH 2.6.35] iwl3945: remove plcp check
by Stanislaw Gruszka 21 Feb '11

21 Feb '11

commit c91d01556f52255a31575be0cb1981c92a2a5028 upstream. Patch fixes: https://bugzilla.redhat.com/show_bug.cgi?id=654599 Many users report very low speed problem on 3945 devices, this patch fixes problem, but only for some of them. For unknown reason, sometimes after hw scanning, device is not able to receive frames at high rate. Since plcp health check may request hw scan to "reset radio", performance problem start to be observable after update kernel to .35, where plcp check was introduced. Bug reporter confirmed that removing plcp check fixed problem for him. Reported-and-tested-by: SilvioTO <silviotoya(a)yahoo.it> Acked-by: Wey-Yi Guy <wey-yi.w.guy(a)intel.com> Signed-off-by: Stanislaw Gruszka <sgruszka(a)redhat.com> --- drivers/net/wireless/iwlwifi/iwl-3945.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/net/wireless/iwlwifi/iwl-3945.c b/drivers/net/wireless/iwlwifi/iwl-3945.c index 2a9480d..7b4fc94 100644 --- a/drivers/net/wireless/iwlwifi/iwl-3945.c +++ b/drivers/net/wireless/iwlwifi/iwl-3945.c @@ -2837,7 +2837,6 @@ static struct iwl_lib_ops iwl3945_lib = { .config_ap = iwl3945_config_ap, .manage_ibss_station = iwl3945_manage_ibss_station, .recover_from_tx_stall = iwl_bg_monitor_recover, - .check_plcp_health = iwl3945_good_plcp_health, .debugfs_ops = { .rx_stats_read = iwl3945_ucode_rx_stats_read, -- 1.7.1

1 0

Re: [PATCH 0/3] [RFC] Print three messages at KERN_WARNING level
by Paul Bolle 10 Feb '11

10 Feb '11

On Thu, 2011-02-03 at 23:07 +0100, Paul Bolle wrote: > I've been entirely unable to rpmbuild a > kernel for i686 _only_, which just might keep the rpmbuild time at a > sane level. Does anyone know how to get Fedora's kernel.spec file to do > _only_ that? I've already managed to do that. Just to help me remember (or rediscover) this: rpmbuild -bb --target=i686 --with baseonly --without perf --without debuginfo $SPECS/kernel.spec comes close. (It also generates the kernel-devel and kernel-headers packages, but that doesn't seem to cost much time). Paul

1 0

[PATCH 2/3] [RFC] Print a watchdog message at KERN_WARNING level
by Paul Bolle 09 Feb '11

09 Feb '11

For messages like NMI watchdog disabled for cpu0: unable to create perf event: -95 KERN_WARNING seems to be more appropriate than KERN_ERR. (Main benefit of the KERN_WARNING level is that Fedora's plymouth bootsplash should now hide them.) Signed-off-by: Paul Bolle <pebolle(a)tiscali.nl> --- Yes, the changed line is getting very long, but that is apparently not a problem in this file. kernel/watchdog.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/kernel/watchdog.c b/kernel/watchdog.c index f37f974..1c2ffe1 100644 --- a/kernel/watchdog.c +++ b/kernel/watchdog.c @@ -363,7 +363,7 @@ static int watchdog_nmi_enable(int cpu) goto out_save; } - printk(KERN_ERR "NMI watchdog disabled for cpu%i: unable to create perf event: %ld\n", + printk(KERN_WARNING "NMI watchdog disabled for cpu%i: unable to create perf event: %ld\n", cpu, PTR_ERR(event)); return PTR_ERR(event); -- 1.7.4

2 9

Update needed to Fedora13 Kernel Source
by Paoloni, Gabriele 08 Feb '11

08 Feb '11

In the Fedora13 Kernel Source there is an issue with the Intel AGP driver that does not allow the X server to start on some Sandybrige platform. The issue has been solved in the Vanilla 2.6.35 according to the commits inline below and as consequence also in the latest updated Fedora14 kernel. http://www.spinics.net/lists/stable-commits/msg08831.html http://www.spinics.net/lists/stable-commits/msg08832.html http://www.spinics.net/lists/stable-commits/msg08833.html For compatibility and reliability reasons we are working on Fedora13 and we would like to have such changes included in the Fedora 13 Kernel Source as well. Is it possible to have it integrated in the Fedora13 branch? When is the expected release date? Thanks and Regards Gabriele Paoloni Find inline below the patch generated against the Fedora13 2.6.34.7 Kernel ************************************************************************************************************ ************************************************************************************************************ Signed-off-by: Gabriele Paoloni <gabriele.paoloni(a)intel.com<mailto:gabriele.paoloni@intel.com>> <paoloni.gabriele(a)gmail.com<mailto:paoloni.gabriele@gmail.com>> diff -urN a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c --- a/drivers/char/agp/intel-agp.c 2011-02-07 19:48:44.463536867 +0000 +++ b/drivers/char/agp/intel-agp.c 2011-02-07 19:46:35.656668212 +0000 @@ -815,17 +815,27 @@ "HD Graphics", NULL, &intel_i965_driver }, { PCI_DEVICE_ID_INTEL_IRONLAKE_MC2_HB, PCI_DEVICE_ID_INTEL_IRONLAKE_M_IG, "HD Graphics", NULL, &intel_i965_driver }, - { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_IG, - "Sandybridge", NULL, &intel_i965_driver }, - { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_IG, - "Sandybridge", NULL, &intel_i965_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT1_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT2_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT2_PLUS_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT1_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT2_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT2_PLUS_IG, + "Sandybridge", NULL, &intel_gen6_driver }, + { PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_HB, PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_IG, + "Sandybridge", NULL, &intel_gen6_driver }, { 0, 0, NULL, NULL, NULL } }; static int __devinit intel_gmch_probe(struct pci_dev *pdev, struct agp_bridge_data *bridge) { - int i; + int i, mask; bridge->driver = NULL; for (i = 0; intel_agp_chipsets[i].name != NULL; i++) { @@ -845,14 +855,19 @@ dev_info(&pdev->dev, "Intel %s Chipset\n", intel_agp_chipsets[i].name); - if (bridge->driver->mask_memory == intel_i965_mask_memory) { - if (pci_set_dma_mask(intel_private.pcidev, DMA_BIT_MASK(36))) - dev_err(&intel_private.pcidev->dev, - "set gfx device dma mask 36bit failed!\n"); - else - pci_set_consistent_dma_mask(intel_private.pcidev, - DMA_BIT_MASK(36)); - } + if (bridge->driver->mask_memory == intel_gen6_mask_memory) + mask = 40; + else if (bridge->driver->mask_memory == intel_i965_mask_memory) + mask = 36; + else + mask = 32; + + if (pci_set_dma_mask(intel_private.pcidev, DMA_BIT_MASK(mask))) + dev_err(&intel_private.pcidev->dev, + "set gfx device dma mask %d-bit failed!\n", mask); + else + pci_set_consistent_dma_mask(intel_private.pcidev, + DMA_BIT_MASK(mask)); return 1; } @@ -1036,6 +1051,7 @@ ID(PCI_DEVICE_ID_INTEL_IRONLAKE_MC2_HB), ID(PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB), ID(PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB), + ID(PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_HB), { } }; diff -urN a/drivers/char/agp/intel-agp.h b/drivers/char/agp/intel-agp.h --- a/drivers/char/agp/intel-agp.h 2011-02-07 19:48:44.463536867 +0000 +++ b/drivers/char/agp/intel-agp.h 2011-02-07 19:46:37.030332262 +0000 @@ -194,10 +194,17 @@ #define PCI_DEVICE_ID_INTEL_IRONLAKE_MA_HB 0x0062 #define PCI_DEVICE_ID_INTEL_IRONLAKE_MC2_HB 0x006a #define PCI_DEVICE_ID_INTEL_IRONLAKE_M_IG 0x0046 -#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB 0x0100 -#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_IG 0x0102 -#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB 0x0104 -#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_IG 0x0106 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB 0x0100 /* Desktop */ +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT1_IG 0x0102 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT2_IG 0x0112 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_GT2_PLUS_IG 0x0122 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB 0x0104 /* Mobile */ +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT1_IG 0x0106 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT2_IG 0x0116 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_GT2_PLUS_IG 0x0126 +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_HB 0x0108 /* Server */ +#define PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_IG 0x010A + /* cover 915 and 945 variants */ #define IS_I915 (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_E7221_HB || \ @@ -224,7 +231,8 @@ agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_HB) #define IS_SNB (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB || \ - agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB) + agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB || \ + agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_HB) #define IS_G4X (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_EAGLELAKE_HB || \ agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q45_HB || \ diff -urN a/drivers/char/agp/intel-gtt.c b/drivers/char/agp/intel-gtt.c --- a/drivers/char/agp/intel-gtt.c 2011-02-07 19:48:44.620861708 +0000 +++ b/drivers/char/agp/intel-gtt.c 2011-02-07 19:46:38.141107459 +0000 @@ -581,8 +581,7 @@ gtt_entries = 0; break; } - } else if (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB || - agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB) { + } else if (IS_SNB) { /* * SandyBridge has new memory control reg at 0x50.w */ @@ -1309,6 +1308,16 @@ return addr | bridge->driver->masks[type].mask; } +static unsigned long intel_gen6_mask_memory(struct agp_bridge_data *bridge, + dma_addr_t addr, int type) +{ + /* gen6 has bit11-4 for physical addr bit39-32 */ + addr |= (addr >> 28) & 0xff0; + + /* Type checking must be done elsewhere */ + return addr | bridge->driver->masks[type].mask; } + static void intel_i965_get_gtt_range(int *gtt_offset, int *gtt_size) { u16 snb_gmch_ctl; @@ -1328,6 +1337,7 @@ break; case PCI_DEVICE_ID_INTEL_SANDYBRIDGE_HB: case PCI_DEVICE_ID_INTEL_SANDYBRIDGE_M_HB: + case PCI_DEVICE_ID_INTEL_SANDYBRIDGE_S_HB: *gtt_offset = MB(2); pci_read_config_word(intel_private.pcidev, SNB_GMCH_CTRL, &snb_gmch_ctl); @@ -1488,12 +1498,45 @@ .owner = THIS_MODULE, .aperture_sizes = intel_i830_sizes, .size_type = FIXED_APER_SIZE, + .num_aperture_sizes = 4, + .needs_scratch_page = true, + .configure = intel_i9xx_configure, + .fetch_size = intel_i9xx_fetch_size, + .cleanup = intel_i915_cleanup, + .mask_memory = intel_i965_mask_memory, + .masks = intel_i810_masks, + .agp_enable = intel_i810_agp_enable, + .cache_flush = global_cache_flush, + .create_gatt_table = intel_i965_create_gatt_table, + .free_gatt_table = intel_i830_free_gatt_table, + .insert_memory = intel_i915_insert_entries, + .remove_memory = intel_i915_remove_entries, + .alloc_by_type = intel_i830_alloc_by_type, + .free_by_type = intel_i810_free_by_type, + .agp_alloc_page = agp_generic_alloc_page, + .agp_alloc_pages = agp_generic_alloc_pages, + .agp_destroy_page = agp_generic_destroy_page, + .agp_destroy_pages = agp_generic_destroy_pages, + .agp_type_to_mask_type = intel_i830_type_to_mask_type, + .chipset_flush = intel_i915_chipset_flush, +#ifdef USE_PCI_DMA_API + .agp_map_page = intel_agp_map_page, + .agp_unmap_page = intel_agp_unmap_page, + .agp_map_memory = intel_agp_map_memory, + .agp_unmap_memory = intel_agp_unmap_memory, +#endif +}; + +static const struct agp_bridge_driver intel_gen6_driver = { + .owner = THIS_MODULE, + .aperture_sizes = intel_i830_sizes, + .size_type = FIXED_APER_SIZE, .num_aperture_sizes = 4, .needs_scratch_page = true, .configure = intel_i9xx_configure, .fetch_size = intel_i9xx_fetch_size, .cleanup = intel_i915_cleanup, - .mask_memory = intel_i965_mask_memory, + .mask_memory = intel_gen6_mask_memory, .masks = intel_i810_masks, .agp_enable = intel_i810_agp_enable, .cache_flush = global_cache_flush, diff -urN a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c --- a/drivers/gpu/drm/i915/i915_drv.c 2011-02-07 19:48:44.473799207 +0000 +++ b/drivers/gpu/drm/i915/i915_drv.c 2011-02-07 19:47:18.418493437 +0000 @@ -180,7 +180,12 @@ INTEL_VGA_DEVICE(0x0042, &intel_ironlake_d_info), INTEL_VGA_DEVICE(0x0046, &intel_ironlake_m_info), INTEL_VGA_DEVICE(0x0102, &intel_sandybridge_d_info), + INTEL_VGA_DEVICE(0x0112, &intel_sandybridge_d_info), + INTEL_VGA_DEVICE(0x0122, &intel_sandybridge_d_info), INTEL_VGA_DEVICE(0x0106, &intel_sandybridge_m_info), + INTEL_VGA_DEVICE(0x0116, &intel_sandybridge_m_info), + INTEL_VGA_DEVICE(0x0126, &intel_sandybridge_m_info), + INTEL_VGA_DEVICE(0x010A, &intel_sandybridge_d_info), {0, 0, 0} }; -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 1

[PATCH 1/3] [RFC] Print a device-tree message at KERN_WARNING level
by Paul Bolle 04 Feb '11

04 Feb '11

For the message /proc/device-tree: can't find root KERN_WARNING seems to be more appropriate than KERN_ERR. (Main benefit of the KERN_WARNING level is that Fedora's plymouth bootsplash should now hide it.) Signed-off-by: Paul Bolle <pebolle(a)tiscali.nl> --- fs/proc/proc_devtree.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c index d9396a4..71dd779 100644 --- a/fs/proc/proc_devtree.c +++ b/fs/proc/proc_devtree.c @@ -233,7 +233,7 @@ void __init proc_device_tree_init(void) return; root = of_find_node_by_path("/"); if (root == NULL) { - printk(KERN_ERR "/proc/device-tree: can't find root\n"); + printk(KERN_WARNING "/proc/device-tree: can't find root\n"); return; } proc_device_tree_add_node(root, proc_device_tree); -- 1.7.4

3 5

[PATCH 3/3] [RFC] Print a IOAPIC message at KERN_WARNING level
by Paul Bolle 03 Feb '11

03 Feb '11

For messages like ERROR: Unable to locate IOAPIC for GSI 13 KERN_WARNING seems to be more appropriate than KERN_ERR. (Main benefit of the KERN_WARNING level is that Fedora's plymouth bootsplash should now hide them.) Signed-off-by: Paul Bolle <pebolle(a)tiscali.nl> --- arch/x86/kernel/apic/io_apic.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c index 697dc34..72f91be 100644 --- a/arch/x86/kernel/apic/io_apic.c +++ b/arch/x86/kernel/apic/io_apic.c @@ -4009,7 +4009,7 @@ int mp_find_ioapic(u32 gsi) return i; } - printk(KERN_ERR "ERROR: Unable to locate IOAPIC for GSI %d\n", gsi); + printk(KERN_WARNING "ERROR: Unable to locate IOAPIC for GSI %d\n", gsi); return -1; } -- 1.7.4

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2011