Linux Linux Kernel 2.6.33.4 is Out!

G

Gaurish

Level F
Hi,
2.6.33.4 brings couple of bug fixes and support for new hardware.

Changelog:
Linux 2.6.33.4
  • MIPS: Sibyte: Apply M3 workaround only on affected chip types and versions.
  • SCSI: Retry commands with UNIT_ATTENTION sense codes to fix ext3/ext4 I/O error
  • Enable retries for SYNCRONIZE_CACHE commands to fix I/O error
  • scsi_debug: virtual_gb ignores sector_size
  • SCSI: libiscsi: regression: fix header digest errors
  • SCSI: fix locking around blk_abort_request()
  • pxa/colibri: fix missing #include <mach/mfp.h> in colibri.h
  • cpuidle: Fix incorrect optimization
  • ACPI: sleep: init_set_sci_en_on_resume for Dell Studio 155x
  • power_meter: acpi_device_class "power_meter_resource" too long
  • ACPI: DMI init_set_sci_en_on_resume for multiple Lenovo ThinkPads
  • V4L/DVB: budget: Oops: "BUG: unable to handle kernel NULL pointer dereference"
  • md/raid6: Fix raid-6 read-error correction in degraded state
  • virtio: initialize earlier
  • md: restore ability of spare drives to spin down.
  • security: testing the wrong variable in create_by_name()
  • sparc64: Fix memory leak in pci_register_iommu_region().
  • sparc64: Adjust __raw_local_irq_save() to cooperate in NMIs.
  • sparc64: Use kstack_valid() in die_if_kernel().
  • sparc64: Fix hardirq tracing in trap return path.
  • sparc64: Fix PREEMPT_ACTIVE value.
  • sparc64: Use correct pt_regs in decode_access_size() error paths.
  • WAN: flush tx_queue in hdlc_ppp to prevent panic on rmmod hw_driver.
  • udp: fix for unicast RX path optimization
  • tun: orphan an skb on tx
  • tipc: Fix oops on send prior to entering networked mode (v3)
  • net: Fix oops from tcp_collapse() when using splice()
  • sctp: Fix oops when sending queued ASCONF chunks
  • sctp: fix to calc the INIT/INIT-ACK chunk length correctly is set
  • sctp: per_cpu variables should be in bh_disabled section
  • sctp: fix potential reference of a freed pointer
  • sctp: avoid irq lock inversion while call sk->sk_data_ready()
  • ipv6: Fix tcp_v6_send_response transport header setting.
  • ieee802154: Fix oops during ieee802154_sock_ioctl
  • cdc_ether: fix autosuspend for mbm devices
  • bnx2: Fix lost MSI-X problem on 5709 NICs.
  • powerpc: Reduce printk from pseries_mach_cpu_die()
  • powerpc: Move checks in pseries_mach_cpu_die()
  • powerpc: Reset kernel stack on cpu online from cede state
  • xfs: add a shrinker to background inode reclaim
  • tg3: Fix INTx fallback when MSI fails
  • skip sense logging for some ATA PASS-THROUGH cdbs
  • ath9k: reorder ieee80211_free_hw behind ath9k_uninit_hw to avoid oops
  • r8169: more broken register writes workaround
  • r8169: fix broken register writes
  • r8169: use correct barrier between cacheable and non-cacheable memory
  • kgdb: don't needlessly skip PAGE_USER test for Fsl booke
  • drivers/net/wireless/p54/txrx.c Fix off by one error
  • jfs: fix diAllocExt error in resizing filesystem
  • CRED: Fix a race in creds_are_invalid() in credentials debugging
  • initramfs: handle unrecognised decompressor when unpacking
  • ext4: correctly calculate number of blocks for fiemap
  • libata: Fix accesses at LBA28 boundary (old bug, but nasty) (v2)
  • PCI: Ensure we re-enable devices on resume
  • ALSA: hda: Use olpc-xo-1_5 quirk for Toshiba Satellite P500-PSPGSC-01800T
  • ALSA: hda: Use olpc-xo-1_5 quirk for Toshiba Satellite Pro T130-15F
  • ALSA: hda: Fix 0 dB for Packard Bell models using Conexant CX20549 (Venice)
  • ALSA: snd-meastro3: Ignore spurious HV interrupts during suspend / resume
  • ALSA: snd-meastro3: Add amp_gpio quirk for Compaq EVO N600C
  • ALSA: hda: Use ALC880_F1734 quirk for Fujitsu Siemens AMILO Xi 1526
  • ALSA: hda: Use STAC_DELL_M6_BOTH quirk for Dell Studio 1558
  • ALSA: hda: Use STAC_DELL_M6_BOTH quirk for Dell Studio XPS 1645
  • ALSA: hda - Add PCI quirk for HP dv6-1110ax.
  • ALSA: hda: Use LPIB quirk for DG965OT board version AAD63733-203
  • x86, k8 nb: Fix boot crash: enable k8_northbridges unconditionally on AMD systems
  • x86: Fix NULL pointer access in irq_force_complete_move() for Xen guests
  • x86: Disable large pages on CPUs with Atom erratum AAE44
  • x86-64: Clear a 64-bit FS/GS base on fork if selector is nonzero
  • edac, mce: Fix wrong mask and macro usage
  • p54pci: fix bugs in p54p_check_tx_ring
  • dm9601: fix phy/eeprom write routine
  • Revert "memory-hotplug: add 0x prefix to HEX block_size_bytes"
  • block: ensure jiffies wrap is handled correctly in blk_rq_timed_out_timer
  • serial: 8250_pnp - add Fujitsu Wacom device
  • raid6: fix recovery performance regression
  • perf: Fix resource leak in failure path of perf_event_open()
  • i2c: Fix probing of FSC hardware monitoring chips
  • Staging: hv: name network device ethX rather than sethX
  • Staging: hv: Fix up memory leak on HvCleanup
  • Staging: hv: Fix a bug affecting IPv6
  • NFS: rsize and wsize settings ignored on v4 mounts
  • nfs d_revalidate() is too trigger-happy with d_drop()
  • powernow-k8: Fix frequency reporting
  • ocfs2_dlmfs: Fix math error when reading LVB.
  • ocfs2: Compute metaecc for superblocks during online resize.
  • ocfs2: potential ERR_PTR dereference on error paths
  • ocfs2: Update VFS inode's id info after reflink.
  • USB: xhci: properly set endpoint context fields for periodic eps.
  • USB: xhci: properly set the "Mult" field of the endpoint context.
  • USB: OHCI: don't look at the root hub to get the number of ports
  • USB: don't choose configs with no interfaces
  • USB: fix testing the wrong variable in fs_create_by_name()
  • USB: don't read past config->interface[] if usb_control_msg() fails in usb_reset_configuration()
  • USB: Add id for HP ev2210 a.k.a Sierra MC5725 miniPCI-e Cell Modem.
  • USB: fix remote wakeup settings during system sleep
  • staging: usbip: Fix deadlock
  • sfc: Change falcon_probe_board() to fail for unsupported boards
  • sfc: Always close net device at the end of a disabling reset
  • sfc: Wait at most 10ms for the MC to finish reading out MAC statistics
  • keys: the request_key() syscall should link an existing key to the dest keyring
  • nfsd4: bug in read_buf
  • procfs: fix tid fdinfo
  • reiserfs: fix corruption during shrinking of xattrs
  • reiserfs: fix permissions on .reiserfs_priv
  • hugetlb: fix infinite loop in get_futex_key() when backed by huge pages
  • flex_array: fix the panic when calling flex_array_alloc() without __GFP_ZERO
  • mac80211: remove bogus TX agg state assignment
  • memcg: fix prepare migration
  • w1: w1 temp: fix negative termperature calculation
  • libata: ensure NCQ error result taskfile is fully initialized before returning it via qc->result_tf.
  • libata: fix locking around blk_abort_request()
  • md/raid5: fix previous patch.
  • md/raid5: allow for more than 2^31 chunks.
  • drm/i915: fix tiling limits for i915 class hw v2
  • drm/i915: Add initial bits for VGA modesetting bringup on Sandybridge.
  • p54usb: Add usbid for Corega CG-WLUSB2GT

