Bug#703082: linux: Please change path in which dtb is installed
Source: linux Version: 3.8.2-1~experimental.1 Severity: normal Tags: patch Dear Maintainer, From linux 3.8, the directory where dtb is created was changed. Therefore, we need to change the script for package building. I created a patch which fix this problem. Please check and apply. Best regards, Nobuhiro -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/rules.real b/debian/rules.real index f4b61f5..2b77891 100644 --- a/debian/rules.real +++ b/debian/rules.real @@ -384,7 +384,7 @@ install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: DTB_INSTALL_DIR = /u install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_image: install -m644 '$(DIR)/arch/$(KERNEL_ARCH)/boot/zImage' $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION) +$(MAKE_CLEAN) -C $(DIR) dtbs - shopt -s nullglob ; for i in $(DIR)/arch/arm/boot/*.dtb ; do \ + shopt -s nullglob ; for i in $(DIR)/arch/arm/boot/dts/*.dtb ; do \ install -D -m644 $$i '$(PACKAGE_DIR)'/'$(DTB_INSTALL_DIR)'/$$(basename $$i) ; \ done endif -- 1.7.10.4
Bug#703083: linux: Please add support armel/Plat'Home OpenBlocks A6
Package: linux Version: 3.8.2-1~experimental.1 Severity: wishlist Tags: patch Dear Maintainer, Please add support Plat'Home OpenBlocks A6 of armel. This board was supported from 3.8. I attached the patch which supports this. Please check and apply. Best regards, Nobuhiro -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff --git a/debian/config/armel/config.kirkwood b/debian/config/armel/config.kirkwood index 1e8790a..0d07c9a 100644 --- a/debian/config/armel/config.kirkwood +++ b/debian/config/armel/config.kirkwood @@ -60,6 +60,7 @@ CONFIG_MACH_GURUPLUG=y CONFIG_ARCH_KIRKWOOD_DT=y CONFIG_MACH_DREAMPLUG_DT=y CONFIG_MACH_ICONNECT_DT=y +CONFIG_MACH_OPENBLOCKS_A6_DT=y CONFIG_MACH_TS219=y CONFIG_MACH_TS41X=y CONFIG_MACH_DOCKSTAR=y
Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive
On 05/03/13 09:36, Chris Boot wrote: On 03/03/13 01:56, Ben Hutchings wrote: Control: tag -1 moreinfo fixed-upstream On Thu, 2013-02-28 at 15:28 +, Chris Boot wrote: We are also seeing this on an NFS server hosing home directories for a fairly large deployment of Debian desktop systems. The symptoms and perf top agree perfectly with what the reporter is experiencing. Please consider backporting said patch to the 3.2 kernel for wheezy/squeeze-backports. Please test the attached backport as explained here: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official Hi Ben, I have been testing a 3.2 kernel with both the patch you backported as well as 64a284d07c7d84299a90826950079a8ef11e8204 from upstream (nfsd4: maintain one seqid stream per (lockowner, file)). These patches together appear to have resolved the issues our client has been seeing, though this is not running in a production environment just yet. I think the other patch (64a284d07c7d84299a90826950079a8ef11e8204) is also quite important in resolving this problem, as it reduces the number of entries in the lockowner hash table. Would this be a patch you would entertain to backport as well? Hi Ben, Did you have any further thoughts about the other patch I mentioned above? I still don't have this running in a production environment, but the testing I have performed looks good with both patches applied. Best regards, Chris -- |Chris Boot |Tiger Computing Ltd |Linux for Business | |Tel: 033 0088 1511 |Web: http://www.tiger-computing.co.uk | |Registered in England. Company number: 3389961 |Registered address: Wyastone Business Park, | Wyastone Leys, Monmouth, NP25 3SR -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5143494a.8020...@tiger-computing.co.uk
Bug#702625: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#702625: linux-source-3.2: Custom kernel built from Debian source gives a package with huge size)
Hello Ben, Thanks for your explanation :-) You could perhaps add a note in the Debian Kernel handbook about this point ? regards, Fred. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130315131011.6d154dd3@joubarbe.local
Bug#703082: linux: Please change path in which dtb is installed
On Fri, 2013-03-15 at 09:22 +0900, Nobuhiro Iwamatsu wrote: From linux 3.8, the directory where dtb is created was changed. Therefore, we need to change the script for package building. I created a patch which fix this problem. Please check and apply. This upstream change was 499cd8298628 ARM: dt: change .dtb build rules to build in dts directory. The suggested fix seems correct to me. Ian. -- Ian Campbell Many are called, few are chosen. Fewer still get to do the choosing. signature.asc Description: This is a digitally signed message part
Bug#703082: linux: Please change path in which dtb is installed
On Fri, 2013-03-15 at 20:29 +, Ian Campbell wrote: On Fri, 2013-03-15 at 09:22 +0900, Nobuhiro Iwamatsu wrote: From linux 3.8, the directory where dtb is created was changed. Therefore, we need to change the script for package building. I created a patch which fix this problem. Please check and apply. This upstream change was 499cd8298628 ARM: dt: change .dtb build rules to build in dts directory. The suggested fix seems correct to me. Please can one of you apply this, then? Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#703083: linux: Please add support armel/Plat'Home OpenBlocks A6
On Fri, 2013-03-15 at 09:35 +0900, Nobuhiro Iwamatsu wrote: Package: linux Version: 3.8.2-1~experimental.1 Severity: wishlist Tags: patch Dear Maintainer, Please add support Plat'Home OpenBlocks A6 of armel. This board was supported from 3.8. I attached the patch which supports this. Please check and apply. You can apply this yourself! Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Bug#702625: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#702625: linux-source-3.2: Custom kernel built from Debian source gives a package with huge size)
On Fri, 2013-03-15 at 13:10 +0100, Fred wrote: Hello Ben, Thanks for your explanation :-) You could perhaps add a note in the Debian Kernel handbook about this point ? Jonathan Nieder already did that in version 1.0.15. But I forgot to update the web site! I've just fixed that. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part
Processed: your mail
Processing commands for cont...@bugs.debian.org: forwarded 702885 https://bugzilla.kernel.org/show_bug.cgi?id=47941 Bug #702885 [src:linux] linux-image-3.8-trunk-amd64: Samsung NP900X3C display does not resume from suspend Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=47941'. End of message, stopping processing here. Please contact me if you need assistance. -- 702885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.136338881232766.transcr...@bugs.debian.org
Bug#703126: linux-image-3.2.0-4-686-pae: Suspend fails with radeon firmware and modeset=0
Package: src:linux Version: 3.2.39-2 Severity: normal Dear kernel maintainers, after updating from Squeeze to Wheezy, suspend stopped working on my Acer with Radeon Mobility X700. Suspending seems ok, but wakeup not: screen stays blank, no reaction to keys, cold reset needed. The firmware loads ok. Tested also with radeon.modeset=0 option, but does not help. Must stress that the suspend worked without a glitch for years with Squeeze kernels. More info will be provided if needed. All the best, Harri K. -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=2c2f6dd9-965c-474b-b091-5e70cf3d4879 ro radeon.modeset=0 ** Not tainted ** Kernel log: [ 10.267536] yenta_cardbus :06:09.0: O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the yenta_socket parameter 'o2_speedup=off' [ 10.325780] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [ 10.325839] ipw2200: Copyright(c) 2003-2006 Intel Corporation [ 10.584219] ACPI: Battery Slot [BAT1] (battery present) [ 10.584302] ACPI: Battery Slot [BAT2] (battery absent) [ 10.640929] NET: Registered protocol family 23 [ 10.712901] yenta_cardbus :06:09.0: ISA IRQ mask 0x0c38, PCI irq 18 [ 10.712966] yenta_cardbus :06:09.0: Socket status: 3006 [ 10.713031] yenta_cardbus :06:09.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] [ 10.713098] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: excluding 0x3000-0x30ff 0x3400-0x34ff [ 10.719335] yenta_cardbus :06:09.0: pcmcia: parent PCI bridge window: [mem 0xc820-0xc82f] [ 10.719402] pcmcia_socket pcmcia_socket0: cs: memory probe 0xc820-0xc82f: excluding 0xc820-0xc821 [ 10.719619] yenta_cardbus :06:09.0: pcmcia: parent PCI bridge window: [mem 0x5000-0x53ff pref] [ 10.719686] pcmcia_socket pcmcia_socket0: cs: memory probe 0x5000-0x53ff: excluding 0x5000-0x53ff [ 10.721484] yenta_cardbus :06:09.1: no bus associated! (try 'pci=assign-busses') [ 10.721567] yenta_cardbus :06:09.3: no bus associated! (try 'pci=assign-busses') [ 10.722177] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection [ 10.726950] nsc-ircc, chip-init [ 10.727017] nsc-ircc, Found chip at base=0x164e [ 10.727103] nsc-ircc, driver loaded (Dag Brattli) [ 10.727175] nsc_ircc_open(), can't get iobase of 0x2f8 [ 10.727269] nsc-ircc, Found chip at base=0x164e [ 10.727355] nsc-ircc, driver loaded (Dag Brattli) [ 10.727422] nsc_ircc_open(), can't get iobase of 0x2f8 [ 10.727731] nsc-ircc 00:06: disabled [ 11.010685] psmouse serio4: synaptics: Touchpad model: 1, fw: 5.9, id: 0x126eb1, caps: 0xa04713/0x4000/0x0 [ 11.056876] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input7 [ 11.062839] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x37f [ 11.065021] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7 [ 11.066014] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 11.066768] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 11.067593] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc 0xe-0xf [ 11.067883] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [ 11.068086] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: clean. [ 11.068266] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 11.096807] ipw2200 :06:03.0: firmware: agent loaded ipw2200-bss.fw into memory [ 11.241957] cfg80211: failed to add phy80211 symlink to netdev! [ 11.242096] ipw2200: Detected geography ZZE (13 802.11bg channels, 19 802.11a channels) [ 11.512546] snd_hda_intel :00:1b.0: irq 300 for MSI/MSI-X [ 11.512605] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 11.644082] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input8 [ 13.356301] Adding 1951860k swap on /dev/sda5. Priority:-1 extents:1 across:1951860k [ 14.031753] EXT3-fs (sda7): using internal journal [ 14.668719] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 14.668782] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 15.437880] usbcore: registered new interface driver cdc_ether [ 15.487490] usbcore: registered new interface driver zaurus [ 29.833802] kjournald starting. Commit interval 5 seconds [ 29.834150] EXT3-fs (sda8): using internal journal [ 29.834209] EXT3-fs (sda8): mounted filesystem with ordered data mode [ 29.950458] kjournald starting. Commit interval 5 seconds [ 29.950959] EXT3-fs
Hang on NFS storage machines
Hi, We use debian for a number of machines in our storage infrastructure and we have recently been seeing a number of hangs. We primary notice this by seeing nfsd processes locking up and then a hung task killer going wild. We finally managed to get a trace last night - its pasted below: We did not see this crash under 2.6.39 back port however this kernel spontaneously rebooted at ~200 days uptime (we had about 3/4 of our infra reboot in a few weeks. It was not a good time for our ops teams). I would be grateful if anybody who could help me narrow this down would jump in and help with requests for further info, or provide further advice. [11309697.466397] [ cut here ] [11309697.466556] WARNING: at /build/buildd-linux_3.2.23-1~bpo60+2-amd64-oLufer/linux-3.2.23/fs/jbd2/journal.c:507 __jbd2_log_start_commit+0x7e/0x8c [jbd2]() [11309697.40] Hardware name: X8DT6 [11309697.466728] JBD2: bad log_start_commit: 2205591757 2205591757 14613566 0 [11309697.466798] Modules linked in: netconsole autofs4 8021q garp bridge stp nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bonding tcp_htcp ext4 jbd2 crc16 configfs loop ohci_hcd tpm_tis tpm i7core_edac i2c_i801 snd_pcm snd_timer snd soundcore edac_core i2c_core ioatdma tpm_bios snd_page_alloc coretemp crc32c_intel psmouse pcspkr joydev evdev acpi_cpufreq mperf processor serio_raw button thermal_sys ext3 jbd mbcache usbhid hid sd_mod ses enclosure crc_t10dif uhci_hcd ahci libahci libata igb ehci_hcd e1000e usbcore dca megaraid_sas usb_common scsi_mod [last unloaded: netconsole] [11309697.470190] Pid: 62, comm: kswapd0 Not tainted 3.2.0-0.bpo.3-amd64 #1 [11309697.470261] Call Trace: [11309697.470329] [810498a8] ? warn_slowpath_common+0x78/0x8c [11309697.470399] [8104995a] ? warn_slowpath_fmt+0x45/0x4a [11309697.470471] [a01cabad] ? __jbd2_log_start_commit+0x7e/0x8c [jbd2] [11309697.470558] [a01cac83] ? jbd2_log_start_commit+0x21/0x2f [jbd2] [11309697.470634] [a02dee7a] ? ext4_evict_inode+0x86/0x2d1 [ext4] [11309697.470707] [81119626] ? evict+0x9a/0x14e [11309697.470775] [811198b4] ? dispose_list+0x35/0x3f [11309697.470844] [81119b87] ? prune_icache_sb+0x2c9/0x2d8 [11309697.470915] [811081b0] ? prune_super+0xd6/0x147 [11309697.470987] [810cb9e2] ? shrink_slab+0x1a3/0x266 [11309697.471056] [810cd937] ? balance_pgdat+0x335/0x625 [11309697.471126] [810cdf31] ? kswapd+0x30a/0x325 [11309697.471196] [81063815] ? wake_up_bit+0x20/0x20 [11309697.471265] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471334] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471403] [810633d9] ? kthread+0x7a/0x82 [11309697.471472] [8136d3f4] ? kernel_thread_helper+0x4/0x10 [11309697.471543] [8106335f] ? kthread_worker_fn+0x147/0x147 [11309697.471613] [8136d3f0] ? gs_change+0x13/0x13 [11309697.471680] ---[ end trace 56d2be5ea52d0917 ]--- -- George Barnett gbarn...@atlassian.com
Bug#703142: Kernel image 3.2.39-2: i915 module will not load.
Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 I'm using a reasonably vanilla testing distribution. The i915 module would not load, either at boot or using modprobe -a i915. The error message on the command line is as follows. FATAL: Error inserting i915 (): Invalid argument In dmesg it is as follows. [3.227711] i915: disagrees about version of symbol i2c_bit_algo [3.227766] i915: Unknown symbol i2c_bit_algo (err -22) Consequently, the xorg intel driver (for intel i3 2100, with HD 2000 graphics) wasn't loaded, and X11 fell back to VESA. I reverted to an earlier kernel/modules set and things work fine. Reverting was somewhat of a chore as when the new kernel/modules set was installed it completely replaced the earlier one. I would rather that it had not. Best wishes, Bob -- Robert L. Frazieremail: robert.fraz...@chch.ox.ac.uk Christ Church Oxford OX1 1DP www: http://kant1.chch.ox.ac.uk UK -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5143e7f7.80...@chch.ox.ac.uk
Bug#703142: marked as done (Kernel image 3.2.39-2: i915 module will not load.)
Your message dated Sat, 16 Mar 2013 05:00:33 + with message-id 1363410033.3937.182.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#703142: Kernel image 3.2.39-2: i915 module will not load. has caused the Debian Bug report #703142, regarding Kernel image 3.2.39-2: i915 module will not load. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 I'm using a reasonably vanilla testing distribution. The i915 module would not load, either at boot or using modprobe -a i915. The error message on the command line is as follows. FATAL: Error inserting i915 (): Invalid argument In dmesg it is as follows. [3.227711] i915: disagrees about version of symbol i2c_bit_algo [3.227766] i915: Unknown symbol i2c_bit_algo (err -22) Consequently, the xorg intel driver (for intel i3 2100, with HD 2000 graphics) wasn't loaded, and X11 fell back to VESA. I reverted to an earlier kernel/modules set and things work fine. Reverting was somewhat of a chore as when the new kernel/modules set was installed it completely replaced the earlier one. I would rather that it had not. Best wishes, Bob -- Robert L. Frazieremail: robert.fraz...@chch.ox.ac.uk Christ Church Oxford OX1 1DP www: http://kant1.chch.ox.ac.uk UK ---End Message--- ---BeginMessage--- On Sat, 2013-03-16 at 03:33 +, Robert Frazier wrote: Package: linux-image-3.2.0-4-amd64 Version: 3.2.39-2 I'm using a reasonably vanilla testing distribution. The i915 module would not load, either at boot or using modprobe -a i915. The error message on the command line is as follows. FATAL: Error inserting i915 (): Invalid argument In dmesg it is as follows. [3.227711] i915: disagrees about version of symbol i2c_bit_algo [3.227766] i915: Unknown symbol i2c_bit_algo (err -22) Consequently, the xorg intel driver (for intel i3 2100, with HD 2000 graphics) wasn't loaded, and X11 fell back to VESA. I reverted to an earlier kernel/modules set and things work fine. Reverting was somewhat of a chore as when the new kernel/modules set was installed it completely replaced the earlier one. I would rather that it had not. This is not a kernel bug - it indicates that modprobe didn't load all of i915's dependencies first (specifically i2c-algo-bit). Since this works for everyone else, I suspect that modprobe's dependency information got corrupted somehow. But all the evidence of that has almost certainly been wiped out when you reinstalled the old package. So there's nothing useful I can do here. Upgrade again and I bet the package will work fine. If not, reopen this bug and attach /lib/modules/3.2.0-4-amd64/modules.*. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part ---End Message---
Hang on NFS storage machines
Hi, We use debian for a number of machines in our storage infrastructure and we have recently been seeing a number of hangs. We primary notice this by seeing nfsd processes locking up and then a hung task killer going wild. We finally managed to get a trace last night - its pasted below: We did not see this crash under 2.6.39 back port however this kernel spontaneously rebooted at ~200 days uptime (we had about 3/4 of our infra reboot in a few weeks. It was not a good time for our ops teams). I would be grateful if anybody who could help me narrow this down would jump in and help with requests for further info, or provide further advice. [11309697.466397] [ cut here ] [11309697.466556] WARNING: at /build/buildd-linux_3.2.23-1~bpo60+2-amd64-oLufer/linux-3.2.23/fs/jbd2/journal.c:507 __jbd2_log_start_commit+0x7e/0x8c [jbd2]() [11309697.40] Hardware name: X8DT6 [11309697.466728] JBD2: bad log_start_commit: 2205591757 2205591757 14613566 0 [11309697.466798] Modules linked in: netconsole autofs4 8021q garp bridge stp nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bonding tcp_htcp ext4 jbd2 crc16 configfs loop ohci_hcd tpm_tis tpm i7core_edac i2c_i801 snd_pcm snd_timer snd soundcore edac_core i2c_core ioatdma tpm_bios snd_page_alloc coretemp crc32c_intel psmouse pcspkr joydev evdev acpi_cpufreq mperf processor serio_raw button thermal_sys ext3 jbd mbcache usbhid hid sd_mod ses enclosure crc_t10dif uhci_hcd ahci libahci libata igb ehci_hcd e1000e usbcore dca megaraid_sas usb_common scsi_mod [last unloaded: netconsole] [11309697.470190] Pid: 62, comm: kswapd0 Not tainted 3.2.0-0.bpo.3-amd64 #1 [11309697.470261] Call Trace: [11309697.470329] [810498a8] ? warn_slowpath_common+0x78/0x8c [11309697.470399] [8104995a] ? warn_slowpath_fmt+0x45/0x4a [11309697.470471] [a01cabad] ? __jbd2_log_start_commit+0x7e/0x8c [jbd2] [11309697.470558] [a01cac83] ? jbd2_log_start_commit+0x21/0x2f [jbd2] [11309697.470634] [a02dee7a] ? ext4_evict_inode+0x86/0x2d1 [ext4] [11309697.470707] [81119626] ? evict+0x9a/0x14e [11309697.470775] [811198b4] ? dispose_list+0x35/0x3f [11309697.470844] [81119b87] ? prune_icache_sb+0x2c9/0x2d8 [11309697.470915] [811081b0] ? prune_super+0xd6/0x147 [11309697.470987] [810cb9e2] ? shrink_slab+0x1a3/0x266 [11309697.471056] [810cd937] ? balance_pgdat+0x335/0x625 [11309697.471126] [810cdf31] ? kswapd+0x30a/0x325 [11309697.471196] [81063815] ? wake_up_bit+0x20/0x20 [11309697.471265] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471334] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471403] [810633d9] ? kthread+0x7a/0x82 [11309697.471472] [8136d3f4] ? kernel_thread_helper+0x4/0x10 [11309697.471543] [8106335f] ? kthread_worker_fn+0x147/0x147 [11309697.471613] [8136d3f0] ? gs_change+0x13/0x13 [11309697.471680] ---[ end trace 56d2be5ea52d0917 ]--- -- George Barnett gbarn...@atlassian.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b2ec601cdda242189a46599b31ea6...@atlassian.com
jbd2 tid wrap seen on NFS server
On Sat, 2013-03-16 at 16:12 +1100, George Barnett wrote: Hi, We use debian for a number of machines in our storage infrastructure and we have recently been seeing a number of hangs. We primary notice this by seeing nfsd processes locking up and then a hung task killer going wild. We finally managed to get a trace last night - its pasted below: We did not see this crash under 2.6.39 back port however this kernel spontaneously rebooted at ~200 days uptime (we had about 3/4 of our infra reboot in a few weeks. It was not a good time for our ops teams). I would be grateful if anybody who could help me narrow this down would jump in and help with requests for further info, or provide further advice. There was some discussion on the ext4 development list in December about why this warning can appear and how that should be dealt. It didn't seem like this actually got resolved though. I'm cc'ing that list in the hope of either reviving that discussion or finding out what the fix is. Ben. [11309697.466397] [ cut here ] [11309697.466556] WARNING: at /build/buildd-linux_3.2.23-1~bpo60+2-amd64-oLufer/linux-3.2.23/fs/jbd2/journal.c:507 __jbd2_log_start_commit+0x7e/0x8c [jbd2]() [11309697.40] Hardware name: X8DT6 [11309697.466728] JBD2: bad log_start_commit: 2205591757 2205591757 14613566 0 [11309697.466798] Modules linked in: netconsole autofs4 8021q garp bridge stp nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bonding tcp_htcp ext4 jbd2 crc16 configfs loop ohci_hcd tpm_tis tpm i7core_edac i2c_i801 snd_pcm snd_timer snd soundcore edac_core i2c_core ioatdma tpm_bios snd_page_alloc coretemp crc32c_intel psmouse pcspkr joydev evdev acpi_cpufreq mperf processor serio_raw button thermal_sys ext3 jbd mbcache usbhid hid sd_mod ses enclosure crc_t10dif uhci_hcd ahci libahci libata igb ehci_hcd e1000e usbcore dca megaraid_sas usb_common scsi_mod [last unloaded: netconsole] [11309697.470190] Pid: 62, comm: kswapd0 Not tainted 3.2.0-0.bpo.3-amd64 #1 [11309697.470261] Call Trace: [11309697.470329] [810498a8] ? warn_slowpath_common+0x78/0x8c [11309697.470399] [8104995a] ? warn_slowpath_fmt+0x45/0x4a [11309697.470471] [a01cabad] ? __jbd2_log_start_commit+0x7e/0x8c [jbd2] [11309697.470558] [a01cac83] ? jbd2_log_start_commit+0x21/0x2f [jbd2] [11309697.470634] [a02dee7a] ? ext4_evict_inode+0x86/0x2d1 [ext4] [11309697.470707] [81119626] ? evict+0x9a/0x14e [11309697.470775] [811198b4] ? dispose_list+0x35/0x3f [11309697.470844] [81119b87] ? prune_icache_sb+0x2c9/0x2d8 [11309697.470915] [811081b0] ? prune_super+0xd6/0x147 [11309697.470987] [810cb9e2] ? shrink_slab+0x1a3/0x266 [11309697.471056] [810cd937] ? balance_pgdat+0x335/0x625 [11309697.471126] [810cdf31] ? kswapd+0x30a/0x325 [11309697.471196] [81063815] ? wake_up_bit+0x20/0x20 [11309697.471265] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471334] [810cdc27] ? balance_pgdat+0x625/0x625 [11309697.471403] [810633d9] ? kthread+0x7a/0x82 [11309697.471472] [8136d3f4] ? kernel_thread_helper+0x4/0x10 [11309697.471543] [8106335f] ? kthread_worker_fn+0x147/0x147 [11309697.471613] [8136d3f0] ? gs_change+0x13/0x13 [11309697.471680] ---[ end trace 56d2be5ea52d0917 ]--- -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
