Bug#524438: cifs: Crash (OOPS or restart) when accessing Windows ME share with accented sharacters in filenames
Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: important -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-k7 (SMP w/1 CPU core) Locale: LANG=et_EE.iso-8859-15, LC_CTYPE=et_EE.iso-8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-18 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: In Lenny kernel 2.6.26-1-686 I had one OOPS and one restart, when trying to backup Windows ME computer to my Debian server (using rsync from Debian to sync files). Unfortunately, I did not write down OOPS infromation first time and in second time it just crashed hard. I then reverted to 2.6.18-6-k7 kernel from Etch. Then I could run backup, but it reported errors about filenames, with accented charactes in filenames (smbfs in Lenny no longer supports codepage parameter, which is cause of that problem). So my guess is, that this crash was caused by those filenames. Unfortunately I cannot run much test either, because it happened in production server. Windows ME has system codepage set to 775. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6 2.6.29-3 urgent upload
announcing for same day, for ftbfs fixes for alpha, parisc, sparc they seem to block transitions. let's hope parisc really builds, verified for 2 others. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524441: suspend to RAM stopped working with linux-image-2.6.26-2-686
Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: normal After upgrading my debian testing from linux-image-2.6.26-1-686 to linux-image-2.6.26-2-686, suspend to RAM stopped working. It blacks the screen, it does not turn off, and is completely frozen. It needs hard restart... -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-15) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu Mar 26 01:08:11 UTC 2009 ** Command line: root=/dev/mapper/evg-root vga=791 ro quiet SELINUX_INIT=NO ** Tainted: P (1) ** Kernel log: [ 16.556446] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 16.565936] ACPI: AC Adapter [ADP0] (on-line) [ 16.576438] input: Power Button (FF) as /class/input/input4 [ 16.583406] ACPI: Power Button (FF) [PWRF] [ 16.583688] input: Power Button (CM) as /class/input/input5 [ 16.586180] ACPI: Power Button (CM) [PWRB] [ 16.586421] input: Lid Switch as /class/input/input6 [ 16.596334] ACPI: Lid Switch [LID0] [ 16.596563] input: Sleep Button (CM) as /class/input/input7 [ 16.607499] input: PC Speaker as /class/input/input8 [ 16.615747] ACPI: Sleep Button (CM) [SLPB] [ 16.621016] ACPI: Battery Slot [BAT0] (battery present) [ 16.623724] input: Video Bus as /class/input/input9 [ 16.637800] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [ 16.694345] Yenta: CardBus bridge found at :06:04.0 [1558:04a0] [ 16.694646] PCI: Bus 7, cardbus bridge: :06:04.0 [ 16.694854] IO window: 0x4400-0x44ff [ 16.695046] IO window: 0x4800-0x48ff [ 16.695248] PREFETCH window: 0x9000-0x903f [ 16.695460] MEM window: 0x8800-0x8bff [ 16.695655] Yenta: Enabling burst memory read transactions [ 16.695889] Yenta: Using CSCINT to route CSC interrupts to PCI [ 16.696149] Yenta: Routing CardBus interrupts to PCI [ 16.696361] Yenta TI: socket :06:04.0, mfunc 0x0022, devctl 0x64 [ 16.705778] NET: Registered protocol family 23 [ 16.748265] ieee80211_crypt: registered algorithm 'NULL' [ 16.751216] ieee80211: 802.11 data/management/control stack, git-1.1.13 [ 16.751505] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [ 16.806162] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [ 16.820005] ipw2200: Copyright(c) 2003-2006 Intel Corporation [ 16.928841] Yenta: ISA IRQ mask 0x, PCI irq 22 [ 16.938594] Socket status: 3086 [ 16.950596] Yenta: Raising subordinate bus# of parent bus (#06) from #06 to #0a [ 16.960338] pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff [ 16.970016] cs: IO port probe 0x4000-0x4fff: clean. [ 16.980035] pcmcia: parent PCI bridge Memory window: 0xc800 - 0xc80f [ 16.991568] ACPI: PCI Interrupt :00:1b.0[A] - GSI 20 (level, low) - IRQ 20 [ 16.997968] PCI: Setting latency timer of device :00:1b.0 to 64 [ 16.998043] Yenta: CardBus bridge found at :06:04.1 [1558:04a0] [ 17.007902] PCI: Bus 11, cardbus bridge: :06:04.1 [ 17.019896] IO window: 0x4c00-0x4cff [ 17.029714] IO window: 0x1400-0x14ff [ 17.039562] PREFETCH window: 0x9040-0x907f [ 17.047073] MEM window: 0x8c00-0x8fff [ 17.059080] Yenta: Using CSCINT to route CSC interrupts to PCI [ 17.066378] Yenta: Routing CardBus interrupts to PCI [ 17.075872] Yenta TI: socket :06:04.1, mfunc 0x0022, devctl 0x64 [ 17.111057] hda_codec: Unknown model for ALC880, trying auto-probe from BIOS... [ 17.193090] ACPI: PCI Interrupt :00:1f.3[B] - GSI 19 (level, low) - IRQ 19 [ 17.316818] Yenta: ISA IRQ mask 0x, PCI irq 21 [ 17.326124] Socket status: 3006 [ 17.335304] Yenta: Raising subordinate bus# of parent bus (#06) from #0a to #0e [ 17.347308] pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff [ 17.356664] cs: IO port probe 0x4000-0x4fff: clean. [ 17.366060] pcmcia: parent PCI bridge Memory window: 0xc800 - 0xc80f [ 17.376410] ACPI: PCI Interrupt :06:03.0[A] - GSI 20 (level, low) - IRQ 20 [ 17.385205] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [ 17.395561] firmware: requesting ipw2200-bss.fw [ 17.598379] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) [ 17.619296] udev: renamed network interface eth0 to eth2 [ 17.707379] input: ImPS/2 Logitech Wheel Mouse as /class/input/input10 [ 19.073719] EXT3 FS on dm-1, internal journal [ 20.047551] fuse init (API version 7.9) [ 20.261621] kjournald starting. Commit interval 5 seconds [ 20.271074] EXT3 FS on hda2, internal journal [ 20.282974] EXT3-fs: mounted filesystem with ordered data mode. [ 20.329764] kjournald starting. Commit interval 5 seconds [ 20.339771] EXT3 FS on dm-2, internal journal [ 20.351482] EXT3-fs: recovery complete. [ 20.361257] EXT3-fs: mounted filesystem with ordered data mode. [ 20.817316] ip_tables: (C)
Bug#524464: USB related crash
Package: linux-image-2.6-amd64 Version: 2.6.26+17+lenny1 Severity: important I have a b2k based usb phone box (http://www.onevoip.net/index.php?catid=55) which causes the kernel to crash when the pc is under load. For example a skype video call or google earth's flight simulator. This is hwo the box is identified by linux: [ 403.795736] usb 1-2: Manufacturer: Yealink Network Technology Ltd. And this is a trace of the crash: [ 562.178804] general protection fault: [1] SMP [ 562.180005] CPU 0 [ 562.180005] Modules linked in: usbhid hid ff_memless radeon drm rfcomm l2cap bluetooth battery ppdev lp cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_stats cpufreq_ondemand ip6table_filter ip6_tables iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_REJECT ipt_REDIRECT ipt_recent ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables ipv6 fuse abituguru powernow_k8 freq_table joydev sbp2 loop snd_via82xx gameport snd_ac97_codec ac97_bus snd_mpu401_uart snd_seq_dummy snd_usb_audio snd_pcm_oss snd_mixer_oss parport_pc parport snd_seq_oss tuner_simple tuner_types snd_pcm snd_page_alloc snd_usb_lib snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_hwdep tuner serio_raw tvaudio pcspkr psmouse snd_timer snd_seq_device k8temp snd soundcore i2c_viapro gspca bttv firmware_class ir_common compat_ioctl32 videodev v4l1_compat i2c_algo_bit v4l2_common videobuf_dma_sg videobuf_core btcx_risc tveeprom i2c_core shpchp button pci_hotplug evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom via82cxxx sd_mod ide_pci_generic ide_core sata_via floppy ehci_hcd sata_sil ata_generic libata uhci_hcd scsi_mod via_velocity crc_ccitt dock ohci1394 ieee1394 thermal processor fan thermal_sys [ 562.180005] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 [ 562.180005] RIP: 0010:[a007dbc6] [a007dbc6] :uhci_hcd:uhci_scan_schedule+0xaf/0x79a [ 562.180005] RSP: :805e2e78 EFLAGS: 00010046 [ 562.180005] RAX: 10413bca89ec458b RBX: 81001f944800 RCX: 810080a33000 [ 562.180005] RDX: 0009 RSI: 81001f944800 RDI: 81001f944978 [ 562.180005] RBP: 81001f567600 R08: 8053cdd0 R09: 0010 [ 562.180005] R10: 810001d53938 R11: 810001d50fe0 R12: 8100120c3cd8 [ 562.180005] R13: 81001f944978 R14: 805a4320 R15: [ 562.180005] FS: 41d96950() GS:8053b000() knlGS:f5efd700 [ 562.180005] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 562.180005] CR2: df5ee000 CR3: 1f692000 CR4: 06e0 [ 562.180005] DR0: DR1: DR2: [ 562.180005] DR3: DR6: 0ff0 DR7: 0400 [ 562.180005] Process swapper (pid: 0, threadinfo 80572000, task 804f8480) [ 562.180005] Stack: 805e2ea8 80231a91 805e2ea8 0001 [ 562.180005] 0009 81001e1152c8 81001f944800 [ 562.180005] 81001f944978 81001f944800 805a4320 [ 562.180005] Call Trace: [ 562.180005] IRQ [80231a91] ? check_preempt_wakeup+0xbd/0xe9 [ 562.180005] [a007fea9] ? :uhci_hcd:uhci_irq+0x123/0x136 [ 562.180005] [8038e83e] ? usb_hcd_irq+0x3b/0x78 [ 562.180005] [8026bd0f] ? handle_IRQ_event+0x2c/0x61 [ 562.180005] [8026d1a8] ? handle_fasteoi_irq+0x90/0xc9 [ 562.180005] [8020f5e4] ? do_IRQ+0x6d/0xd9 [ 562.180005] [8020b0a3] ? default_idle+0x0/0x49 [ 562.180005] [8020c46d] ? ret_from_intr+0x0/0x19 [ 562.180005] EOI [8021eb68] ? native_safe_halt+0x2/0x3 [ 562.180005] [8020b0cd] ? default_idle+0x2a/0x49 [ 562.180005] [8020ac79] ? cpu_idle+0x89/0xb3 [ 562.180005] [ 562.180005] [ 562.180005] Code: 06 00 00 48 8b 45 10 48 83 e8 10 49 89 85 80 00 00 00 83 7d 74 01 0f 84 81 04 00 00 83 7d 70 03 75 1f 4c 8b 65 30 49 8b 44 24 20 44 8b 70 ec 45 31 ff 41 f7 c6 00 00 80 00 75 12 80 65 7c f7 eb [ 562.180005] RIP [a007dbc6] :uhci_hcd:uhci_scan_schedule+0xaf/0x79a [ 562.180005] RSP 805e2e78 [ 562.180006] ---[ end
Bug#523711: update-initramfs doesn't pass version to flash-kernel
On Sat, 11 Apr 2009, Martin Michlmayr wrote:
Package: initramfs-tools
I use one hard drive on several different ARM machines for tests from
time to time, so I have kernels for different subarches installed.
/boot/vmlinux may point to a kernel that is not the current subarch.
When I ran update-initramfs with a specific kernel, I get the
following:
| foobar:/etc/initramfs-tools# update-initramfs -u -k 2.6.28-1-ixp4xx
| update-initramfs: Generating /boot/initrd.img-2.6.28-1-ixp4xx
| Kernel /boot/vmlinuz-2.6.29-rc8-kirkwood does not match your subarchitecture
| ixp4xx, therefore not writing it to flash.
Now this situation is not common, but it shows a more general problem:
when /boot/vmlinux points to version 1 but you run update-initramfs on
version 2 it will still write version 1 to flash. I think it should
either write version 2 to flash or not write anything to flash (and
only update the ramdisk on disk).
The easiest solution is probably to pass a specific version to
flash-kernel.
sure update-initramfs can pass the ${version} to flash kernel.
how does flash-kernel react with the extra arg,
just tell me how you want it to be passed and it will get added for 0.93.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.29-3_amd64.changes
linux-2.6_2.6.29-3_amd64.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.29-3.dsc linux-2.6_2.6.29-3.diff.gz linux-doc-2.6.29_2.6.29-3_all.deb linux-manual-2.6.29_2.6.29-3_all.deb linux-patch-debian-2.6.29_2.6.29-3_all.deb linux-source-2.6.29_2.6.29-3_all.deb linux-support-2.6.29-1_2.6.29-3_all.deb linux-tree-2.6.29_2.6.29-3_all.deb linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb linux-libc-dev_2.6.29-3_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb: package says section is admin, override says kernel. Please note that a list of new sections were recently added to the archive: cli-mono, database, debug, fonts, gnu-r, gnustep, haskell, httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video, xfce, zope. At this time a script was used to reclassify packages into these sections. If this is the case, please only reply to this email if the new section is inappropriate, otherwise please update your package at the next upload. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. Please INCLUDE the list of packages as seen above, or we won't be able to deal with your mail due to missing information. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.29-3_amd64.changes ACCEPTED
Accepted: linux-2.6_2.6.29-3.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-3.diff.gz linux-2.6_2.6.29-3.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-3.dsc linux-doc-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-3_all.deb linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb linux-libc-dev_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.29-3_amd64.deb linux-manual-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.29_2.6.29-3_all.deb linux-patch-debian-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.29_2.6.29-3_all.deb linux-source-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-source-2.6.29_2.6.29-3_all.deb linux-support-2.6.29-1_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-support-2.6.29-1_2.6.29-3_all.deb linux-tree-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.29_2.6.29-3_all.deb Override entries for your package: linux-2.6_2.6.29-3.dsc - source devel linux-doc-2.6.29_2.6.29-3_all.deb - optional doc linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb - optional devel linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb - optional devel linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb - optional devel linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb - optional devel linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb - optional kernel linux-libc-dev_2.6.29-3_amd64.deb - optional devel linux-manual-2.6.29_2.6.29-3_all.deb - optional doc linux-patch-debian-2.6.29_2.6.29-3_all.deb - optional devel linux-source-2.6.29_2.6.29-3_all.deb - optional devel linux-support-2.6.29-1_2.6.29-3_all.deb - optional devel linux-tree-2.6.29_2.6.29-3_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 518231 523726 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522666: marked as done (linux-image-2.6.29-1-powerpc: run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20)
Your message dated Fri, 17 Apr 2009 12:48:07 + with message-id e1lunuf-0001zb...@ries.debian.org and subject line Bug#518231: fixed in linux-2.6 2.6.29-3 has caused the Debian Bug report #518231, regarding linux-image-2.6.29-1-powerpc: run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 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.) -- 518231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-1-powerpc Version: 2.6.29-2 Severity: grave postinst fails. Worked fine with version 2.6.29-1. The following happens reproducible: Setting up linux-image-2.6.29-1-powerpc (2.6.29-2) ... Running depmod. Running update-initramfs. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools run-parts: executing /etc/kernel/postinst.d/mkvmlinuz run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.29-1-powerpc.postinst line 1146. dpkg: error processing linux-image-2.6.29-1-powerpc (--configure): subprocess post-installation script returned error exit status 2 [...] Errors were encountered while processing: linux-image-2.6.29-1-powerpc [...] E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.29-1-powerpc (2.6.29-2) ... Running depmod. Running update-initramfs. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools run-parts: executing /etc/kernel/postinst.d/mkvmlinuz run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.29-1-powerpc.postinst line 1146. dpkg: error processing linux-image-2.6.29-1-powerpc (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-2.6.29-1-powerpc -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (400, 'stable'), (110, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.26-1-powerpc Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-powerpc depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii libc6 2.9-6 GNU C Library: Shared libraries ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-powerpc recommends no packages. Versions of packages linux-image-2.6.29-1-powerpc suggests: pn linux-doc-2.6.29 none (no description available) ii mkvmlinuz 35 create a kernel to boot a PowerPC -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-powerpc/preinst/elilo-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/failed-to-move-modules-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/bootloader-test-error-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/old-initrd-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-powerpc/postinst/old-dir-initrd-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/overwriting-modules-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/bootloader-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/old-system-map-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/depmod-error-2.6.29-1-powerpc: false linux-image-2.6.29-1-powerpc/preinst/abort-overwrite-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/postinst/depmod-error-initrd-2.6.29-1-powerpc: false linux-image-2.6.29-1-powerpc/postinst/bootloader-error-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/preinst/abort-install-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/preinst/lilo-initrd-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/preinst/initrd-2.6.29-1-powerpc: linux-image-2.6.29-1-powerpc/prerm/would-invalidate-boot-loader-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/create-kimage-link-2.6.29-1-powerpc: true linux-image-2.6.29-1-powerpc/postinst/kimage-is-a-directory:
Bug#523726: marked as done (linux-image-2.6.29-1-amd64: source should point to /usr/src/linux-headers-2.6.29-1-common)
Your message dated Fri, 17 Apr 2009 12:48:07 + with message-id e1lunuf-0001zd...@ries.debian.org and subject line Bug#523726: fixed in linux-2.6 2.6.29-3 has caused the Debian Bug report #523726, regarding linux-image-2.6.29-1-amd64: source should point to /usr/src/linux-headers-2.6.29-1-common 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.) -- 523726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-2 Severity: important Hello, The way kernel headers are installed seem to have changed recently. It breaks external module building because there is no easy way to find all non-compile generated headers. They were in /usr/src/linux-headers-*-amd64 earlier, now they are in /usr/src/linux-headers-*-common/ I think symlink /lib/modules/2.6.29-1-amd64/source (which disappeared btw?) should point to /usr/src/linux-headers-2.6.29-1-common/ This is what other distros such as Suse seem to be doing, and I don't see any other easy way to solve this. thanks, Brice -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, lc_ctype=fr...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.1 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo linux-image-2.6.29-1-amd64 recommends no packages. Versions of packages linux-image-2.6.29-1-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 none(no description available) -- debconf information: linux-image-2.6.29-1-amd64/preinst/overwriting-modules-2.6.29-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.29-1-amd64/preinst/failed-to-move-modules-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-test-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/old-dir-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/prerm/removing-running-kernel-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.29-1-amd64/postinst/create-kimage-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/initrd-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/elilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.29-1-amd64/postinst/old-initrd-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/depmod-error-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/postinst/depmod-error-initrd-2.6.29-1-amd64: false linux-image-2.6.29-1-amd64/preinst/abort-install-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/preinst/abort-overwrite-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/postinst/bootloader-error-2.6.29-1-amd64: linux-image-2.6.29-1-amd64/prerm/would-invalidate-boot-loader-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/postinst/old-system-map-link-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/lilo-initrd-2.6.29-1-amd64: true linux-image-2.6.29-1-amd64/preinst/bootloader-initrd-2.6.29-1-amd64: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.29-3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.29-3.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.29-3.diff.gz linux-2.6_2.6.29-3.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.29-3.dsc linux-doc-2.6.29_2.6.29-3_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.29_2.6.29-3_all.deb linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-all-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-all_2.6.29-3_amd64.deb linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-amd64_2.6.29-3_amd64.deb linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.29-1-common_2.6.29-3_amd64.deb linux-image-2.6.29-1-amd64_2.6.29-3_amd64.deb to
Bug#518231: marked as done (linux-image-2.6.28-1-powerpc: Fails to configure due to a debconf error)
Your message dated Fri, 17 Apr 2009 12:48:07 +
with message-id e1lunuf-0001zb...@ries.debian.org
and subject line Bug#518231: fixed in linux-2.6 2.6.29-3
has caused the Debian Bug report #518231,
regarding linux-image-2.6.28-1-powerpc: Fails to configure due to a debconf
error
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.)
--
518231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.28-1-powerpc
Version: 2.6.28-1
Severity: serious
Tags: patch
Hi,
I tried installing linux-image-2.6.28-1-powerpc from experimental but it
failed to configure:
run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20
I added set -x to this script, which revealed:
+ _db_cmd GET mkvmlinuz/bootloaders
+ IFS= printf %s\n GET mkvmlinuz/bootloaders
+ IFS= read -r _db_internal_line
+ RET=20 Unsupported command update-initramfs: (full line was
update-initramfs: Generating /boot/initrd.img-2.6.28-1-powerpc) received from
confmodule.
+ return 20
My system has the not so usual feature of using GRUB2 instead of yaboot for
booting, and I suspect I'm probably the only one doing this on this on
powerpc.
yaboot was installed, and the mkvmlinux/bootloaders debconf variable was
set to yaboot, it turned out.
This bug seems a reincarnation of this Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/54346
The following patch to postinst fixed it for me, although I'm not sure its
the right fix.
--- /tmp/linux-image-2.6.28-1-powerpc.postinst 2009-03-04 23:04:09.0
+0100
+++ /var/lib/dpkg/info/linux-image-2.6.28-1-powerpc.postinst2009-03-04
22:48:38.0 +0100
@@ -983,7 +983,7 @@
my $initrd_path = $realimageloc . initrd.img-$version;
my $ret = system($ramdisk_cmd .
($mkimage ? -m '$mkimage' : ) .
- -c -t -k $version);
+ -c -t -k $version 2);
if ($ret) {
warn $ramdisk_cmd failed to create initrd image.\n;
} else {
-- Package-specific info:
** Version:
Linux version 2.6.28-1-powerpc (Debian 2.6.28-1) (m...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-4) ) #1 Mon Feb 23 23:26:08 UTC 2009
** Command line:
BOOT_IMAGE=/boot/vmlinux-2.6.28-1-powerpc root=/dev/hda3 ro quiet
** Not tainted
** Kernel log:
[7.880625] usb usb4: Product: EHCI Host Controller
[7.880628] usb usb4: Manufacturer: Linux 2.6.28-1-powerpc ehci_hcd
[7.880631] usb usb4: SerialNumber: 0001:10:1b.2
[7.887940] ide-gd driver 1.18
[7.887983] hda: max request size: 512KiB
[7.906049] firewire_ohci 0002:24:0e.0: enabling device ( - 0002)
[7.937116] hda: 156301488 sectors (80026 MB), CHS=16383/255/63
[7.937191] hda: cache flushes supported
[7.937300] hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6
[7.976185] firewire_ohci: Added fw-ohci device 0002:24:0e.0, OHCI version
1.10
[7.976839] sungem.c:v0.98 8/24/03 David S. Miller (da...@redhat.com)
[8.044551] PHY ID: 1410cc1, addr: 0
[8.045269] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:3b:80:c4
[8.045273] eth0: Found Marvell 88E PHY
[8.464592] udev: renamed network interface eth0 to lan
[8.476343] firewire_core: created device fw0: GUID 000d93fffe3b80c4, S800
[9.179749] kjournald starting. Commit interval 5 seconds
[9.179772] EXT3-fs: mounted filesystem with ordered data mode.
[ 11.350275] udevd version 125 started
[ 11.897085] Linux agpgart interface v0.103
[ 11.930156] agpgart-uninorth :00:0b.0: Apple UniNorth 2 chipset
[ 11.930280] agpgart-uninorth :00:0b.0: configuring for size idx: 8
[ 11.930369] agpgart-uninorth :00:0b.0: AGP aperture is 32M @ 0x0
[ 11.990716] yenta_cardbus 0001:10:13.0: CardBus bridge found [:]
[ 11.990735] yenta_cardbus 0001:10:13.0: Enabling burst memory read
transactions
[ 11.990741] yenta_cardbus 0001:10:13.0: Using CSCINT to route CSC interrupts
to PCI
[ 11.990744] yenta_cardbus 0001:10:13.0: Routing CardBus interrupts to PCI
[ 11.990750] yenta_cardbus 0001:10:13.0: TI: mfunc 0x1002, devctl 0x60
[ 12.092216] yenta_cardbus 0001:10:13.0: ISA IRQ mask 0x, PCI irq 53
[ 12.09] yenta_cardbus 0001:10:13.0: Socket status: 3007
[ 12.092233] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge I/O
window: 0x0 - 0x7f
[ 12.092239] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge Memory
window: 0xf300 - 0xf3ff
[ 12.092244] yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge Memory
window: 0x8000 -
Patches for Debian Kernel.
Hi, There are a couple of patches, actually fixes, related to VMI ( paravirtualization) which were applied to the mainline kernel. The regression is present in all the kernels starting from 2.6.25. Given that Debian 5 is based of kernel version 2.6.26 we would need these patches in the Debian kernel too. The commits I am talking about are commit 55a8ba4b7f76bebd7e8ce3f74c04b140627a1bad x86, vmi: put a missing paravirt_release_pmd in pgd_dtor commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d x86, vmi: TSC going backwards check in vmi clocksource Not sure what the protocol is to ask for submissions, but I would know after this, i guess. Let me know if you would need anything else from me. Thanks, Alok -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503544: ath5k: after suspend to RAM, requires cold boot to work again
This is just to say that after an interval of working well, my ath5k is now completely nonfunctional in both 2.6.28 and 2.6.29. (I'm going to try backing all the way down to 2.6.27 next.) Cold boot doesn't help. Rebooting into Windows doesn't help (it used to). This isn't a hardware failure, because the wireless *does* work when Windows is the active operating system -- but the adapter seems permanently stuck in noise floor calibration timeout land with the Linux drivers. zw -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503544: ath5k: after suspend to RAM, requires cold boot to work again
On Tue, Apr 7, 2009 at 6:50 PM, Moritz Muehlenhoff j...@inutil.org wrote: I don't have the slightest idea how to report a bug to the kernel upstream. It's a standard Bugzilla installation: http://bugzilla.kernel.org Do they mind receiving bug reports for distribution-modified kernels? (i.e. do I need to reproduce the problem with an unmodified upstream kernel first?) While this works well for application software bugs, kernel bugs tend to require hardware-specific test/feedback requests from the relevant subsystem maintainer. All the Debian maintainers could do is to forward mails around and inducing needless overhead and delay. Ok, fair enough. Clearer documentation *would* be appreciated (including within reportbug) but I apologize for my earlier crankiness. Since the ath5k problem seems to have come back with a vengeance, I will see about taking it to upstream, but not until next week - I'm at a conference right now. zw -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patches for Debian Kernel.
On Fri, Apr 17, 2009 at 09:32:15AM -0700, Alok Kataria wrote: Hi, hey, There are a couple of patches, actually fixes, related to VMI ( paravirtualization) which were applied to the mainline kernel. The regression is present in all the kernels starting from 2.6.25. Given that Debian 5 is based of kernel version 2.6.26 we would need these patches in the Debian kernel too. The commits I am talking about are commit 55a8ba4b7f76bebd7e8ce3f74c04b140627a1bad x86, vmi: put a missing paravirt_release_pmd in pgd_dtor Already in lenny - see http://bugs.debian.org/520677 commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d x86, vmi: TSC going backwards check in vmi clocksource Not sure what the protocol is to ask for submissions, but I would know after this, i guess. The protocol is to file a bug (see http://bugs.debian.org). Its good (but not required) to include a good explanation about how the problem effects end users, whether or not it is a regression from a previous debian release, and to address the risk of the fix itself causing a regression. Thanks! -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patches for Debian Kernel.
On Fri, Apr 17, 2009 at 09:32:15AM -0700, Alok Kataria wrote: Hi, There are a couple of patches, actually fixes, related to VMI ( paravirtualization) which were applied to the mainline kernel. The regression is present in all the kernels starting from 2.6.25. Given that Debian 5 is based of kernel version 2.6.26 we would need these patches in the Debian kernel too. The commits I am talking about are commit 55a8ba4b7f76bebd7e8ce3f74c04b140627a1bad x86, vmi: put a missing paravirt_release_pmd in pgd_dtor commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d x86, vmi: TSC going backwards check in vmi clocksource Not sure what the protocol is to ask for submissions, but I would know after this, i guess. Let me know if you would need anything else from me. please file a bug with severity important so that the patches can be accepted for a stable backport. do the above patches apply to 2.6.26? could you later on test snapshots? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patches for Debian Kernel.
On Fri, 2009-04-17 at 10:23 -0700, maximilian attems wrote: On Fri, Apr 17, 2009 at 09:32:15AM -0700, Alok Kataria wrote: Hi, There are a couple of patches, actually fixes, related to VMI ( paravirtualization) which were applied to the mainline kernel. The regression is present in all the kernels starting from 2.6.25. Given that Debian 5 is based of kernel version 2.6.26 we would need these patches in the Debian kernel too. The commits I am talking about are commit 55a8ba4b7f76bebd7e8ce3f74c04b140627a1bad x86, vmi: put a missing paravirt_release_pmd in pgd_dtor commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d x86, vmi: TSC going backwards check in vmi clocksource Not sure what the protocol is to ask for submissions, but I would know after this, i guess. Let me know if you would need anything else from me. please file a bug with severity important so that the patches can be accepted for a stable backport. do the above patches apply to 2.6.26? could you later on test snapshots? Hi Max, Dann had already applied one of these patches, Thanks Dann. For the TSC going backwards check and some other requests that I have i will file a bug and take it from there. Regarding testing of snapshots, yes I can have someone test it out over here on VMware platform, but I had assume that you would also do some testing for regression on native hardware with any of these patches. Thanks a lot for your quick response. Alok -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#503544: ath5k: after suspend to RAM, requires cold boot to work again
On Fri, Apr 17, 2009 at 12:57:09PM -0400, Zack Weinberg wrote: This is just to say that after an interval of working well, my ath5k is now completely nonfunctional in both 2.6.28 and 2.6.29. (I'm going to try backing all the way down to 2.6.27 next.) Cold boot doesn't help. Rebooting into Windows doesn't help (it used to). This isn't a hardware failure, because the wireless *does* work when Windows is the active operating system -- but the adapter seems permanently stuck in noise floor calibration timeout land with the Linux drivers. zw please as already told several times report upstream on bugzilla.kernel.org so that the guys working on it can fix it. let us know the bug number. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524521: Fix time warps with VMI clocksource
Package: linux-2.6 Version: 2.6.26-13 This is a bug in the VMI_timer clocksource implementation and affects only when running with VMI enabled on VMware platform. There can be situations when the VMI_CYCLES_COUNTER can go back between subsequent reads of that counter. This could result in kernels hangs due to the unsigned calculation that are done in the clocksource code. This situation is only seen when the guest is running boot-halt tests (as the VMI timer could mostly be skewed only during the boot process) in a highly over-committed situation. So though the bug is not very severe it has negligible impact as it affects code which will be run only when running under VMware and that too in 32bit configuration. Please include it for the next update of the kernel for lenny. Commit details are commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d Author: Alok N Kataria akata...@vmware.com Date: Wed Feb 18 12:33:55 2009 -0800 x86, vmi: TSC going backwards check in vmi clocksource Thanks, Alok -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524442: linux-image-2.6.29-1-686: hangs starting hald when booting into multiuser mode
I didn't notice that dpkg had truncated the version of hal that I'm using. :; dpkg -l hal | sed -ne '$s/ */ /gp' ii hal 0.5.12~git20090406.46dc48-1 Hardware Abstraction Layer -- If the From address bounces, please see http://www.pook.it/. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patches for Debian Kernel.
On Fri, Apr 17, 2009 at 10:43:10AM -0700, Alok Kataria wrote: Dann had already applied one of these patches, Thanks Dann. For the TSC going backwards check and some other requests that I have i will file a bug and take it from there. cool, saw your bug report. Regarding testing of snapshots, yes I can have someone test it out over here on VMware platform, but I had assume that you would also do some testing for regression on native hardware with any of these patches. well native of course we do test, vmware specifics not. info about debian linux-2.6 specifics http://wiki.debian.org/DebianKernel including pointer to snapshots, we will ping you once build with the relevant patches. kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516078: IP masquerade misbehaves on kernel-2.6.26
Hi Maarten, I have just read your post and you are right. Unfortunately, I have had to work much more because I hadn't read your email. I excepcted to be notified by email, but I haven't. I have two nics eth0 -- intranet static ip eth1 -- internet dhcp ip Although on both kernel 2.6.18-etch and 2.8.26-lenny eth1 MTU was 576 (X.25 network size) for some reason with the former kernel it worked, but with the latter it didn't. By setting up the right MTU size (1500 for my cable connection) everything works pretty good. I found this article that was very helpful: http://adam.rosi-kessel.org/weblog/2009/02/25/iptables_router_failed_after_debian_lenny_upgrade_solved_by_setting_mtu My solution was inspired in what says here http://www.debianadmin.com/change-mtu-maximum-transmission-unit-of-network-interface.html but I had to put this instead in my /etc/network/interfaces file: ...etc... allow-hotplug eth1 iface eth1 inet dhcp post-up /sbin/ifconfig eth1 mtu 1500 I hope it helps anyone and again, thanks a lot Maarten for your help. Best regards! :-) PD: I have upgraded the pastebin links I pasted in my above posts. They were temporary and the new ones are permanent. Test on 2.6.18-etch: http://pastebin.com/f24d02877 Test on 2.6.28-lenny: http://pastebin.com/f62e2ffe4 _ ¿Quieres crear tus propios emoticonos gratis? Descubre cómo hacerlo en el Club Oficial de Messenger http://vivelive.com/ilovemessenger/
Bug#524529: linux-2.6: Missing build-dependency on cpio
Package: linux-2.6 Version: 2.6.29-2 It seems that linux-2.6 has an undeclared build-dependency on cpio. Note: Writing rdev_get_id.9 make[3]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29/debian/build/source » touch 'debian/stamps/build-doc' dh_prep mkdir -p debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29 cp -a debian/build/source/CREDITS debian/build/source/MAINTAINERS debian/build/source/README debian/build/source/REPORTING-BUGS debian/build/source/Documentation debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29 rm -rf debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29/Documentation/DocBook cd debian/build/build-doc/Documentation/DocBook; \ find * -name '*.html' -print \ | \ cpio -pd --preserve-modification-time '/tmp/jrnieder/linux-2.6-2.6.29/debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29/html' bash: line 3: cpio: command not found make[2]: *** [install-doc] Erreur 127 make[2]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29 » make[1]: *** [binary-indep] Erreur 2 make[1]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29 » make: *** [binary-indep] Erreur 2 dpkg-buildpackage: erreur: fakeroot debian/rules binary a produit une erreur de sortie de type 2 debuild: fatal error at line 1319: dpkg-buildpackage -rfakeroot -D -us -uc failed Regards, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524534: initramfs-tools: returns error when attempting to remove an already removed initrd
Package: initramfs-tools Version: 0.93.2 Severity: normal I was trying to remove a 2.6.27 kernel I had built from source and somehow the initrd was removed before initramfs-tools tried to remove it. This resulted in a failure to remove the kernel from the packaging system. See also bug #524499. The error message I was left with was: Cannot delete /boot/initrd.img-2.6.27, doesn't exist. run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1 dpkg: error processing linux-2.6.27 (--purge): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: linux-2.6.27 E: Sub-process /usr/bin/dpkg returned an error code (1) So this is a problem with /etc/kernel/postrm.d/initramfs-tools I temporarily added exit 0 to the start of /etc/kernel/postrm.d/initramfs-tools to force the removal of kernel-2.6.27. Right. We need to get the script in /etc/kernel/postrm.d/initramfs-tools fixed. Any idea where it came from? -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.26-2-amd64 root=UUID=39706f53-7c27-4310-b22a-36c7b042d1a1 ro -- /proc/filesystems ext3 vfat -- lsmod Module Size Used by battery16776 0 ipv6 288328 20 vfat 14976 0 fat51128 1 vfat nls_base 12932 2 vfat,fat it87 28952 0 hwmon_vid 7296 1 it87 loop 19468 0 snd_hda_intel 436440 0 snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81672 2 snd_hda_intel,snd_pcm_oss snd_seq_dummy 7428 0 snd_seq_oss33280 0 snd_seq_midi 11072 0 snd_rawmidi26784 1 snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 25744 2 snd_pcm,snd_seq snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd63688 10 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device i2c_piix4 13072 0 soundcore 12064 1 snd psmouse42268 0 i2c_core 27936 1 i2c_piix4 k8temp 9216 0 snd_page_alloc 13072 2 snd_hda_intel,snd_pcm pcspkr 7040 0 serio_raw 9860 0 shpchp 34208 0 pci_hotplug32056 1 shpchp wmi11712 0 button 11680 0 evdev 14208 3 ext3 124944 1 jbd51240 1 ext3 mbcache12804 1 ext3 sg 36576 0 sr_mod 19652 0 cdrom 37928 1 sr_mod sd_mod 29376 3 ata_generic10116 0 ide_pci_generic 9220 0 [permanent] ahci 33036 2 atiixp 8324 0 [permanent] libata165600 2 ata_generic,ahci ohci_hcd 25092 0 ide_core 128284 2 ide_pci_generic,atiixp scsi_mod 160760 4 sg,sr_mod,sd_mod,libata ehci_hcd 35980 0 dock 14112 1 libata r8169 31492 0 thermal22816 0 processor 42304 1 thermal fan 9352 0 thermal_sys17728 3 thermal,processor,fan -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9.90-3 GNU cpio -- a program to manage ar ii findutils 4.4.0-3utilities for finding files--find, ii klibc-utils 1.5.15-1 small utilities built with klibc f ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo ii udev 0.140-2/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.10.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of
Bug#524529: marked as done (linux-2.6: Missing build-dependency on cpio)
Your message dated Fri, 17 Apr 2009 23:04:46 +0200 with message-id 20090417210445.ga7...@wavehammer.waldi.eu.org and subject line Re: Bug#524529: linux-2.6: Missing build-dependency on cpio has caused the Debian Bug report #524529, regarding linux-2.6: Missing build-dependency on cpio 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.) -- 524529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.29-2 It seems that linux-2.6 has an undeclared build-dependency on cpio. Note: Writing rdev_get_id.9 make[3]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29/debian/build/source » touch 'debian/stamps/build-doc' dh_prep mkdir -p debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29 cp -a debian/build/source/CREDITS debian/build/source/MAINTAINERS debian/build/source/README debian/build/source/REPORTING-BUGS debian/build/source/Documentation debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29 rm -rf debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29/Documentation/DocBook cd debian/build/build-doc/Documentation/DocBook; \ find * -name '*.html' -print \ | \ cpio -pd --preserve-modification-time '/tmp/jrnieder/linux-2.6-2.6.29/debian/linux-doc-2.6.29/usr/share/doc/linux-doc-2.6.29/html' bash: line 3: cpio: command not found make[2]: *** [install-doc] Erreur 127 make[2]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29 » make[1]: *** [binary-indep] Erreur 2 make[1]: quittant le répertoire « /tmp/jrnieder/linux-2.6-2.6.29 » make: *** [binary-indep] Erreur 2 dpkg-buildpackage: erreur: fakeroot debian/rules binary a produit une erreur de sortie de type 2 debuild: fatal error at line 1319: dpkg-buildpackage -rfakeroot -D -us -uc failed Regards, Jonathan ---End Message--- ---BeginMessage--- On Fri, Apr 17, 2009 at 03:10:26PM -0500, Jonathan Nieder wrote: It seems that linux-2.6 has an undeclared build-dependency on cpio. cpio is a dependency of dpkg-dev which is pulled in via build-essential. Bastian -- Peace was the way. -- Kirk, The City on the Edge of Forever, stardate unknown ---End Message---
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #499227 # * http://bugzilla.kernel.org/show_bug.cgi?id=11600 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 499227 + fixed-upstream Bug#499227: linux-image-2.6.26-1-amd64: linux-image-2.6.26 kills HDA ATI SB sound There were no tags set. Tags added: fixed-upstream usertags 499227 - status-NEW Bug#499227: linux-image-2.6.26-1-amd64: linux-image-2.6.26 kills HDA ATI SB sound Usertags were: status-NEW. Usertags are now: . usertags 499227 + status-RESOLVED resolution-CODE-FIX Bug#499227: linux-image-2.6.26-1-amd64: linux-image-2.6.26 kills HDA ATI SB sound There were no usertags set. Usertags are now: resolution-CODE-FIX status-RESOLVED. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513537: linux-image-2.6.26-1-openvz-amd64 hanging
Hi Vitaliy, On Fri, Apr 03, 2009 at 02:21:45PM +0400, Vitaily Gusev wrote: On Thursday 02 April 2009 01:57:43 am Tom Rathborne wrote: On Wed, Apr 01, 2009 at 05:39:59PM -0400, Tom Rathborne wrote: I commented out the junk in fs/dcache.c and the kernel compiled. :) I will send you the sysrq-D info next time I get the bug! Oops ... now OpenVZ won't start! magrathea:~# vzctl start 101 Starting VE ... MOUNTING VE is mounted Error: kernel does not support user resources. Please, rebuild with CONFIG_USER_RESOURCE=y VE start failed UNMOUNTING VE is unmounted I do not see a CONFIG_USER_RESOURCE is not set in .config, and if I add 'CONFIG_USER_RESOURCE=y' then 'make menuconfig' reports: .config:3953:warning: trying to assign nonexistent symbol USER_RESOURCE I did find a couple of references to it: ./net/ipv4/tcp.c:#ifdef CONFIG_USER_RESOURCE ./net/ipv4/tcp_timer.c:#ifdef CONFIG_USER_RESOURCE but it looks like those should be CONFIG_BEANCOUNTERS. So ... what do I do next? It seems like this bug only happens with OpenVZ processes, but OpenVZ will not start without CONFIG_BEANCOUNTERS! Ok, switching off CONFIG_BEANCOUNTERS was a bad idea ;( I will prepare patch to fix beancounter warning in one-two days and send to you. Thanks a lot of for your efforts! Debian lenny recently updated its kernel source tree and patches, so I have built a fresh kernel with all of your debugging flags on, and of course CONFIG_BEANCOUNTERS on. I'm using these packages: linux-patch-debian-2.6.26 2.6.26-15 Debian patches to version 2.6.26 of the Linux kernel linux-source-2.6.262.6.26-15 Linux kernel source for version 2.6.26 with Debian patches linux-tree-2.6.26 2.6.26-15 Linux kernel source tree for building Debian kernel images The Debian patch directory is much bigger ... now looks like this: 0015--UB-Double-free-for-UDP-socket.patch.bz2 0016-nfs-fix-nfs-clinet-in-VE-finally.patch.bz2 0017-cpt-bump-image-version-to-VERSION_26.patch.bz2 0018-nfs-add-missed-ve_nfs.h-file.patch.bz2 0020-autofs4-pidns-friendly-oz_mode.patch.bz2 0021-autofs-fix-default-pgrp-vnr.patch.bz2 0022-conntrack-prevent-double-allocate-free-of-protos.patch.bz2 0023-conntrack-prevent-call-register_pernet_subsys-fro.patch.bz2 0024-conntrack-prevent-call-nf_register_hooks-from-VE.patch.bz2 0025-conntrack-Allocate-free-ve_nf_conntrack_l3proto_ipv.patch.bz2 0026-ct-Move-_nf_conntrack_l3proto_ipv6-to-net-namespace.patch.bz2 0027-Fix-erratum-that-causes-memory-corruption.patch.bz2 0028-conntrack-fix-oops-in-nf_ct_frag6_gather.patch.bz2 0029-conntrack-adjust-context-during-freeing.patch.bz2 0031-Add-VE-features-for-sit-and-ipip-devices.patch.bz2 0033-netfilter-NAT-assign-nf_nat_seq_adjust_hook-from-V.patch.bz2 0034-netfilter-call-nf_register_hooks-from-VE0-context-o.patch.bz2 0040-Simplify-call-__dev_change_net_namespace-by-remove.patch.bz2 0041-Adjust-VE-before-call-netdev_unregister_kobject-netd.patch.bz2 0042-iptables-setup-init-iptables-mask-before-net-initia.patch.bz2 0042-netns-fix-net_generic-array-leak.patch.bz2 0043-net-set-ve-context-when-init-exit-method-is-called.patch.bz2 0044-vzwdog-walk-through-the-block-devices-list-properly.patch.bz2 0045-Correct-per-process-capabilities-bounding-set-in-CT.patch.bz2 0046-netns-enable-cross-ve-Unix-sockets.patch.bz2 0047-netfilter-Fix-NULL-dereference-in-nf_nat_setup_info.patch.bz2 0048-netfilter-Add-check-to-the-nat-hooks.patch.bz2 0049-cpt-Make-the-proper-check-for-sigmask.patch.bz2 0050-nfs-Fix-access-to-freed-memory.patch.bz2 0051-NFS-NFS-super-blocks-in-different-VEs-should-be-dif.patch.bz2 0052-ms-fix-inotify-umount.patch.bz2 0054-ve-sanitize-capability-checks-for-namespaces-creati.patch.bz2 0056-nfs-Fix-nfs_match_client.patch.bz2 0057-Add-do_ve_enter_hook.patch.bz2 0058-Add-kthread_create_ve-and-kthread_run_ve-functio.patch.bz2 0059-Don-t-dereference-NULL-tsk-mm-in-ve_move_task.patch.bz2 0060-nfs-use-kthread_run_ve-to-start-lockd.patch.bz2 0063-bridge-don-t-leak-master-device-on-brctl-addif.patch.bz2 0064-net-NETIF_F_VIRTUAL-intersects-with-NETIF_F_LRO.patch.bz2 0065-Fix-broken-permissions-for-Unix98-pty.patch.bz2 0066-Free-skb-nf_bridge-in-veth_xmit-and-venet_xmit.patch.bz2 0067-autofs4-fix-ia32-compat-mode.patch.bz2 0070-pidns-update-leader_pid-at-pidns-attach.patch.bz2 0072-pidns-lost-task-debug-print-uses-wrong-prototype.patch.bz2 0073-pidns-zap-ve-process-only-when-killing-ve-s-init-pi.patch.bz2 0075-bc-fix-permissions-on-proc-bc.patch.bz2 cpt-revert-check-on-sk_reuse-gt-one.patch.bz2 fix-wrong-size-of-ub0_percpu.patch.bz2 netlink-fix-conntrack-oops.patch.bz2 openvz.patch.bz2 simfs-getatts-fix-oops-on-NULL-mnt.patch.bz2 I will let you know what happens. Of course I am
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #499227 # * http://bugzilla.kernel.org/show_bug.cgi?id=11600 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 499227 + fixed-upstream usertags 499227 - status-NEW usertags 499227 + status-RESOLVED resolution-CODE-FIX thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524542: Patches to fix bugs related to TSC clocksource on VMware
Package: linux-2.6 Version: 2.6.26-13 This is regarding some patches which improve timekeeping for Linux when running under VMware. Without these patches we may see incorrect timekeeping with Debian's lenny kernel when running as guest under VMware. VMware hypervisor exports a consistent TSC to the guest for timekeeping purposes, but still due to some kernel assumptions which don't hold true in virtualization environments, the kernel can mark the TSC unstable and hence unusable for timekeeping purposes. Without these patches TSC cannot be used as a reliable clocksource under VMware. The problems with TSC assumptions in the kernel are as follows. 1) TSC calibration : TSC calibration maybe error prone in virtualized environment, and since an error in TSC frequency may accumulate during the kernels runtime, its important to keep the error to the minimum. The best way to get the TSC frequency is to ask the hypervisor for that. 2) With the NO-HZ kernel, there is no guarantee that the acpi_pm timer will be sampled at least every 4.68 seconds (the wrap interval), because the vcpu, in extreme circumstances, may not have a chance to run in that time. Thus, the acpi_pm timer is not suitable to be used as a clocksource watchdog when running on a hypervisor. 3) Virtual TSCs can be kept nearly in sync, but because the virtual TSC offset is set by software, it's not perfect. So, the TSC synchronization test at bootup can fail. (Really, it can fail on native as well, and that's why the tests for backwards TSC were added to read_tsc()/vread_tsc()). We need a way to skip this check when on VMware. These patches add some VMware detection code which we use to get around these TSC assumptions which fail under VMware's hypervisor. Please note that these patches are not VMI ( paravirt) specific, and change the default kernel for 32 and 64bit, but the modifications come into affect only when we are running under VMware. Just the init and detection code is run for native case. This will also change the kABI, as it adds a field to the cpuinfo_x86 structure. The mainline commit id's are commit b2bcc7b299f37037b4a78dc1538e5d6508ae8110 x86: add a synthetic TSC_RELIABLE feature bit commit 49ab56ac6e1b907b7dadb72a4012460359feaf0e x86: add X86_FEATURE_HYPERVISOR feature bit commit 88b094fb8d4fe43b7025ea8d487059e8813e02cd x86: Hypervisor detection and get tsc_freq from hypervisor commit eca0cd028bdf0f6aaceb0d023e9c7501079a7dda x86: Add a synthetic TSC_RELIABLE feature bit. commit 395628ef4ea12ff0748099f145363b5e33c69acb x86: Skip verification by the watchdog for TSC clocksource. commit 6bdbfe99916398dbb28d83833cc04757110f2738 x86: VMware: Fix vmware_get_tsc code commit fd8cd7e1919fc1c27fe2fdccd2a1cd32f791ef0f x86: vmware: look for DMI string in the product serial key These patches have been included in the Ubuntu intrepid kernel as well which is 2.6.27, so if its easier you may cherry pick those patches from that tree. The only reason it might be easier is because IMO it would require less or no effort to backport it to Lenny from Intrepid rather than from mainline where these patches were applied in the 2.6.29 cycle. Thanks, Alok -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524464: Also existing in 2.6.29
Here is another trace from 2.6.29. This is not causing a crash, but it's the first symptom. When the system is used a little more the kernel crashes. There are similar traces from 2.6.26 before the crash. Apr 18 00:26:42 george kernel: [ 1393.322650] [ cut here ] Apr 18 00:26:42 george kernel: [ 1393.325446] WARNING: at /build/linux-2.6-2.6.29/debian/build/source_amd64_none/drivers/usb/host/uhci-q.c:129 uhci_free_td+0x78/0x8c [uhci_hcd]() Apr 18 00:26:42 george kernel: [ 1393.325446] Hardware name: Apr 18 00:26:42 george kernel: [ 1393.325446] Device: uhci_hcd Apr 18 00:26:42 george kernel: [ 1393.325446] td 88000c2ada40 still in fl_list! Apr 18 00:26:42 george kernel: [ 1393.325446] Modules linked in: hid_gaff hid_pl hid_cypress hid_zpff hid_gyration hid_sony hid_ntrig hid_samsung hid_microsoft hid_tmff hid_monterey hid_ezkey hid_apple hid_a4tech hid_logitech ff_memless hid_cherry hid_sunplus hid_petalynx hid_belkin hid_chicony usbhid snd_usb_audio hid snd_usb_lib snd_hwdep gspca_zc3xx gspca_main uhci_hcd radeon drm rfcomm l2cap bluetooth battery ppdev lp cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_stats ip6table_filter ip6_tables iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables ipv6 fuse abituguru powernow_k8 firewire_sbp2 loop snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_mpu401_uart snd_seq_dummy tuner_simple tuner_types tuner tvaudio snd_seq_oss snd_seq_midi snd_rawmidi evdev snd_seq_midi_event snd_seq serio_raw psmouse joydev pcspkr snd_timer snd_seq_device snd k8temp bttv soundcore i2c_viapro ir_common i2c_algo_bit v4l2_common videodev v4l1_compat v4l2_compat_ioctl32 videobuf_dma_sg videobuf_core btcx_risc tveeprom i2c_core shpchp pci_hotplug parport_pc parport button ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod ide_cd_mod cdrom via82cxxx sd_mod crc_t10dif ide_pci_generic ide_core sata_via floppy sata_sil ata_generic ehci_hcd libata via_velocity crc_ccitt scsi_mod firewire_ohci firewire_core crc_itu_t thermal processor fan thermal_sys Apr 18 00:26:42 george kernel: [ 1393.325446] Pid: 9819, comm: Xorg Not tainted 2.6.29-trunk-amd64 #1 Apr 18 00:26:42 george kernel: [ 1393.325446] Call Trace: Apr 18 00:26:42 george kernel: [ 1393.325446] IRQ [80244bb5] warn_slowpath+0xd8/0x112 Apr 18 00:26:42 george kernel: [ 1393.325446] [8023750c] __wake_up_common+0x44/0x73 Apr 18 00:26:42 george kernel: [ 1393.325446] [80238174] __wake_up+0x30/0x44 Apr 18 00:26:42 george kernel: [ 1393.325446] [80228dbc] default_spin_lock_flags+0x5/0x9 Apr 18 00:26:42 george kernel: [ 1393.325446] [8047a824] _spin_lock_irqsave+0x24/0x2c Apr 18 00:26:42 george kernel: [ 1393.325446] [80228dbc] default_spin_lock_flags+0x5/0x9 Apr 18 00:26:42 george kernel: [ 1393.325446] [8047a824] _spin_lock_irqsave+0x24/0x2c Apr 18 00:26:42 george kernel: [ 1393.325446] [a067c70a] uhci_free_td+0x78/0x8c [uhci_hcd] Apr 18 00:26:42 george kernel: [ 1393.325446] [a067cf0f] uhci_scan_schedule+0x3ff/0x835 [uhci_hcd] Apr 18 00:26:42 george kernel: [ 1393.325446] [a067ef1a] uhci_irq+0x132/0x148 [uhci_hcd] Apr 18 00:26:42 george kernel: [ 1393.325446] [803d0d91] usb_hcd_irq+0x3d/0x89 Apr 18 00:26:42 george kernel: [ 1393.325446] [80280dfd] handle_IRQ_event+0x2c/0x61 Apr 18 00:26:42 george kernel: [ 1393.325446] [802822be] handle_fasteoi_irq+0x88/0xce Apr 18 00:26:42 george kernel: [ 1393.325446] [80213da1] do_IRQ+0x64/0xd7 Apr 18 00:26:42 george kernel: [ 1393.325446] [80211b93] ret_from_intr+0x0/0x29 Apr 18 00:26:42 george kernel: [ 1393.325446] EOI [8045f1c0] unix_poll+0x0/0x97 Apr 18 00:26:42 george kernel: [ 1393.325446] [8047a8fd] _spin_unlock_irqrestore+0xf/0x17 Apr 18 00:26:42 george kernel: [ 1393.325446] [802ca81e] poll_freewait+0x5b/0x86 Apr 18 00:26:42 george kernel: [ 1393.325446] [802cb2c9] do_select+0x4e2/0x510 Apr 18 00:26:42 george kernel: [ 1393.325446]
Bug#524529: linux-2.6: Missing build-dependency on cpio
Hi Bastian, Bastian Blank wrote: On Fri, Apr 17, 2009 at 03:10:26PM -0500, Jonathan Nieder wrote: It seems that linux-2.6 has an undeclared build-dependency on cpio. cpio is a dependency of dpkg-dev which is pulled in via build-essential. That makes sense. dpkg-dev 1.15.0 from experimental does not build-depend on cpio (from the changelog: * Remove unneeded cpio dependency from dpkg-dev.), hence my confusion. Maybe it would make sense for linux-2.6 to build-depend directly on cpio in the future, but for now there is certainly no problem. Sorry for the spurious bug report, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