Just updated to a new kernel, runs perfectly:D
 
Whats so special about this kernel compared to other releases??? Whats that new hardware they added support for?
 
vishalrao said:
Whats so special about this kernel compared to other releases??? Whats that new hardware they added support for?
Click to expand...

its bugfix release. I just upgraded, so posted it here.

About new hardware, read changelog
 
^ well, the changelog is Greek & Latin for most of the users ... all the users need not be techies !

if user needs to upgrade the kernel alone - why and how ?
 
^^Well first thing first, you never upgrade kernel, You always install new kernel replacing the older one. Means if somehow the new one doesn't meet the hardware expectations then you can always return back to the old one that worked for you.

Apart from that you can compile kernel from source , or wait for your distro update :)
 
seshu said:
^ well, the changelog is Greek & Latin for most of the users ... all the users need not be techies !

if user needs to upgrade the kernel alone - why and how ?
Click to expand...

If you can't understand the changelog I have posted. This might make more sense to you:

LinuxChanges - Linux Kernel Newbies

Q) Why one should we upgrade kernel?

Ans)

New Kernel brings support for new hardware & bug fixed. In this release, bugs in my network card driver(r8169) were fixed:



r8169: more broken register writes workaround

r8169: fix broken register writes

r8169: use correct barrier between cacheable and non-cacheable memory



