Re: [Bug 8374] ACPI: Unable to turn cooling device [c146aec8] 'on'
On Tue, Aug 12, 2008 at 01:29:44PM +0800, cruz wrote: http://bugzilla.kernel.org/show_bug.cgi?id=8374 Hi, I am still having this problem with Lenny (2.6.24-1-686), can someone advise me on any workaround? lenny has newer kernel aka 2.6.25 and will soon get unstable 2.6.26 install those. also bug reports are *bad* for support requests please direct those to an user mailing list. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494365: 2.6.26 hangs on opteron CPUs
adding [EMAIL PROTECTED] on cc for 8004dd965b13b01a96def054d420f6df7ff22d53 On Mon, Aug 11, 2008 at 11:17:34PM -0600, dann frazier wrote: On Fri, Aug 08, 2008 at 08:51:33PM +0200, Peter Palfrader wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Severity: important Hi, it seems that 2.6.26 (whether the debian package or the kernel.org kernel) locks up after a while on Debian's DL385G1 systems. After a while, sooner with more disk IO/filesystem load, the system hangs: it continues to do stuff but everything involving disk hangs forever. The systems work just fine on a 2.6.25.10 kernel. The servers have Opterons like this: cpu family : 15 model : 33 so http://www.uwsg.iu.edu/hypermail/linux/kernel/0808.0/0882.html might explain it. hey Peter, This is readily reproducible - a simple kernel compile was all it took. git bisecting suggests that this issue was introduced by [1] and unmasked by [2] during 2.6.26 devlopment. It was later fixed during 2.6.27 development by [3]. Can you confirm that the attached backport of [3] fixes the problem for you? [1] 35605a1027ac630f85a1b95684f7e86b82498cd6 [2] 8d539108560ec121d59eee05160236488266221c [3] 8004dd965b13b01a96def054d420f6df7ff22d53 -- dann frazier commit 8004dd965b13b01a96def054d420f6df7ff22d53 Author: Yinghai Lu [EMAIL PROTECTED] Date: Mon May 12 17:40:39 2008 -0700 x86: amd opteron TOM2 mask val fix there is a typo in the mask value, need to remove that extra 0, to avoid 4bit clearing. Signed-off-by: Yinghal Lu [EMAIL PROTECTED] Signed-off-by: Ingo Molnar [EMAIL PROTECTED] Backported to Debian's 2.6.26 by dann frazier [EMAIL PROTECTED] diff -urpN linux-source-2.6.26.orig/arch/x86/kernel/cpu/mtrr/generic.c linux-source-2.6.26/arch/x86/kernel/cpu/mtrr/generic.c --- linux-source-2.6.26.orig/arch/x86/kernel/cpu/mtrr/generic.c 2008-08-11 22:55:59.0 -0600 +++ linux-source-2.6.26/arch/x86/kernel/cpu/mtrr/generic.c2008-08-11 22:57:13.0 -0600 @@ -219,7 +219,7 @@ void __init get_mtrr_state(void) tom2 = hi; tom2 = 32; tom2 |= lo; - tom2 = 0xff800ULL; + tom2 = 0xff80ULL; } if (mtrr_show) { int high_width; diff -urpN linux-source-2.6.26.orig/arch/x86/pci/k8-bus_64.c linux-source-2.6.26/arch/x86/pci/k8-bus_64.c --- linux-source-2.6.26.orig/arch/x86/pci/k8-bus_64.c 2008-08-11 22:55:59.0 -0600 +++ linux-source-2.6.26/arch/x86/pci/k8-bus_64.c 2008-08-11 22:57:13.0 -0600 @@ -384,7 +384,7 @@ static int __init early_fill_mp_bus_info /* need to take out [0, TOM) for RAM*/ address = MSR_K8_TOP_MEM1; rdmsrl(address, val); - end = (val 0xff800ULL); + end = (val 0xff80ULL); printk(KERN_INFO TOM: %016lx aka %ldM\n, end, end20); if (end (1ULL32)) update_range(range, 0, end - 1); @@ -478,7 +478,7 @@ static int __init early_fill_mp_bus_info /* TOP_MEM2 */ address = MSR_K8_TOP_MEM2; rdmsrl(address, val); - end = (val 0xff800ULL); + end = (val 0xff80ULL); printk(KERN_INFO TOM2: %016lx aka %ldM\n, end, end20); update_range(range, 1ULL32, end - 1); } -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[PATCH] Enable amd64 Xen on trunk
Since trunk is now at 2.6.27 which supports amd64 Xen guest's I thought we could enable CONFIG_XEN for that kernel. I also added some options to the 32 bit config, they are enabled anyway this just makes them that explicit. any opinions? diff --git a/linux-2.6/debian/config/amd64/config b/linux-2.6/debian/config/amd64/config index 81ece14..a7258aa 100644 --- a/linux-2.6/debian/config/amd64/config +++ b/linux-2.6/debian/config/amd64/config @@ -93,6 +93,13 @@ CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m ## +## file: arch/x86/xen/Kconfig +## +CONFIG_XEN=y +CONFIG_XEN_MAX_DOMAIN_MEMORY=32 +CONFIG_XEN_SAVE_RESTORE=y + +## ## file: crypto/Kconfig ## CONFIG_CRYPTO_AES_X86_64=m @@ -176,6 +183,7 @@ CONFIG_BLK_DEV_RAM_SIZE=65536 CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set +CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=m ## @@ -242,6 +250,7 @@ CONFIG_STALDRV=y CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m +CONFIG_HVC_XEN=y CONFIG_NVRAM=m CONFIG_RTC=y CONFIG_GEN_RTC=m @@ -506,6 +515,7 @@ CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m +CONFIG_XEN_KBDDEV_FRONTEND=y ## ## file: drivers/input/gameport/Kconfig @@ -931,6 +941,7 @@ CONFIG_R8169=m CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m +CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_FDDI=y CONFIG_DEFXX=m # CONFIG_DEFXX_MMIO is not set @@ -1341,6 +1352,7 @@ CONFIG_FB_VOODOO1=m CONFIG_FB_TRIDENT=m # CONFIG_FB_TRIDENT_ACCEL is not set CONFIG_FB_VIRTUAL=m +CONFIG_XEN_FBDEV_FRONTEND=y ## ## file: drivers/video/backlight/Kconfig @@ -1404,6 +1416,12 @@ CONFIG_WDT_501_PCI=y CONFIG_USBPCWATCHDOG=m ## +## file: drivers/xen/Kconfig +## +CONFIG_XEN_BALLOON=y +CONFIG_XEN_SCRUB_PAGES=y + +## ## file: fs/partitions/Kconfig ## CONFIG_ACORN_PARTITION=y diff --git a/linux-2.6/debian/config/i386/config b/linux-2.6/debian/config/i386/config index ed13748..fb8f5d1 100644 --- a/linux-2.6/debian/config/i386/config +++ b/linux-2.6/debian/config/i386/config @@ -158,6 +158,8 @@ CONFIG_LGUEST_GUEST=y ## file: arch/x86/xen/Kconfig ## CONFIG_XEN=y +CONFIG_XEN_MAX_DOMAIN_MEMORY=8 +CONFIG_XEN_SAVE_RESTORE=y ## ## file: crypto/Kconfig @@ -610,6 +612,7 @@ CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m +CONFIG_XEN_KBDDEV_FRONTEND=y ## ## file: drivers/input/gameport/Kconfig @@ -1667,6 +1670,12 @@ CONFIG_USBPCWATCHDOG=m CONFIG_BINFMT_AOUT=m ## +## file: drivers/xen/Kconfig +## +CONFIG_XEN_BALLOON=y +CONFIG_XEN_SCRUB_PAGES=y + +## ## file: fs/partitions/Kconfig ## CONFIG_ACORN_PARTITION=y -- Ian Campbell It may or may not be worthwhile, but it still has to be done. signature.asc Description: This is a digitally signed message part
Bug#494783: usbserial module parameters
Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: normal modinfo usbserial shows three parameters: filename: /lib/modules/2.6.26-1-686/kernel/drivers/usb/serial/usbserial.ko license:GPL description:USB Serial Driver core author: Greg Kroah-Hartman, [EMAIL PROTECTED], http://www.kroah.com/linux/ depends:usbcore vermagic: 2.6.26-1-686 SMP mod_unload modversions 686 parm: vendor:User specified USB idVendor (ushort) parm: product:User specified USB idProduct (ushort) parm: debug:Debug enabled or not (bool) but the sysfs shows only one parameter % ls -al /sys/module/usbserial/parameters insgesamt 0 drwxr-xr-x 2 root root0 12. Aug 09:24 . drwxr-xr-x 7 root root0 12. Aug 09:24 .. -rw-r--r-- 1 root root 4096 12. Aug 09:24 debug What is correct? -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494365: 2.6.26 hangs on opteron CPUs
On Fri, Aug 08, 2008 at 08:51:33PM +0200, Peter Palfrader wrote: it seems that 2.6.26 (whether the debian package or the kernel.org kernel) locks up after a while on Debian's DL385G1 systems. On Mon, Aug 11, 2008 at 11:17:34PM -0600, dann frazier wrote: hey Peter, This is readily reproducible - a simple kernel compile was all it took. git bisecting suggests that this issue was introduced by [1] and unmasked by [2] during 2.6.26 devlopment. It was later fixed during 2.6.27 development by [3]. Can you confirm that the attached backport of [3] fixes the problem for you? [3] 8004dd965b13b01a96def054d420f6df7ff22d53 I upgraded several of Debian's machines to 2.6.26.2 plus the patch you provided. So far they are still running - and I put them under load that would reliably kill them before. Thanks, weasel -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493479: test build
hey Dave, I'm wondering if this is an occurrence of #494365. Can you test this build to see if it fixes this issue for you? http://people.debian.org/~dannf/bugs/494365/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494783: usbserial module parameters
On Tue, Aug 12, 2008 at 09:29:54AM +0200, Dr. Markus Waldeck wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: normal modinfo usbserial shows three parameters: filename: /lib/modules/2.6.26-1-686/kernel/drivers/usb/serial/usbserial.ko license:GPL description:USB Serial Driver core author: Greg Kroah-Hartman, [EMAIL PROTECTED], http://www.kroah.com/linux/ depends:usbcore vermagic: 2.6.26-1-686 SMP mod_unload modversions 686 parm: vendor:User specified USB idVendor (ushort) parm: product:User specified USB idProduct (ushort) parm: debug:Debug enabled or not (bool) but the sysfs shows only one parameter % ls -al /sys/module/usbserial/parameters insgesamt 0 drwxr-xr-x 2 root root0 12. Aug 09:24 . drwxr-xr-x 7 root root0 12. Aug 09:24 .. -rw-r--r-- 1 root root 4096 12. Aug 09:24 debug What is correct? sysfs is for runtime changes, the other on load. please ask support question on mailing list and not as bug report. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Enable amd64 Xen on trunk
On Tue, 12 Aug 2008, Ian Campbell wrote: Since trunk is now at 2.6.27 which supports amd64 Xen guest's I thought we could enable CONFIG_XEN for that kernel. I also added some options to the 32 bit config, they are enabled anyway this just makes them that explicit. any opinions? full ack. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Enable amd64 Xen on trunk
On Tue, Aug 12, 2008 at 08:40:09AM +0100, Ian Campbell wrote: Since trunk is now at 2.6.27 which supports amd64 Xen guest's I thought we could enable CONFIG_XEN for that kernel. I also added some options to the 32 bit config, they are enabled anyway this just makes them that explicit. any opinions? diff --git a/linux-2.6/debian/config/amd64/config b/linux-2.6/debian/config/amd64/config index 81ece14..a7258aa 100644 --- a/linux-2.6/debian/config/amd64/config +++ b/linux-2.6/debian/config/amd64/config @@ -93,6 +93,13 @@ CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m ## +## file: arch/x86/xen/Kconfig +## +CONFIG_XEN=y +CONFIG_XEN_MAX_DOMAIN_MEMORY=32 +CONFIG_XEN_SAVE_RESTORE=y Okay. CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m +CONFIG_XEN_KBDDEV_FRONTEND=y =m? CONFIG_FB_TRIDENT=m # CONFIG_FB_TRIDENT_ACCEL is not set CONFIG_FB_VIRTUAL=m +CONFIG_XEN_FBDEV_FRONTEND=y =m? Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, Elaan of Troyius, stardate 4372.5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434138: Boot failure from software-RAID1 in etch during upgrade to 2.4.24-etchnhalf.1-686
Hello, Through upgrade of our servers, I got biten several times by this bug. This is a sum up : - most of those pb occured while upgrading to 2.6.24-etchnhalf.1 - all the servers are Dell PowerEdges, with / build on /dev/md0=/dev/sd[a,b]2, the disks been SCSI, SAS or SATA2. - Using rootdelay=1 solved the pb on all cases (included the case in my previous report). - All the upgrades path have been : - upgrade to uptodate 2.6.18 (works on all cases except 1 out of ~30 servers) - then upgrade to 2.6.24 on some servers Didn't boot without the fix (PE = PowerEdge): - 2 * PE-1750 - 1 * PE-2800 - 2 PE-2850, one of them didn't boot on the linux-image-2.6.18-6-686-bigmem 2.6.18.dfsg.1-18etch6 - 2.6.18.dfsg.1-22 upgrade (did without -bigmem, did with 2.6.18-bigmem or 2.4.24 with rootdelay=1) - 3 * PE2950 Did boot 2.6.24 without the fix : - 3 * PE-860 (SATA2 for those servers) - 1 * PE-2650 All the server failed at the same stage in the initrd with the following error : ... Failure: failed to start /dev/md0 Attached : - /etc/mdadm/mdadm.conf from /boot/initrd.img-2.6.24-etchnhalf.1-686 - /conf/md.conf from /boot/initrd.img-2.6.24-etchnhalf.1-686 - the bootlog from the PE-2800. In the used initrd /scripts/init-premount/udev has been edited to echo -- in premount and -- out premount. Getting this fixed for lenny would be appreciated. Documenting the pb in http://wiki.debian.org/EtchAndAHalf?highlight=%28EtchAndAHalf%29 might help others. As a side not, I would have appreciated a quick fix with the hard coded sleep [1|2] instead of the undocumented rootdelay approch for etch. Getting bitten by 2 years old bug [#366175] in debian stable is annoying. @+, Fab DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 UUID=be7f596f:e7ec06aa:9493fbbb:7d3be05a devices=/dev/sda2,/dev/sdb2 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=d8569b32:d1f063b0:b2cbc7fc:60944e9b devices=/dev/sda5,/dev/sdb5 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=c7758f0c:5c84bf52:8d369270:bf854ddc devices=/dev/sda6,/dev/sdb6 MD_HOMEHOST='proxy' MD_DEVPAIRS='/dev/md0:raid1 /dev/md1:raid1 /dev/md2:raid1' MD_LEVELS='raid1' MD_DEVS='/dev/md0' MD_MODULES='raid1' Initializing cgroup subsys cpuset Linux version 2.6.24-etchnhalf.1-686 (Debian 2.6.24-6~etchnhalf.4) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Jul 21 11:17:43 UTC 2008 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 0010 - dffc (usable) BIOS-e820: dffc - dffcfc00 (ACPI data) BIOS-e820: dffcfc00 - d000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - fec9 (reserved) BIOS-e820: fed0 - fed00400 (reserved) BIOS-e820: fee0 - fee1 (reserved) BIOS-e820: ffb0 - 0001 (reserved) BIOS-e820: 0001 - 00012000 (usable) Warning only 4GB will be used. Use a HIGHMEM64G enabled kernel. 3200MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000fe710 Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 229376 HighMem229376 - 1048576 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 - 1048576 DMI 2.3 present. ACPI: RSDP 000FD5B0, 0014 (r0 DELL ) ACPI: RSDT 000FD5C4, 0038 (r1 DELL PE BKC 1 MSFT 10A) ACPI: FACP 000FD620, 0074 (r1 DELL PE BKC 1 MSFT 10A) ACPI: DSDT DFFC, 3CCD (r1 DELL PE BKC 1 MSFT 10E) ACPI: FACS DFFCFC00, 0040 ACPI: APIC 000FD694, 00E0 (r1 DELL PE BKC 1 MSFT 10A) ACPI: SPCR 000FD774, 0050 (r1 DELL PE BKC 1 MSFT 10A) ACPI: HPET 000FD7C4, 0038 (r1 DELL PE BKC 1 MSFT 10A) ACPI: MCFG 000FD7FC, 003C (r1 DELL PE BKC 1 MSFT 10A) ACPI: PM-Timer IO Port: 0x808 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) Processor #6 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) Processor #1 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled) Processor #7 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x05] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x05] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0]) IOAPIC[0]:
Processing of initramfs-tools_0.92f_amd64.changes
initramfs-tools_0.92f_amd64.changes uploaded successfully to localhost along with the files: initramfs-tools_0.92f.dsc initramfs-tools_0.92f.tar.gz initramfs-tools_0.92f_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Enable amd64 Xen on trunk
On Tue, 2008-08-12 at 11:25 +0200, Bastian Blank wrote: On Tue, Aug 12, 2008 at 08:40:09AM +0100, Ian Campbell wrote: CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m +CONFIG_XEN_KBDDEV_FRONTEND=y =m? CONFIG_FB_TRIDENT=m # CONFIG_FB_TRIDENT_ACCEL is not set CONFIG_FB_VIRTUAL=m +CONFIG_XEN_FBDEV_FRONTEND=y =m? These are currently already =y due to the Kconfigs having default y in them. They could be made modular but I'm not sure how this would impact d-i where I'm am considering enabling graphical install mode for Xen http://lists.debian.org/debian-boot/2008/08/msg00274.html Since this is trunk we could switch to =m now and figure out d-i later for Lenny+1 (or +0.5). On the other hand VFB is somewhat to Xen like CONFIG_FB_VESA is to native so an argument could be made for keeping it builtin. I'll do a build and try and see what the size impact is. If we do go for =m I'd do it in a separate changeset to this one. Ian. -- Ian Campbell Current Noise: Firebird - I Wish You Well broad-mindedness, n: The result of flattening high-mindedness out. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434138: Boot failure from software-RAID1 in etch during upgrade to 2.4.24-etchnhalf.1-686
Fabrice LORRAIN a écrit : Hello, ... ... Failure: failed to start /dev/md0 Hmmm, missing part of my cut en paste, sorry, better read : ... Begin: Assembling MD array /dev/md0 ... mdadm: no devices found for /dev/md0 Failure: failed to start /dev/md0 Done. @+, Fab -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
initramfs-tools_0.92f_amd64.changes ACCEPTED
Accepted: initramfs-tools_0.92f.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.92f.dsc initramfs-tools_0.92f.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.92f.tar.gz initramfs-tools_0.92f_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.92f_all.deb Override entries for your package: initramfs-tools_0.92f.dsc - source utils initramfs-tools_0.92f_all.deb - optional utils Announcing to [EMAIL PROTECTED] Closing bugs: 490875 493238 494027 494257 494433 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot failure from software-RAID1 in etch during upgrade to 2.4.24-etchnhalf.1-686
Hi all, As reported in #434138, in some cases, upgrading to etchnhalf + software raid doesn't work. The quick fix is to use delayroot=n as a kernel parameter. This information might be a helpful addition for [1]. Also, it seems that [1] [2] hadn't been updated since etchnhalf released, removing all the will, and may would help understand where we stand. Thanks, @+, Fab [1] http://wiki.debian.org/EtchAndAHalf?highlight=%28etchand%29. [2] http://wiki.debian.org/EtchAndAHalf/ReleaseNotes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490875: marked as done (initramfs-tools: Incorrect warning message on upgrade if busybox is not installed)
Your message dated Tue, 12 Aug 2008 09:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#490875: fixed in initramfs-tools 0.92f has caused the Debian Bug report #490875, regarding initramfs-tools: Incorrect warning message on upgrade if busybox is not installed 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 [EMAIL PROTECTED] immediately.) -- 490875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490875 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: initramfs-tools Version: 0.92e Severity: minor When upgrading recently I noticed initramfs-tools give the following warning: Warning: Busybox is required for successful boot! ... but it isn't. I shut down, and rebooted perfectly successfully. This happened on two different machines (neither has busybox installed any more). Both are fine. Surely, if this warning were to be true, and busybox were truly necessary for a successful boot, then initramfs-tools should surely depend on busybox rather than merely recommending it. Regards, CC -- Package-specific info: -- /proc/cmdline root=/dev/md0 ro -- /proc/filesystems cramfs ext3 -- lsmod Module Size Used by ip6table_filter 3072 1 iptable_raw 2688 0 xt_comment 2112 0 xt_policy 3776 0 ipt_ULOG8964 14 ipt_TTL 2560 0 ipt_ttl 2176 0 ipt_TOS 2496 0 ipt_tos 1920 0 ipt_SAME2688 0 ipt_REJECT 4736 4 ipt_REDIRECT2368 1 ipt_recent 9176 0 ipt_owner 2240 0 ipt_NETMAP 2368 0 ipt_MASQUERADE 3904 1 ipt_LOG 6272 0 ipt_iprange 2112 0 ipt_ECN 3200 0 ipt_ecn 2496 0 ipt_CLUSTERIP 8900 0 ipt_ah 2176 0 ipt_addrtype2176 0 nf_nat_tftp 2176 0 nf_nat_snmp_basic 10308 0 nf_nat_sip 4864 0 nf_nat_pptp 3968 0 nf_nat_proto_gre3012 1 nf_nat_pptp nf_nat_irc 3008 0 nf_nat_h323 7552 0 nf_nat_ftp 3520 0 nf_nat_amanda 2688 0 ts_kmp 2496 5 nf_conntrack_amanda 5440 1 nf_nat_amanda nf_conntrack_tftp 6036 1 nf_nat_tftp nf_conntrack_sip9876 1 nf_nat_sip nf_conntrack_proto_sctp 8840 0 nf_conntrack_pptp 7168 1 nf_nat_pptp nf_conntrack_proto_gre 6080 1 nf_conntrack_pptp nf_conntrack_netlink25152 0 nf_conntrack_netbios_ns 3328 0 nf_conntrack_irc7320 1 nf_nat_irc nf_conntrack_h323 48988 1 nf_nat_h323 ipv6 239460 57 nf_conntrack_h323 nf_conntrack_ftp9984 1 nf_nat_ftp xt_tcpmss 2496 0 xt_pkttype 2176 4 xt_physdev 2896 0 xt_NFQUEUE 2240 0 xt_NFLOG2368 0 xt_multiport3456 4 xt_MARK 2560 0 xt_mark 2176 0 xt_mac 2176 0 xt_limit2880 0 xt_length 2240 0 xt_helper 3072 0 xt_hashlimit 10252 0 ip6_tables 13860 2 ip6table_filter,xt_hashlimit xt_DSCP 2688 0 xt_dscp 2432 0 xt_dccp 3588 0 xt_conntrack3072 3 xt_CONNMARK 3392 0 xt_connmark 2624 0 xt_CLASSIFY 2112 0 xt_tcpudp 3392 79 xt_state2752 20 iptable_nat 7556 1 nf_nat 18348 14 ipt_SAME,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,nf_conntrack_netlink,iptable_nat nf_conntrack_ipv4 18124 25 iptable_nat nf_conntrack 61000 29 ipt_MASQUERADE,ipt_CLUSTERIP,nf_nat_tftp,nf_nat_snmp_basic,nf_nat_sip,nf_nat_pptp,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,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_helper,xt_conntrack,xt_CONNMARK,xt_connmark,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 iptable_mangle 3136 1 nfnetlink 6168 4 nf_conntrack_netlink,nf_nat,nf_conntrack_ipv4,nf_conntrack iptable_filter 3264 1 ip_tables 12708 4
Bug#494257: marked as done (Please make log_begin_msg not emit trailing newline)
Your message dated Tue, 12 Aug 2008 09:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#494257: fixed in initramfs-tools 0.92f has caused the Debian Bug report #494257, regarding Please make log_begin_msg not emit trailing newline 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 [EMAIL PROTECTED] immediately.) -- 494257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494257 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: initramfs-tools Version: 0.92e Severity: minor Tags: patch Hi, Please make log_begin_msg not emit a trailing newline - this makes the non- quiet output cleaner and results in half as many lines being emitted. For example: Begin: Finding root filesytem ... Done. Becomes: Begin: Finding root filesytem ... done. Patch attached - it also adds a space and alters the case of done for symmetry. This would be especially useful in Debian Live where we show a large number of these messages by default. Regards, -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 diff -urNad initramfs-tools-0.92e.orig/scripts/functions initramfs-tools-0.92e/scripts/functions --- initramfs-tools-0.92e.orig/scripts/functions2008-08-08 03:34:46.0 +0100 +++ initramfs-tools-0.92e/scripts/functions 2008-08-08 03:49:14.0 +0100 @@ -3,22 +3,22 @@ _log_msg() { if [ $quiet = y ]; then return; fi - echo $@ + printf $@ } log_success_msg() { - _log_msg Success: $@ + _log_msg Success: [EMAIL PROTECTED] } log_failure_msg() { - _log_msg Failure: $@ + _log_msg Failure: [EMAIL PROTECTED] } log_warning_msg() { - _log_msg Warning: $@ + _log_msg Warning: [EMAIL PROTECTED] } log_begin_msg() @@ -26,7 +26,7 @@ if [ -x /sbin/usplash_write ]; then /sbin/usplash_write TEXT $@ fi - _log_msg Begin: $@ ... + _log_msg Begin: $@ ... } log_end_msg() @@ -34,7 +34,7 @@ if [ -x /sbin/usplash_write ]; then /sbin/usplash_write SUCCESS ok fi - _log_msg Done. + _log_msg done.\n } panic() signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.92f We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive: initramfs-tools_0.92f.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.92f.dsc initramfs-tools_0.92f.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.92f.tar.gz initramfs-tools_0.92f_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.92f_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems [EMAIL PROTECTED] (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Aug 2008 11:09:11 +0200 Source: initramfs-tools Binary: initramfs-tools Architecture: source all Version: 0.92f Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: maximilian attems [EMAIL PROTECTED] Description: initramfs-tools - tools for generating an initramfs Closes: 490875 493238 494027 494257 494433 Changes: initramfs-tools (0.92f) unstable; urgency=medium . [ maximilian attems ] * mkinitramfs: only lvm2 initramfs has busybox dep. (closes: #490875) * mkinitramfs: Fix usage and man outfile arg is not optional. (closes: #493238) * preinst fix vol_id path. (closes: #494433) * update-initramfs: run_bootloader() invoke flash-kernel and glantank- update-kernel in order to have latest initramfs flashed on triggered update. Thanks to Joey Hess [EMAIL PROTECTED]. * debian/control: Newer standards version without changes. . [ Chris Lamb ] * make log_begin_msg not emit trailing newline (closes: #494257) . [ Martin Michlmayr ] * MODULES=dep boot fix for Orion. (closes: #494027) Checksums-Sha1: ab2beff55de10868126adc5d6c78b576960f3dc0 1004 initramfs-tools_0.92f.dsc
Bug#494433: marked as done (/sbin/vol_id: No such file or directory in preinst)
Your message dated Tue, 12 Aug 2008 09:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#494433: fixed in initramfs-tools 0.92f has caused the Debian Bug report #494433, regarding /sbin/vol_id: No such file or directory in preinst 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 [EMAIL PROTECTED] immediately.) -- 494433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494433 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: initramfs-tools Version: 0.92e Tags: patch preinst contains the following lines: 25 elif [ -x /lib/udev/vol_id ]; then 26 UUID=$(/sbin/vol_id -u $RESUME || true) 27 fi Line 26 clearly is a copypaste error in that it should read /lib/udev/vol_id instead of /sbin/vol_id. Changing this should fix the bug immediately (thus tagging patch). Best, Michael pgpreHOaCZ8bt.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.92f We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive: initramfs-tools_0.92f.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.92f.dsc initramfs-tools_0.92f.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.92f.tar.gz initramfs-tools_0.92f_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.92f_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems [EMAIL PROTECTED] (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Aug 2008 11:09:11 +0200 Source: initramfs-tools Binary: initramfs-tools Architecture: source all Version: 0.92f Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: maximilian attems [EMAIL PROTECTED] Description: initramfs-tools - tools for generating an initramfs Closes: 490875 493238 494027 494257 494433 Changes: initramfs-tools (0.92f) unstable; urgency=medium . [ maximilian attems ] * mkinitramfs: only lvm2 initramfs has busybox dep. (closes: #490875) * mkinitramfs: Fix usage and man outfile arg is not optional. (closes: #493238) * preinst fix vol_id path. (closes: #494433) * update-initramfs: run_bootloader() invoke flash-kernel and glantank- update-kernel in order to have latest initramfs flashed on triggered update. Thanks to Joey Hess [EMAIL PROTECTED]. * debian/control: Newer standards version without changes. . [ Chris Lamb ] * make log_begin_msg not emit trailing newline (closes: #494257) . [ Martin Michlmayr ] * MODULES=dep boot fix for Orion. (closes: #494027) Checksums-Sha1: ab2beff55de10868126adc5d6c78b576960f3dc0 1004 initramfs-tools_0.92f.dsc ad5e9b9a909b67826312bbe0b7b5f5f634677dff 66586 initramfs-tools_0.92f.tar.gz e7a565d10f14b11a4ddfee0947d569ce9e90f7c2 73516 initramfs-tools_0.92f_all.deb Checksums-Sha256: 1aa3b9bf25bcb12566aae815a31004d22fbeb1aeb7c16bce8e9e13f0521f69bb 1004 initramfs-tools_0.92f.dsc 285ee4734068f2d9a2b3ae904f479954958d16fea5fdf58f4d73ce1b99e4 66586 initramfs-tools_0.92f.tar.gz 4f7bc9c8234196f39ca5e3c4cce898461b67ec250d4210d244d6082757014251 73516 initramfs-tools_0.92f_all.deb Files: 5fa85bead74fbaaa951e67c67fbef68e 1004 utils optional initramfs-tools_0.92f.dsc 2484226382c931de4a144b5c954e7831 66586 utils optional initramfs-tools_0.92f.tar.gz 080e14eb933888e4a1a29a6773be64b8 73516 utils optional initramfs-tools_0.92f_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkihWawACgkQeW7Lc5tEHqg5HACfbhqfgAISZsdwIxE23k4mnMx8 HoMAoLCBUiIUN33d46NjLmvZchhLgr8B =ExM5 -END PGP SIGNATURE- ---End Message---
Bug#493238: marked as done (initramfs-tool: wrong synopsis and usage message)
Your message dated Tue, 12 Aug 2008 09:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#493238: fixed in initramfs-tools 0.92f has caused the Debian Bug report #493238, regarding initramfs-tool: wrong synopsis and usage message 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 [EMAIL PROTECTED] immediately.) -- 493238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493238 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: initramfs-tool Version: 0.92e Tags: patch Hi, I tried to create an initrd and got: debian:~# mkinitramfs 2.6.26 Usage: /usr/sbin/mkinitramfs [OPTION]... -o outfile [version] Options: -d confdir Specify an alternative configuration directory. -k Keep temporary directory used to make the image. -o outfile Write to outfile. -r root Override ROOT setting in mkinitrd.conf. See mkinitramfs(8) for further details. Mhm, strange ... I opened mkinitramfs(8) which advises: mkinitramfs [-d confdir] [-k] [-o outfile] [-r root] [-v] [version] Nevertheless it seems that -o outfile is *not* optional and required. Also in the Usage line I don't know how to parse -o outfile. Why do you use ? I suggest to change the manpage to mkinitramfs [-d confdir] [-k] -o outfile [-r root] [-v] [version] and the Usage line to Usage: /usr/sbin/mkinitramfs [OPTION]... -o outfile [version] Jens ---End Message--- ---BeginMessage--- Source: initramfs-tools Source-Version: 0.92f We believe that the bug you reported is fixed in the latest version of initramfs-tools, which is due to be installed in the Debian FTP archive: initramfs-tools_0.92f.dsc to pool/main/i/initramfs-tools/initramfs-tools_0.92f.dsc initramfs-tools_0.92f.tar.gz to pool/main/i/initramfs-tools/initramfs-tools_0.92f.tar.gz initramfs-tools_0.92f_all.deb to pool/main/i/initramfs-tools/initramfs-tools_0.92f_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems [EMAIL PROTECTED] (supplier of updated initramfs-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Aug 2008 11:09:11 +0200 Source: initramfs-tools Binary: initramfs-tools Architecture: source all Version: 0.92f Distribution: unstable Urgency: medium Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: maximilian attems [EMAIL PROTECTED] Description: initramfs-tools - tools for generating an initramfs Closes: 490875 493238 494027 494257 494433 Changes: initramfs-tools (0.92f) unstable; urgency=medium . [ maximilian attems ] * mkinitramfs: only lvm2 initramfs has busybox dep. (closes: #490875) * mkinitramfs: Fix usage and man outfile arg is not optional. (closes: #493238) * preinst fix vol_id path. (closes: #494433) * update-initramfs: run_bootloader() invoke flash-kernel and glantank- update-kernel in order to have latest initramfs flashed on triggered update. Thanks to Joey Hess [EMAIL PROTECTED]. * debian/control: Newer standards version without changes. . [ Chris Lamb ] * make log_begin_msg not emit trailing newline (closes: #494257) . [ Martin Michlmayr ] * MODULES=dep boot fix for Orion. (closes: #494027) Checksums-Sha1: ab2beff55de10868126adc5d6c78b576960f3dc0 1004 initramfs-tools_0.92f.dsc ad5e9b9a909b67826312bbe0b7b5f5f634677dff 66586 initramfs-tools_0.92f.tar.gz e7a565d10f14b11a4ddfee0947d569ce9e90f7c2 73516 initramfs-tools_0.92f_all.deb Checksums-Sha256: 1aa3b9bf25bcb12566aae815a31004d22fbeb1aeb7c16bce8e9e13f0521f69bb 1004 initramfs-tools_0.92f.dsc 285ee4734068f2d9a2b3ae904f479954958d16fea5fdf58f4d73ce1b99e4 66586 initramfs-tools_0.92f.tar.gz 4f7bc9c8234196f39ca5e3c4cce898461b67ec250d4210d244d6082757014251 73516 initramfs-tools_0.92f_all.deb Files: 5fa85bead74fbaaa951e67c67fbef68e 1004 utils optional initramfs-tools_0.92f.dsc 2484226382c931de4a144b5c954e7831 66586 utils optional initramfs-tools_0.92f.tar.gz 080e14eb933888e4a1a29a6773be64b8 73516 utils optional initramfs-tools_0.92f_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkihWawACgkQeW7Lc5tEHqg5HACfbhqfgAISZsdwIxE23k4mnMx8 HoMAoLCBUiIUN33d46NjLmvZchhLgr8B
Bug#494800: linux-image-2.6.26-1-686: usb-storage broken, media size not detected
Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: important Hi, today I found my flash disks stopped working with linux 2.6.26. Attached are kernel messages with kernel 2.6.25 - ok and with 2.6.26 for the same USB flash disk. I tried to google for similar problems, and found this: http://lkml.org/lkml/2008/7/29/459 Best Regards -- Zito -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=cs_CZ.ISO-8859-2 (charmap=ISO-8859-2) 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.23 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e 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-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-46GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information excluded [ 165.404983] usb 1-7: new high speed USB device using ehci_hcd and address 6 [ 165.538444] usb 1-7: configuration #1 chosen from 1 choice [ 165.538757] usb 1-7: New USB device found, idVendor=058f, idProduct=6387 [ 165.538767] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 165.538772] usb 1-7: Product: Mass Storage Device [ 165.538776] usb 1-7: Manufacturer: JetFlash [ 165.538780] usb 1-7: SerialNumber: W4UWVJ2E [ 165.705589] Initializing USB Mass Storage driver... [ 165.706978] scsi2 : SCSI emulation for USB Mass Storage devices [ 169.876481] usb-storage: device found at 6 [ 169.876487] usb-storage: waiting for device to settle before scanning [ 165.707175] usbcore: registered new interface driver usb-storage [ 165.707179] USB Mass Storage support registered. [ 170.654142] usb-storage: device scan complete [ 170.656716] scsi 2:0:0:0: Direct-Access JetFlash TS2GJFV308.07 PQ: 0 ANSI: 2 [ 174.904718] sd 2:0:0:0: [sdb] 3969022 512-byte hardware sectors (2032 MB) [ 174.905323] sd 2:0:0:0: [sdb] Write Protect is off [ 174.905331] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 174.905336] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 174.907904] sd 2:0:0:0: [sdb] 3969022 512-byte hardware sectors (2032 MB) [ 174.908599] sd 2:0:0:0: [sdb] Write Protect is off [ 174.908609] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 174.908613] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 174.908619] sdb: sdb1 [ 175.91] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 175.222365] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 242.520149] usb 5-7: new high speed USB device using ehci_hcd and address 6 [ 242.652674] usb 5-7: configuration #1 chosen from 1 choice [ 242.653817] usb 5-7: New USB device found, idVendor=058f, idProduct=6387 [ 242.653829] usb 5-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 242.653835] usb 5-7: Product: Mass Storage Device [ 242.653842] usb 5-7: Manufacturer: JetFlash [ 242.653848] usb 5-7: SerialNumber: W4UWVJ2E [ 242.841050] Initializing USB Mass Storage driver... [ 242.841050] scsi2 : SCSI emulation for USB Mass Storage devices [ 242.841050] usbcore: registered new interface driver usb-storage [ 242.841050] USB Mass Storage support registered. [ 242.841050] usb-storage: device found at 6 [ 242.841050] usb-storage: waiting for device to settle before scanning [ 247.864483] usb-storage: device scan complete [ 247.864483] scsi scan: INQUIRY result too short (5), using 36 [ 247.864483] scsi 2:0:0:0: Direct-Access PQ: 0 ANSI: 0 [ 247.876768] sd 2:0:0:0: [sdb] Sector size 0 reported, assuming 512. [ 247.876768] sd 2:0:0:0: [sdb] 1 512-byte hardware sectors (0 MB) [ 247.877020] sd 2:0:0:0: [sdb] Write Protect is off [ 247.877020] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 247.877020] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 247.877647] sd 2:0:0:0: [sdb] Sector size 0 reported, assuming 512. [ 247.877647] sd 2:0:0:0: [sdb] 1 512-byte hardware sectors (0 MB) [ 247.877977] sd 2:0:0:0: [sdb] Write Protect is off [ 247.877977] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 247.877977] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 247.877977] sdb: sdb1 [ 248.199041] sdb: p1 exceeds device capacity [ 248.199251] sd 2:0:0:0: [sdb] Attached SCSI disk [ 248.199328] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 248.598836] attempt to access beyond end of device [ 248.598836] sdb: rw=0, want=64, limit=1 [ 248.598836] Buffer I/O error on device sdb1, logical block 0 [ 248.598836] attempt to access
Bug#494445: first debian openvz 2.6.26 bugs
On 11 August 2008 19:39:35 maximilian attems wrote: hello, could you please take a look at: * oops on load of nf_conntrack_ipv6 http://bugs.debian.org/494445 IPv6 conntrack doesn't work yet. It will be finished in this week. * nfsd module trouble http://bugs.debian.org/494384 Sorry, I didn't understand this notes: I upgraded from 2.6.25-2 to 2.6.26-1-openvz-686. After reboot, the nfsd module fails to load with this error message: nfsd loads without error if I boot the 2.6.26-1-686 kernel instead. That was loaded and then error occurs? thanks -- Thank, Vitaliy Gusev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
Am Monday 11 August 2008 20:40:51 schrieben Sie: On Tuesday 05 August 2008 01:06:35 pm Uwe Bugla wrote: (Snip) OK, let's back way up. Apart from the confusing messages, it seems like the real problem is related to this modprobe config line: options parport_pc io=0x378,0x278 irq=7,5 With that line present, I think you have: parport0 at port 0x378, irq 7 parport1 at port 0x278, irq 5 ad1816a at ports 0x220, 0x388, 0x500, irq 10, dma 1, 3 ad1816a MPU401 at port 0x300, irq disabled Without that line, it sounds like you have this: parport0 at port 0x378, irq ? parport1 at port 0x278, irq disabled (polling) ad1816a at ports 0x220, 0x388, 0x500, irq 5, dma 1, 3 ad1816a MPU401 at port 0x300, irq ? (maybe 7?) If the parallel ports only have 5 and 7 as IRQ possibilities, I can imagine how loading the ad1816a driver first might claim those IRQs, leaving them unavailable for parport_pc. But all your logs show parport_pc being loaded first. And I would think that if ad1816a were loaded first, it would claim both 5 and 7, leaving *both* parallel ports in polling mode. If this is indeed the problem, can you send a dmesg for this failing case? (Try dmesg -s64000; the first part of the log should show parport resource info, but it is truncated in the logs you posted). What would you think of something like the patch below? It doesn't fix anything, but maybe it would help show what's going on. diff --git a/drivers/pnp/quirks.c b/drivers/pnp/quirks.c index 0bdf9b8..6bcf17b 100644 --- a/drivers/pnp/quirks.c +++ b/drivers/pnp/quirks.c @@ -182,6 +182,7 @@ static void quirk_add_irq_optional_dependent_sets(struct pnp_dev *dev) unsigned int num_sets, i, set; struct pnp_irq *irq; + dev_info(dev-dev, adding MPU configurations with optional IRQ\n); num_sets = dev-num_dependent_sets; for (i = 0; i num_sets; i++) { new_option = pnp_clone_dependent_set(dev, i); diff --git a/sound/isa/ad1816a/ad1816a.c b/sound/isa/ad1816a/ad1816a.c index 68f1260..374d1d0 100644 --- a/sound/isa/ad1816a/ad1816a.c +++ b/sound/isa/ad1816a/ad1816a.c @@ -111,14 +111,14 @@ static int __devinit snd_card_ad1816a_pnp(int dev, struct snd_card_ad1816a *acar acard-devmpu = pnp_request_card_device(card, id-devs[1].id, NULL); if (acard-devmpu == NULL) { mpu_port[dev] = -1; - snd_printk(KERN_WARNING PFX MPU401 device busy, skipping.\n); + dev_warn(acard-devmpu-dev, MPU401 device busy, skipping\n); } pdev = acard-dev; err = pnp_activate_dev(pdev); if (err 0) { - printk(KERN_ERR PFX AUDIO PnP configure failure\n); + dev_err(pdev-dev, audio PNP configuration failed\n); return -EBUSY; } @@ -127,6 +127,11 @@ static int __devinit snd_card_ad1816a_pnp(int dev, struct snd_card_ad1816a *acar dma1[dev] = pnp_dma(pdev, 0); dma2[dev] = pnp_dma(pdev, 1); irq[dev] = pnp_irq(pdev, 0); + dev_info(pdev-dev, OPL3 FM synth at port %#llx, codec at port %#llx, + playback DMA %d, capture DMA %d, IRQ %d\n, + (unsigned long long) fm_port[dev], + (unsigned long long) port[dev], + dma1[dev], dma2[dev], irq[dev]); if (acard-devmpu == NULL) return 0; @@ -135,12 +140,14 @@ static int __devinit snd_card_ad1816a_pnp(int dev, struct snd_card_ad1816a *acar err = pnp_activate_dev(pdev); if (err 0) { - printk(KERN_ERR PFX MPU401 PnP configure failure\n); + dev_err(pdev-dev, MPU401 PNP configuration failed\n); mpu_port[dev] = -1; acard-devmpu = NULL; } else { mpu_port[dev] = pnp_port_start(pdev, 0); mpu_irq[dev] = pnp_irq(pdev, 0); + dev_info(pdev-dev, MPU401 at port %#llx, IRQ %d\n, + (unsigned long long) mpu_port[dev], mpu_irq[dev]); } return 0; Hello Bjorn, OK, let's back way up. Apart from the confusing messages, it seems like the real problem is related to this modprobe config line: options parport_pc io=0x378,0x278 irq=7,5 With that line present, I think you have: parport0 at port 0x378, irq 7 parport1 at port 0x278, irq 5 ad1816a at ports 0x220, 0x388, 0x500, irq 10, dma 1, 3 ad1816a MPU401 at port 0x300, irq disabled A bit more precise: Case A: 1. IRQs 7 and 5 reserved for ISA use only (in BIOS) 2. entry options parport_pc io=0x378,0x278 irq=7,5 in etc/modprobe.d/arch/i386 activated parport0 at port 0x378, irq 7 parport1 at port 0x278, irq 5 ad1816a at ports 0x200 (ns558pnp - gameport), 0x388 (OPL 2,3), SS at 0x500, irq 10, dma 1 3 ad1816a MPU401 at port 0x300, irq disabled Case B: same preconditions as above, but: 2. entry options parport_pc io=0x378,0x278 irq=7,5 in etc/modprobe.d/arch/i386 commented out parport0 at port 0x378, irq 7 parport1 at port 0x278, irq
Bug#494384: first debian openvz 2.6.26 bugs
Vitaliy Gusev wrote: Sorry, I didn't understand this notes: I upgraded from 2.6.25-2 to 2.6.26-1-openvz-686. After reboot, the nfsd module fails to load with this error message: nfsd loads without error if I boot the 2.6.26-1-686 kernel instead. That was loaded and then error occurs? IMHO what the bug reporter means is nfsd loads fine with non-openvz kernels (both 2.6.25 and 2.6.26), but fails to load with openvz 2.6.26 kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The Talent War (Newsletter CO2 - 12th Aug)
(This is a Catch Mails certified e-newsletter sent to debian-kernel@lists.debian.org, to discontinue your mailings follow the instructions located at the end of this message.) __ McQuire Rens Jones Presents The creator of Good Boss Bad Boss Author of The Talent War, Kerry Larkan Live in Sri Lanka The Talent War is the 21st centurys definitive guide to modern business corporations most pressing problems: identifying and attracting talented people, and inducing them to stay in the organisation. As much of the developed world faces a rapidly ageing population and an entirely different mindset towards work emerges amongst a new generation of working individuals, companies nowadays can no longer rely on traditional, preset ideas and methods of attracting and retaining good staff. As the power of choice shifts from employer to employee, values and an ideal workplace environment will be more important than ever before for any business that hopes to be sustainable. a new dynamic between bosses and employees is imperative. Kerry Larkans The Talent War will show you how to become an employer of choice, and attract the best and the brightest on offer, and more crucially, to keep them working for you. Kerry Larkan is an acclaimed Australian consultant, author and international speaker Browse Kerrys website: www.KerryLarkan.com CEO Breakfast Forum Top Leaders | Top People | Top Secret 23rd September 2008 | Queens Court, TransAsia Hotel, Colombo Areas Covered - Why all the buzz about retention? - the myopia of success - values the heart of success - why would i want to work for you? - shared mind-set - followship, leadership or jump ship - are you falling behind, keeping up or pulling ahead? Management Event --- The Talent War - How to Find and Retain the Best People for Your Company 24th September 2008 | Kings Court, TransAsia Hotel, Colombo Areas Covered The First Wave The Case for Becoming an Employer of Choice - Introductions - Whats Changed and Why - Cost versus Benefits - The Business Case for Change - Exercise The Second Wave Its Not for the Faint Hearted --- - What Makes an Employer of Choice? - The Need for a Champion - Change Takes Time and Focus - Exercise The Third Wave Getting Results --- - Leadership Effects Everything - Creating the Right Context - Demographics and Recruitment - Exercise The Fourth Wave Making Change Stick Using the Right Tools - - 360º Feedback - Satisfaction Surveys - Strategic Alignment Survey - Talent Development The Fifth Wave A Road Map for Success -- - Key Messages - Alignment - How to Get Started CEO Breakfast Forum For Whom : Chairmen, CEOs, COOs Directors Date Time : 23rd September 2008 | 9.00 am to 11:00 am (Registration Breakfast 8:00 am to 8:50 am) Investment : Rs. 10,000/- + VAT (Registration No. 114301744 - 7000) Cheques to be drawn in favour of McQuire Rens Jones (Pvt) Ltd crossed A/c payee. Management Event For Whom : Business Leaders, Entrepreneurs, Senior Middle Management, Organizational Consultants, HR Practitioners anyone who wishes to recruit, motivate and retain the talented employee Date Time : 24th September 2008 | 9.00 am to 5:00 pm (Registration 8:30 am) Investment : Rs. 12,500/- + VAT (Registration No. 114301744 - 7000) Cheques to be drawn in favour of McQuire Rens Jones (Pvt) Ltd crossed A/c payee Registration McQuire Rens Jones (Pvt) Ltd (+94) 11 5 833 100 | (+94) 11 5 836 888 | (+94) 11 5 323 999 [EMAIL PROTECTED] | www.rensj.com Exclusive Print Media Partner - The Sunday Times, Daily mirror Electronic Media Partner - ART TV Electronic Radio Partner - EFM Official Telecom Partner - Tigo Official Hotel - Fortress -- The following information is a reminder of your current mailing list subscription: You are subscribed to the following list: Catch Offers - Sri Lanka using the following email: debian-kernel@lists.debian.org You may automatically unsubscribe from this list at any time by visiting the following URL: http://www.srilankamails.com/cgi-bin/pro/mail.cgi/u/co/ If the above URL is inoperable, make sure that you have copied the entire address. Some mail
Bug#493479: test build
hey Dave, I'm wondering if this is an occurrence of #494365. Can you test this build to see if it fixes this issue for you? http://people.debian.org/~dannf/bugs/494365/ Thanks for the test build. I just tried it, but the behavior remains unchanged: kernel freezes unless the boot parameter hpet=disabled is supplied. I read the 494365 BTS page first, and guessed that it probably would not fix my issue: when you replied that 494365 was later fixed during 2.6.27 development by [8004dd965b13b01a96def054d420f6df7ff22d53] I knew that this test build kernel would not fix mine. After I took Bastian's advice to bisect using git, I ended up with a nice git tree which I could use to obtain any version I wanted to test. One of the first things the LKML folks asked me to do was build an up-to-date 2.6.27 kernel, and I found it also freezes. Please note: my last message in this thread pretty much begged for a Debian Kernel Team member to go to bat for me because I felt that the LKML people were not going to respond. I was wrong. After I did some more digging, and added RCU problem to the subject line in my LKML posts, it started getting more attention. Since Saturday there has been much discussion, though not really any progress besides ruling out what the problem is not, but the right folks are scratching there heads about it. If someone on the kernel team did raise awareness for me with the kernel folks, I really appreciate it. In any case, it has been noticed at LKML, and I was asking for no more than that. Thanks Dann, Dave W. BTW: The LKML posts on this can be viewed (via the mixed up LKML archive web interface) starting at these links: http://www.uwsg.indiana.edu/hypermail/linux/kernel/0808.0/index.html#1723 http://www.uwsg.indiana.edu/hypermail/linux/kernel/0808.1/index.html#0117 http://www.uwsg.indiana.edu/hypermail/linux/kernel/0808.1/index.html#0523 http://www.uwsg.indiana.edu/hypermail/linux/kernel/0808.1/index.html#1272 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494822: linux-image-2.6.25-2-686: DVD-writing with VIA IDE controller produce kernel error hdd: status timeout
Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 Severity: normal When I use the writing-capabilities (in simulation!), after a while, the (simulated) writing process will terminate and my syslog begins to get filled with plenty of repeated kernel error messages related to my DVD-writer. My DVD-writer, from that time on, is unusable until the next reboot. The only thing I found to stop kernel error logging is to unload the ide_cd_mod module. Here attached, you will find my setup and what I exactly did to produce the problem. Please note that the first DVD-writing attempt did NOT trigger the error, thus I guess there is some randomness included. But I got the problem each time I tried to write at speed=1 (I guess, because the time to terminate the process is longer so more chance to trigger the problem). -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 03:23:20 UTC 2008 ** Command line: BOOT_IMAGE=Linux-2.6.25-2 ro root=301 ** Not tainted -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e 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.25-2-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.25-2-686 suggests: ii lilo 1:22.8-5 LInux LOader - The Classic OS load pn linux-doc-2.6.25 none (no description available) - setup and bug triggering, 23 juil, 18h - ~#uname -a Linux Olivier 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 GNU/Linux /var/log#apt-show-versions | grep image-2.6.25 linux-image-2.6.25-2-686/testing uptodate 2.6.25-6 ~#lsmod | grep ide_ ide_disk 13952 3 ide_cd_mod 32864 0 cdrom 31872 1 ide_cd_mod ide_pci_generic 4228 0 [permanent] ide_core 100312 4 ide_disk,ide_cd_mod,via82cxxx,ide_pci_generic ~#lspci | grep IDE 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) ~#wodim --devices wodim: Overview of accessible drives (2 found) : - 0 dev='/dev/hdc' rwrw-- : 'SAMSUNG' 'DVD-ROM SD-616Q' 1 dev='/dev/hdd' rwrw-- : 'PLEXTOR' 'DVDR PX-708A' - mounting a CD with mount /dev/hdc and mount /dev/hdd: works (I can read the content). Then I unmount and load an empty DVD in the Plextor drive. ~#hdparm /dev/hdd /dev/hdd: IO_support= 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) HDIO_GETGEO failed: Inappropriate ioctl for device ~#dvd+rw-mediainfo /dev/hdd INQUIRY:[PLEXTOR ][DVDR PX-708A ][1.02] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Current Write Speed: 4.0x1385=5540KB/s Write Speed #0:4.0x1385=5540KB/s Write Speed #1:2.0x1385=2770KB/s Write Speed #2:1.0x1385=1385KB/s GET [CURRENT] PERFORMANCE: Write Performance: 4.0x1385=5540KB/[EMAIL PROTECTED] - 2294911] Speed Descriptor#0:02/2298495 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:02/2298495 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#2:02/2298495 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2298496*2KB=4707319808 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: invisible incremental Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2297888*2KB Track Size:2297888*2KB READ CAPACITY: 0*2048=0 ~#wodim dev=/dev/hdd -dummy Fedora-9-x86_64-DVD.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. Device type: Removable CD-ROM Version: 0 Response Format: 1 Vendor_info: 'PLEXTOR ' Identification : 'DVDR PX-708A ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Using generic SCSI-3/mmc DVD-R(W)
Processed: tagging 491149
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 tags 491149 - patch Bug#491149: initramfs-tools: panic() won't print error message Tags were: patch Tags removed: patch End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475108: Missing build-dependencies
linux-kbuild-2.6 should build-depend linux-support-2.6.xx and on python2.4. Best regards, Martijn Grendelman smime.p7s Description: S/MIME Cryptographic Signature
Processed: closing 493957
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35.1 close 493957 Bug#493957: Orion/QNAP TS-109 II: possible sata_mv problems 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Timo Jyrinki [EMAIL PROTECTED] End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed (with 1 errors): your mail
Processing commands for controlbugs.debian.org: reopen 479709 Bug#479709: linux-image-2.6.25-1-amd64: Kernel 2.6.25 freezes after several hours of uptime. System runs fine with .24 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. found linux-2.6/2.6.26-1 Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Enable amd64 Xen on trunk
On Tue, 2008-08-12 at 10:46 +0100, Ian Campbell wrote: They could be made modular but I'm not sure how this would impact d-i where I'm am considering enabling graphical install mode for Xen http://lists.debian.org/debian-boot/2008/08/msg00274.html Since this is trunk we could switch to =m now and figure out d-i later for Lenny+1 (or +0.5). On the other hand VFB is somewhat to Xen like CONFIG_FB_VESA is to native so an argument could be made for keeping it builtin. I'll do a build and try and see what the size impact is. I make it around 10k on the vmlinux (3489678-3479036=10642) or 6k on the bzImage (1542-1536). Changing CONFIG_XEN_FBDEV_FRONTEND and CONFIG_XEN_KBDDEV_FRONTEND to =m also caused these symbols to follow: CONFIG_FB_SYS_FILLRECT CONFIG_FB_SYS_COPYAREA CONFIG_FB_SYS_IMAGEBLIT CONFIG_FB_SYS_FOPS $ cat sizes-y textdata bss dec hex filename 2145 168 02313 909 drivers/input/xen-kbdfront.o 286341412 252 30298765a drivers/input/built-in.o 3571 328 03899 f3b drivers/video/xen-fbfront.o 9976632407880 110886 1b126 drivers/video/built-in.o 2754338 276588 458752 3489678 353f8e vmlinux -rwxr-xr-x 1 ijc ijc 4.2M Aug 12 10:50 vmlinux* -rw-r--r-- 1 ijc ijc 1.6M Aug 12 11:09 arch/x86/boot/bzImage -rw-r--r-- 1 ijc ijc 1542 Aug 12 12:01 arch/x86/boot/bzImage $ cat sizes-m textdata bss dec hex filename 43621504 0586616ea drivers/input/xen-kbdfront.ko 20791344 03423 d5f drivers/input/xen-kbdfront.mod.o 2240 160 02400 960 drivers/input/xen-kbdfront.o 264871220 252 279596d37 drivers/input/built-in.o 74421664 091062392 drivers/video/xen-fbfront.ko 36151344 04959135f drivers/video/xen-fbfront.mod.o 3769 320 04089 ff9 drivers/video/xen-fbfront.o 9064229127880 101434 18c3a drivers/video/built-in.o 2744216 276068 458752 3479036 3515fc vmlinux -rwxr-xr-x 1 ijc ijc 4.2M Aug 12 11:10 vmlinux* -rw-r--r-- 1 ijc ijc 1.5M Aug 12 11:10 arch/x86/boot/bzImage -rw-r--r-- 1 ijc ijc 1536 Aug 12 12:00 arch/x86/boot/bzImage -- Ian Campbell Current Noise: Godflesh - Dead Head ... [concerning quotation marks] even if we *___did* quote anybody in this business, it probably would be gibberish. -- Thom McLeod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reopening 493957
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35.1 reopen 493957 Bug#493957: Orion/QNAP TS-109 II: possible sata_mv problems Bug reopened, originator not changed. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494842: versatile kernel doesn't boot
Package: linux-2.6 Version: 2.6.26-2 Severity: serious The current versatile kernel doesn't boot in QEMU. This bug should not stop 2.6.26 from migrating to testing though since versatile is not a platform that is used a lot. Aurelien Jarno looked at the problem and found: | It's because I have enabled tickless options in the kernel. I don't | know if it is actually a qemu or a kernel problem, but given we are | close to the release, the best is simply to disable this options. | Unfortunately I am afraid this will change the ABI... I'll disable the option when we change the ABI. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 479709 in 2.6.26-1
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 found 479709 2.6.26-1 Bug#479709: linux-image-2.6.25-1-amd64: Kernel 2.6.25 freezes after several hours of uptime. System runs fine with .24 Bug marked as found in version 2.6.26-1. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479709: reopened
I can confirm that a) the patch is applied and b) the system still freezes. Thus I reopen the bug. I ran 2.6.26 without a problem for quite some time until I discovered that my chrony still wasn't starting. After starting it again the system froze in a matter of seconds. Could anyone of you NOT experiencing the problem so far try running chrony to see whether this triggers it? Also for those of you having the same problem, does disabling chrony help? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 493479 is forwarded to http://lkml.org/lkml/2008/8/9/70
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 forwarded 493479 http://lkml.org/lkml/2008/8/9/70 Bug#493479: linux-image-2.6.26-1-amd64: 2.6.26-1 freezes soon after boot, a regression compared to 2.6.25-2 Noted your statement that Bug has been forwarded to http://lkml.org/lkml/2008/8/9/70. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 479709
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 tags 479709 - pending Bug#479709: linux-image-2.6.25-1-amd64: Kernel 2.6.25 freezes after several hours of uptime. System runs fine with .24 Tags were: pending fixed-upstream Tags removed: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 479709
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 tags 479709 - fixed-upstream Bug#479709: linux-image-2.6.25-1-amd64: Kernel 2.6.25 freezes after several hours of uptime. System runs fine with .24 Tags were: fixed-upstream Tags removed: fixed-upstream End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: closing 493994
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.29~bpo40+1 close 493994 2.6.26-2 Bug#493994: linux-modules-extra-2.6_2.6.26-1(sparc/unstable): FTBFS on sparc 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.6.26-2, send any further explanations to Martin Zobel-Helas [EMAIL PROTECTED] End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494360: linux-image-2.6.26-1-686: dl2k fails to work since 2.6.24-6
http://bugzilla.kernel.org/show_bug.cgi?id=11311 Thank you in advance, D.I. Kulagin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote: A bit more precise: Case A: 1. IRQs 7 and 5 reserved for ISA use only (in BIOS) 2. entry options parport_pc io=0x378,0x278 irq=7,5 in etc/modprobe.d/arch/i386 activated parport0 at port 0x378, irq 7 parport1 at port 0x278, irq 5 ad1816a at ports 0x200 (ns558pnp - gameport), 0x388 (OPL 2,3), SS at 0x500, irq 10, dma 1 3 ad1816a MPU401 at port 0x300, irq disabled Case B: same preconditions as above, but: 2. entry options parport_pc io=0x378,0x278 irq=7,5 in etc/modprobe.d/arch/i386 commented out parport0 at port 0x378, irq 7 parport1 at port 0x278, irq disabled (polling) ad1816a at ports 0x200 (ns558pnp - gameport), 0x388 (OPL 2,3), SS at 0x500, irq 5, dma 1 3 ad1816a MPU401 at port 0x300, irq 10 Thanks a lot for your detailed observations. Your dmesg logs are still missing the interesting part at the beginning. Can you find the entire log in /var/log/messages or something similar? These lines are from your case C log, but the same thing probably happened in case B: parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378, irq 7 [PCSPP(,...)] parport_pc 00:0a: driver attached parport1: PC-style at 0x278 [PCSPP(,...)] We found parport0 via PNPACPI, but you mentioned that parport1 is a non-PNP ISA card with jumpers on it. In that case, the parport_pc driver doesn't try to use an IRQ unless one is specified with a module parameter. It's possible the driver could guess somehow, but I don't know enough to propose any changes here. I think you could use options parport_pc io=0x278 irq=5, i.e., you probably only need to tell the driver about the non-PNP device. Case C: same preconditions as case B, but additionally: 1. no IRQs reserved for ISA use only (in BIOS) This option I would call PNP pure parport0 at port 0x378, irq 7 parport1 at port 0x278, irq disabled (polling) ad1816a at ports 0x200 (ns558pnp), 0x388 (OPL 2,3), SS at 0x500, irq 5, dma 1 3 ad1816a MPU401 at port 0x300, irq disabled The only difference here is that the MPU has no IRQ. You can see from the log how all the possibilities (5, 7, 9, 10, 11, 15) are already used by ad1816a, parport0, and some PCI devices. With IRQs 5 7 reserved for ISA use, PCI device 00:08.0 (aic7xxx) uses IRQ 11. With no IRQs reserved, that device uses IRQ 10. Without the beginning of the log, I can't tell whether Linux or the BIOS changed that assignment. PNP is supposed to notice IRQs that are in use by active PNP devices, as well as those that could possibly be used, so we can try to avoid them when we configure PCI interrupt links. But it looks like some of this logic is missing from ISAPNP. Can you try the experimental patch below to see whether it helps? It won't change parport, of course, but you might get an MPU IRQ. If the parallel ports only have 5 and 7 as IRQ possibilities, I can imagine how loading the ad1816a driver first might claim those IRQs, leaving them unavailable for parport_pc. Yes and No. IRQ 7 for parport 0 is out of discussion, as it is the traditional standard for the first parport. The traditional problem causing system crashes in earlier times was that both sound card and parport 1 would claim IRQ 5. The decision to put the second parport into polling mode while the PnP sound card grabs IRQ 5 is wrong. I don't think the kernel has enough information to make a different decision. The kernel doesn't know anything about the configuration of the non-PNP ISA card. I think you'd have to use a boot parameter like pnp_reserve_irq=5 to tell Linux that it can't use IRQ 5 when it configures the sound card. ... My only criticism within the desired case C (no additional screwing around done by user) consists of two points: 1. I'd prefer the second parport running with IRQ 5 instead of in polling mode. Yes, that would be good. But I think the only way to achieve this reliably is to use the pnp_reserve_irq=5 kernel parameter and the options parport_pc io=0x278 irq=5 module parameter. Otherwise the kernel doesn't know how the jumpers on the ISA parport card are set. 2. the state of MPU 401 is OK so far, but the messages are highly annoying: pnp: the driver 'mpu 401' has been registered MPU-401 device not found or device busy pnp: the driver 'mpu 401' has been unregistered I think we ought to just remove this message completely and add a new message when the driver claims a device, something like the attached patch does. ... 5. And if you expect some enlighting help from Documentation/sound/alsa/ALSA- Configuration.txt then you are completely lost in space. I find Linux sound completely incomprehensible myself. Fortunately, it's easy for me to live without it :-) Bjorn diff --git a/drivers/pnp/isapnp/core.c b/drivers/pnp/isapnp/core.c index 101a835..27596f0 100644 --- a/drivers/pnp/isapnp/core.c +++ b/drivers/pnp/isapnp/core.c @@ -42,6 +42,7 @@
Bug#494875: linux-image-2.6.25-2-686-bigmem: hangs after a while
Package: linux-image-2.6.25-2-686-bigmem Version: 2.6.25-7 Severity: critical Justification: breaks the whole system I've upgraded recently to kernel 2.6.25, used it for a while (couple of hourse, it's not on my primary machine). Today I noticed that it produces random hangs. First it crashed while doing a partimage from sda to sda. After that (and after doing an upgrade to 2.6.25-7 - it was 6 before, so it affects both packages) it hung while copying from sda to sdb (a USB hdd). The hang is the same in both cases: console is still active (receives keystrokes) but no command gets through. I can switch consoles, though (Alt-F1, Alt-F2) but obviously none of them work. I can press SysReq, and reboot from there. 2.6.24-7 is stable so far. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e 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.25-2-686-bigmem recommends: ii libc6-i6862.7-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.25-2-686-bigmem suggests: ii grub 0.97-46GRand Unified Bootloader (Legacy v pn linux-doc-2.6.25 none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 494875 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 494875 important Bug#494875: linux-image-2.6.25-2-686-bigmem: hangs after a while Severity set to `important' from `critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 494875 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.35 severity 494875 normal Bug#494875: linux-image-2.6.25-2-686-bigmem: hangs after a while Severity set to `normal' from `important' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
On Tuesday 12 August 2008 12:10:51 pm Bjorn Helgaas wrote: On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote: Case C: same preconditions as case B, but additionally: 1. no IRQs reserved for ISA use only (in BIOS) This option I would call PNP pure ... My only criticism within the desired case C (no additional screwing around done by user) consists of two points: 1. I'd prefer the second parport running with IRQ 5 instead of in polling mode. Yes, that would be good. But I think the only way to achieve this reliably is to use the pnp_reserve_irq=5 kernel parameter and the options parport_pc io=0x278 irq=5 module parameter. Otherwise the kernel doesn't know how the jumpers on the ISA parport card are set. One more thing: since you have a non-PNP ISA card, I don't think you can reliably use a pure PNP approach. In addition to the kernel and module parameters, I think you need to configure the BIOS to reserve IRQ 5 for ISA use. Otherwise, the BIOS might put some other device on IRQ 5. Of course, if you are content to run the second parport in polling mode, you wouldn't need the BIOS configuration. Bjorn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451422: pulseaudio: CPU time limit exhausted after resume
Something datapointish, maybe. My problem is also with pulseaudio exhausting the time limit, and I also use snd-hda-intel (on an Asus M2A-VM motherboard). But some things are different. It also happens after a fresh start, not only after resume, and it only started occuring with linux-image-2.6.26-1-686 (2.6.26-2), or at least I couldn't yet reproduce it with my previous linux-image-2.6.25-2-686 (2.6.25-7). Maybe it just needs more time with the older kernel, but with .26 it is pretty instant on this system. -- Michał Politowski Talking has been known to lead to communication if practiced carelessly. signature.asc Description: Digital signature
Re: Bug#489387: Please do not replace vserver with openvz.
Bastian Blank [EMAIL PROTECTED] writes: On Fri, Aug 08, 2008 at 04:42:03PM -0500, William Pitcock wrote: It appears the plan is to drop vserver in favour of openvz, offering openvz as an alternative and perhaps default is a good option, but please do not remove vservers, as there are real people who depend on this feature. No. OpenVZ is an alternative. VServer is currently not supported because upstream is lets say in hibernation. There is simply no working patch available. There is a working patch available as of yesterday for 2.6.25 and 2.6.25.2 which fixes both ext4 and xfs. It has had the 'dontuse' flag removed and is considered pre5. micah pgp6CQAgs5EhJ.pgp Description: PGP signature
Bug#494922: initramfs-tools: fails to include the ext4 module into the initramfs.
Package: initramfs-tools Severity: normal I switched my root fs from ext3 to ext4. The initramfs built by initramfs-tools doesn't include the ext4 module, making the system unbootable. I removed the package and installed yaird, which correctly identifies the dependency on ext4. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9-13 GNU cpio -- a program to manage ar ii findutils 4.4.0-2utilities for finding files--find, ii klibc-utils 1.5.12-1 small utilities built with klibc f ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii udev 0.125-3/dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: pn busybox | busybox-initramfs none (no description available) initramfs-tools suggests no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]