Also, I had a lower memory corruption issue when resuming from standy, which has fixed as well.Likewise, Its Always be a good idea to run Latest kernel.

Q) How to get new Kernel

Ans)

you run a bleeding-edge distro like ArchLinux(which I do) or compile your kernel from http://Kernel.org. Your choice:)
 
Gaurish said:
New Kernel brings support for new hardware & bug fixed. In this release, bugs in my network card driver(r8169) were fixed:


r8169: more broken register writes workaround
r8169: fix broken register writes
r8169: use correct barrier between cacheable and non-cacheable memory


Also, I had a lower memory corruption issue when resuming from standy, which has fixed as well.Likewise, Its Always be a good idea to run Latest kernel.
Click to expand...

OK now I understand the point of this thread - it fixes bugs for your stuff :) I thot you would start posting a new thread for every kernel release like 2.6.33.5, then 2.6.33.6 and so no :P
 
Dark Star said:
^^Well first thing first, you never upgrade kernel, You always install new kernel replacing the older one. Means if somehow the new one doesn't meet the hardware expectations then you can always return back to the old one that worked for you.

Apart from that you can compile kernel from source , or wait for your distro update :)
Click to expand...

Thanks, I was to ask a question relating the kernel installation,
in an update Ubuntu installed a new kernel now when I boot i have two kernels with diff. ver. obviously ! was about to ask if I can/should remove the older one.
 
Dark Star said:
^^Only if the new one is working perfectly/.

Code: 
sudo apt-get autoremove
Click to expand...

apt-get autoremove will never remove old kernels (atleast in ubuntu, not sure about debian or other debian based distroes) unless you modify the /etc/apt/apt.conf.d/01autoremove file to remove them from exceptions..
 
Yondaime said:
Thanks, I was to ask a question relating the kernel installation,
in an update Ubuntu installed a new kernel now when I boot i have two kernels with diff. ver. obviously ! was about to ask if I can/should remove the older one.
Click to expand...

Here:

How to Delete Old Kernels in Ubuntu | ICT Learning

vishalrao said:
OK now I understand the point of this thread - it fixes bugs for your stuff :) I thot you would start posting a new thread for every kernel release like 2.6.33.5, then 2.6.33.6 and so no :P
Click to expand...

Lol, Yes. I won't post all the minor revision.
 
Back
Top