Bug#502849: Possible fix
I installed r12453 sid snapshot xen kernel. It works: xen dom0 boots on all my 3 test PCs. Attached to this message you can find Gigabyte P35-DS3L motherboard PC boot log. Thanks for your support. Original Message Subject: Bug#502849: Possible fix From: Ian Campbell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: 27/11/2008 9.01 Executive summary: please try the r12453 sid snapshot once it appears. (XEN) Xen version 3.2-1 (Debian 3.2.1-2) ([EMAIL PROTECTED]) (gcc version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008 (XEN) Command line: console=com1,vga com1=115200,8n1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009f800 (usable) (XEN) 0009f800 - 000a (reserved) (XEN) 000f - 0010 (reserved) (XEN) 0010 - 7fee (usable) (XEN) 7fee - 7fee3000 (ACPI NVS) (XEN) 7fee3000 - 7fef (ACPI data) (XEN) 7fef - 7ff0 (reserved) (XEN) f000 - f400 (reserved) (XEN) fec0 - 0001 (reserved) (XEN) System RAM: 2046MB (2095612kB) (XEN) Xen heap: 14MB (15012kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 6:15 APIC version 20 (XEN) Processor #1 6:15 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2400.048 MHz processor. (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz stepping 0d (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz stepping 0d (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) - Using new ACK method (XEN) Platform timer overflows in 14998 jiffies. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x20 - 0x631918 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 7800-7a00 (472725 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8020-80631918 (XEN) Init. ramdisk: 80632000-81857e00 (XEN) Phys-Mach map: 81858000-81c034a8 (XEN) Start info:81c04000-81c044a4 (XEN) Page tables: 81c05000-81c18000 (XEN) Boot stack:81c18000-81c19000 (XEN) TOTAL: 8000-8200 (XEN) ENTRY ADDRESS: 8020 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x1225e00, start at 0x80632000 (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input - DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 104kB init memory. Kernel alive kernel direct mapping tables up to 75e95000 @ 1c18000-1fcb000 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-xen-amd64 (Debian 2.6.26-12~snapshot.12453) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23+1)) #1 SMP Fri Nov 28 04:06:47 UTC 2008 [0.00] Command line: root=/dev/sda7 ro console=tty0 [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 75e95000 (usable) [0.00] max_pfn_mapped = 482965 [0.00] init_memory_mapping [0.00] DMI 2.4 present. [0.00] early res: 0 [20-631917] TEXT DATA BSS [0.00] early res: 1 [632000-1c17fff] Xen provided [0.00] early res: 2 [1c18000-1fcbfff] PGTABLE [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 482965 [0.00] ACPI: RSDP 000F6A60, 0014 (r0 GBT ) [0.00] ACPI: RSDT 7FEE3040, 0038 (r1 GBTGBTUACPI 42302E31 GBTU 1010101) [0.00] ACPI: FACP 7FEE30C0, 0074 (r1 GBTGBTUACPI 42302E31 GBTU 1010101) [0.00] ACPI: DSDT 7FEE3180, 4B27 (r1 GBTGBTUACPI 1000 MSFT 10C) [0.00] ACPI: FACS 7FEE, 0040 [0.00] ACPI: HPET 7FEE7E00, 0038 (r1 GBTGBTUACPI 42302E31 GBTU 98) [0.00] ACPI: MCFG 7FEE7E80, 003C (r1
Processed: tagging 504668
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 504668 + pending Bug#504668: firmware-nonfree: Add License handler in gencontrol.py Tags were: patch Tags added: 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 449235
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 449235 + pending Bug#449235: Please add ipw2200 firmware There were no tags set. Tags added: 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 504671
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 504671 + pending Bug#504671: firmware-nonfree: Please add ipw2100 firmware Tags were: patch Tags added: 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]
Bug#506835: Info received ([Fwd: Re: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created])
I tried booting kernel 2.6.18-4-686 version 2.6.18.dfsg.1-12etch2 and was able to successfully modprobe eata and get the device files created. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502326: upstream bug assigned
Hi Moritz, I can confirm that the provided firmware fixes the problem on my machine. Its current uptime reached 5 hrs so far using a vanilla 2.6.27.6 i686 kernel (iwlagn driver). Cheers, Oliver Zhu Yi's answer seems to indicate that an updated firmware fixes the problem. Can you confirm that for the Lenny kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506835: DPT2044W SCSI adaptor with disk installed but no /dev/sd* devices created
Arthur Marsh wrote, on 28/11/08 20:33: The 2.6.18.dfsg.1-12etch2 kernel allowed me to modprobe eata and I received similar messages to those quoted above. The next newest kernel I can download is 2.6.24-etchnhalf.1-686. kernel 2.6.24-etchnhalf.1-686 had problems after modprobe eata Is there any site that has precompiled Debian kernels between 2.6.18.dfsg.1-1etch2 and 2.6.24-etchnhalf.1-686 ? Arthur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#281248: pm2fb does not work
On Thu, Nov 27, 2008 at 11:59:14PM +0100, Moritz Muehlenhoff wrote: Clint, since last year pm2fb seems to be under active maintenance again. Do you still own that machine, does it work for you with current kernels, such as the 2.6.24 kernel from Etch 4.0r4 or the Lenny kernel? Unfortunately I no longer have such a machine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503766: linux-image-2.6.26-1-amd64: intelfb puts console screen into standby
On Tue, Oct 28, 2008 at 09:19:53AM +0100, Olaf Zaplinski wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-8 Severity: important When intelfb is loaded, the screen goes into standby immediately. System is Dell Dimension E520. There have been few changes in intelfb since 2.6.26, could you try to reproduce this with 2.6.28-rc6 and file a bug at bugzilla.kernel.org if the problem still persists? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#507150: MMC_SDHCI_PC disabled on 2.6.27
Processing commands for [EMAIL PROTECTED]: reassign 507150 linux-2.6 Bug#507150: MMC_SDHCI_PC disabled on 2.6.27 Warning: Unknown package 'linux-image-2.6.27' Bug reassigned from package `linux-image-2.6.27' to `linux-2.6'. 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#405285: linux-image-2.6.18-3-sparc64: framebuffer broken in 2.6 since 2.6.8
On Tue, Jan 02, 2007 at 09:50:28PM +1100, Tim Connors wrote: Package: linux-image-2.6.18-3-sparc64 Version: 2.6.18-8 Severity: important Upon installing either of the sarge 2.6.8 or sid 2.6.18 kernels on my Sun Ultra10 with a Creator 3D card (as well as onboard ati rage 128, from my understanding), I get get a kernel that boots up without a console. It seems to be a well known problem with a solution of appending video=atyfb:off to silo; perhaps this should be done by default? Furthermore (probably related?), apparently the ffb driver is completely dead anyway from 2.6.8, and as such has been removed from the kernel: http://lkml.org/lkml/2005/1/5/33 If they are the same problems, is there any chance of getting this looked into? Presumably not being able to modprobe ffb (because it doesn't exist) is the reason why we also don't have working DRM under Xorg? Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440654: same problem with SMP machines
On Thu, Sep 13, 2007 at 03:42:36AM +0200, Bernd Zeimetz wrote: although no non-SMP kernel boots on this machine as reported in #440720, even the 2.6.18 SMP kernel from Etch just hangs the machine, just not as badly as the non-SMP kernel. Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#507150: MMC_SDHCI_PC disabled on 2.6.27
Package: linux-image-2.6.27 Version: 2.6.27-1 Severity: wishlist Hi, i tested debian kernel 2.6.27 from trunk and my ENE CB-710/2/4 Cardbus Controller doesn't not work because of MMC_SDHCI_PCI option not enabled. Recompiling the kernel with MMC_SDHCI_PCI=m solves the problem. Please consider to enable MMC_SDHCI_PCI kernel option. (just to remind ENE Controller has stopped to work since 2.6.26 kernel: see bug #496485 :-) ) Regards, Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463124: linux-image-2.6.22-3-686: Intel framebuffer modules fail unless intel-agp module is loaded
On Tue, Jan 29, 2008 at 06:43:48PM +0100, Alain Kalker wrote: Package: linux-image-2.6.22-3-686 Version: 2.6.22-6 Severity: important The i810fb module depends on agpgart module, but intel-agp module needs to be loaded before agpgart (and therefore i810fb) will use it. From searching the Web and the BTS, this seems to apply to intelfb as well. Does this behaviour still persist with current Lenny? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506586: Works with samba share from lenny
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For what it's worth, I have tried to stress test access to a samba share running on a second debian lenny system and it works flawlessly without any glitches. Unfortunately I don't know what software is running on the system that still crashes the kernel. Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkwSd8ACgkQC1NzPRl9qEV+SgCdHeC1La26kgim/nR09JF1tuvA YNYAn0OSeM1CLwXxK6afU+QKQvHBhxf3 =JUJj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-kbuild-2.6.27
Where you able to build this? It is not in trunk yet nor does there seem to be the dsc for it
Bug#281248: marked as done (pm2fb does not work)
Your message dated Fri, 28 Nov 2008 23:24:35 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#281248: pm2fb does not work has caused the Debian Bug report #281248, regarding pm2fb does not work 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.) -- 281248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281248 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kernel-image-2.6.8-1-sparc64 Version: 2.6.8-3 The Permedia2 framebuffer driver does not work on a SB100. It works in kernel-image-2.4.26-sparc64. ---End Message--- ---BeginMessage--- On Fri, Nov 28, 2008 at 04:57:05PM +, Clint Adams wrote: On Thu, Nov 27, 2008 at 11:59:14PM +0100, Moritz Muehlenhoff wrote: Clint, since last year pm2fb seems to be under active maintenance again. Do you still own that machine, does it work for you with current kernels, such as the 2.6.24 kernel from Etch 4.0r4 or the Lenny kernel? Unfortunately I no longer have such a machine. Closing the bug, since there's not much point in keeping it open. Cheers, Moritz ---End Message---
Processing of redhat-cluster_2.20080801-4+lenny1_i386.changes
redhat-cluster_2.20080801-4+lenny1_i386.changes uploaded successfully to localhost along with the files: redhat-cluster_2.20080801-4+lenny1.dsc redhat-cluster_2.20080801-4+lenny1.diff.gz cman_2.20080801-4+lenny1_i386.deb libcman2_2.20080801-4+lenny1_i386.deb libcman-dev_2.20080801-4+lenny1_i386.deb libdlm2_2.20080801-4+lenny1_i386.deb libdlm-dev_2.20080801-4+lenny1_i386.deb gfs-tools_2.20080801-4+lenny1_i386.deb gfs2-tools_2.20080801-4+lenny1_i386.deb gnbd-client_2.20080801-4+lenny1_i386.deb gnbd-server_2.20080801-4+lenny1_i386.deb rgmanager_2.20080801-4+lenny1_i386.deb redhat-cluster-suite_2.20080801-4+lenny1_all.deb redhat-cluster-source_2.20080801-4+lenny1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497875: linux-image-2.6.26-1-686 (2.6.26-4): virtualbox-ose - Kernel booting fails.
On Fri, Sep 05, 2008 at 09:55:34AM +0800, Patrick Yuen wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: important Hello, I am running lenny in virtualbox-ose (1.6.2-dfsg-4), kernel 2.6.24 works fine. The new kernel fails with message [0.824031] BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1 Does this error still occur with current Lenny, which has both a more recent kernel and a more recent virtualbox? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Different source package
Processing commands for [EMAIL PROTECTED]: reassign 350714 unionfs Bug#350714: nfs-kernel-server: Kernel NULL pointer dereference with unionfs and the NFS kernel server Bug reassigned from package `linux-2.6' to `unionfs'. 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]
Bug#348492: Serverworks CSB6 vs. kernel 2.6.12-10
On Tue, Jan 17, 2006 at 11:25:23AM +0100, Konrad Korzeniowski wrote: Package: linux-source-2.6.12 Version: 2.6.12-10 I'm using Fujitsu-Siemens TX200 (one HT proc) machine with Serverworks CSB6 ide controler. System is setup on SCSI disk so I have some possibilities to experiment. lspci -vvv [...] :00:0f.1 IDE interface: ServerWorks CSB6 RAID/IDE Controller (rev a0) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 1734:1012 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64, Cache Line Size: 0x10 (64 bytes) Region 0: I/O ports at ignored Region 1: I/O ports at ignored Region 2: I/O ports at ignored Region 3: I/O ports at ignored Region 4: I/O ports at 1400 [size=16] [...] System is Sarge but I've installed package in question (linux-source-2.6.12) from testing. Debian-way custom compilation (make-kpkg) with predefined (nothing changed) config is smooth, but I cannot make serverworks module run. modprobe serverworks loads without error and I can see it listed with lsmod. But there is no : SvrWks CSB6: IDE controller at PCI slot :00:0f.1 SvrWks CSB6: chipset revision 160 [...] in dmesg after module load, and I cannot access ide disks. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496410: redhat-cluster tmpfile fixes
Hi, please accept redhat-cluster 2.20080801-4+lenny1 which I have just uploaded to testing-proposed-updates: * Fix several tmpfile race conditions, among them CVE-2008-4192 and CVE-2008-4579. (Closes: #496410) Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378323: marked as done (linux-image-2.6.17-1-686: CONFIG_SMP=y keeps APM poweroff from working)
Your message dated Sat, 29 Nov 2008 00:12:46 +0100 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.17-1-686: CONFIG_SMP=y keeps APM poweroff from working has caused the Debian Bug report #378323, regarding linux-image-2.6.17-1-686: CONFIG_SMP=y keeps APM poweroff from working 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.) -- 378323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378323 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.17-1-686 Version: 2.6.17-3 Severity: normal As said above: CONFIG_SMP=y keeps APM poweroff from working. On a system without ACPI support this bug can really be a pain. squeezer:~# uname -a Linux squeezer 2.6.17-1-686 #1 SMP Thu Jul 13 14:30:26 UTC 2006 i686 GNU/Linux Regards, Joe. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=C, [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages linux-image-2.6.17-1-686 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-15 Yet Another mkInitRD Versions of packages linux-image-2.6.17-1-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information excluded ---End Message--- ---BeginMessage--- On Sun, May 20, 2007 at 11:09:56PM +0200, Johannes Tysiak wrote: Hi, sorry - I forgot about this bug request. The hardware I was experiencing this bug on died at the end of last year. Right now I can't say whether Willi's suggestion would have been a work-around. As nobody else seems to have this problem, I would suggest to close this bug. Doing so. Cheers, Moritz ---End Message---
Bug#352013: linux-image-2.6.15-1-686-smp: file lock not working over nfs
On Thu, Feb 09, 2006 at 09:23:48AM +0100, Erhard Schultchen wrote: Package: linux-image-2.6.15-1-686-smp Version: 2.6.15-4 Severity: normal Eclipse does not start on this machine running linux-image-2.6.15-1-686-smp. It complains about an I/O error while locking a certain file accessed over nfs. This works on my custom 2.6.14 and on previous versions of linux-image-2.6.15-1-686-smp (at least 2.6.15-1) Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
redhat-cluster_2.20080801-4+lenny1_i386.changes ACCEPTED
Accepted: cman_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/cman_2.20080801-4+lenny1_i386.deb gfs-tools_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/gfs-tools_2.20080801-4+lenny1_i386.deb gfs2-tools_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/gfs2-tools_2.20080801-4+lenny1_i386.deb gnbd-client_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/gnbd-client_2.20080801-4+lenny1_i386.deb gnbd-server_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/gnbd-server_2.20080801-4+lenny1_i386.deb libcman-dev_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/libcman-dev_2.20080801-4+lenny1_i386.deb libcman2_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/libcman2_2.20080801-4+lenny1_i386.deb libdlm-dev_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/libdlm-dev_2.20080801-4+lenny1_i386.deb libdlm2_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/libdlm2_2.20080801-4+lenny1_i386.deb redhat-cluster-source_2.20080801-4+lenny1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080801-4+lenny1_all.deb redhat-cluster-suite_2.20080801-4+lenny1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080801-4+lenny1_all.deb redhat-cluster_2.20080801-4+lenny1.diff.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080801-4+lenny1.diff.gz redhat-cluster_2.20080801-4+lenny1.dsc to pool/main/r/redhat-cluster/redhat-cluster_2.20080801-4+lenny1.dsc rgmanager_2.20080801-4+lenny1_i386.deb to pool/main/r/redhat-cluster/rgmanager_2.20080801-4+lenny1_i386.deb Override entries for your package: cman_2.20080801-4+lenny1_i386.deb - optional admin gfs-tools_2.20080801-4+lenny1_i386.deb - optional admin gfs2-tools_2.20080801-4+lenny1_i386.deb - optional admin gnbd-client_2.20080801-4+lenny1_i386.deb - optional admin gnbd-server_2.20080801-4+lenny1_i386.deb - optional admin libcman-dev_2.20080801-4+lenny1_i386.deb - optional libdevel libcman2_2.20080801-4+lenny1_i386.deb - optional libs libdlm-dev_2.20080801-4+lenny1_i386.deb - optional libdevel libdlm2_2.20080801-4+lenny1_i386.deb - optional libs redhat-cluster-source_2.20080801-4+lenny1_all.deb - optional admin redhat-cluster-suite_2.20080801-4+lenny1_all.deb - optional admin redhat-cluster_2.20080801-4+lenny1.dsc - source admin rgmanager_2.20080801-4+lenny1_i386.deb - optional admin Announcing to [EMAIL PROTECTED] Closing bugs: 496410 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496410: redhat-cluster tmpfile fixes
On Fri, Nov 28, 2008 at 11:53:45PM +0100, Stefan Fritsch wrote: please accept redhat-cluster 2.20080801-4+lenny1 which I have just uploaded to testing-proposed-updates: Where is the patch? Do I have to remind you about the NMU procedures? Bastian -- Deflector shields just came on, Captain. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378072: newer kernels don't find secondary IDE controller during boot
On Wed, Jul 12, 2006 at 10:29:16PM -0400, Brian White wrote: Package: linux-image-2.6.17-1-686 Version: 2.6.17-2 I cannot get my system to come up with the 2.6.17 kernel. It starts fine, but is unable to find drive hde,hdf,hdg, and hdh. These are all drives connected to a second IDE controller, a Promise PDC20268 (Ultra100 TX2). The 2.6.15 kernel also had this problem. 2.6.12 works fine. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496410: marked as done (The possibility of attack with the help of symlinks in some Debian packages)
Your message dated Fri, 28 Nov 2008 23:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#496410: fixed in redhat-cluster 2.20080801-4+lenny1 has caused the Debian Bug report #496410, regarding The possibility of attack with the help of symlinks in some Debian packages 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.) -- 496410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496410 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: cman Severity: grave Hi, maintainer! This message about the error concerns a few packages at once. I've tested all the packages (for Lenny) on my Debian mirror. All scripts of packages (marked as executable) were tested. In some packages I've discovered scripts with errors which may be used by a user for damaging important system files or user's files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlink with the same name in this directory in order to destroy or rewrite some system or user file. Symlink attack may also lead not only to the data desctruction but to denial of service as well. Even if you create files or directories with help of function 'RANDOM' or pid(), then your system is not protected. Attacker can create many symlinks in order to destroy your data or create 'denial of service' for your package scripts. Even if you make rm(dir) for files/directories, then your system is not protected. Attacker can permanently create symlinks. This list is created with the help of script. This list is sorted by hand. Howewer in some cases mistake is possible. Please, Be understanding to possible mistakes. :) I set Severity into grave for this bug. The table of discovered problems is below. Discussion of this bug you can see in debian-devel@: http://lists.debian.org/debian-devel/2008/08/msg00271.html Binary-package: r-base-core-ra (1.1.1-1) file: /usr/lib/Ra/lib/R/bin/javareconf Binary-package: rccp (0.9-2) file: /usr/lib/rccp/delqueueask Binary-package: mafft (6.240-1) file: /usr/bin/mafft-homologs Binary-package: openoffice.org-common (1:2.4.1-6) file: /usr/lib/openoffice/program/senddoc Binary-package: crossfire-maps (1.11.0-1) file: /usr/share/games/crossfire/maps/Info/combine.pl Binary-package: sgml2x (1.0.0-11.1) file: /usr/bin/rlatex Binary-package: liguidsoap (0.3.6-4) file: /var/lib/liguidsoap/liguidsoap.py Binary-package: citadel-server (7.37-1) file: /usr/lib/citadel-server/migrate_aliases.sh Binary-package: ampache (3.4.1-1) file: /usr/share/ampache/www/locale/base/gather-messages.sh Binary-package: xen-utils-3.2-1 (3.2.1-2) file: /usr/lib/xen-3.2-1/bin/qemu-dm.debug Binary-package: dtc-common (0.29.6-1) file: /usr/share/dtc/admin/accesslog.php file: /usr/share/dtc/admin/sa-wrapper Binary-package: honeyd-common (1.5c-3) file: /usr/share/honeyd/scripts/test.sh Binary-package: lustre-tests (1.6.5-1) file: /usr/lib/lustre/tests/runiozone Binary-package: linuxtrade (3.65-8+b4) file: /usr/share/linuxtrade/bin/linuxtrade.bwkvol file: /usr/share/linuxtrade/bin/linuxtrade.wn file: /usr/share/linuxtrade/bin/moneyam.helper Binary-package: freevo (1.8.1-0) file: /usr/bin/freevo.real Binary-package: fml (4.0.3.dfsg-2) file: /usr/share/fml/libexec/mead.pl Binary-package: rkhunter (1.3.2-3) file: /usr/bin/rkhunter Binary-package: openswan (1:2.4.12+dfsg-1.1) file: /usr/lib/ipsec/livetest Binary-package: linux-patch-openswan (1:2.4.12+dfsg-1.1) file: /usr/src/kernel-patches/all/openswan/packaging/utils/maysnap file: /usr/src/kernel-patches/all/openswan/packaging/utils/maytest Binary-package: aptoncd (0.1-1.1) file: /usr/share/aptoncd/xmlfile.py Binary-package: cdcontrol (1.90-1.1) file: /usr/lib/cdcontrol/writtercontrol Binary-package: newsgate (1.6-23) file: /usr/bin/mkmailpost Binary-package: gpsdrive-scripts (2.10~pre4-3) file: /usr/bin/geo-code Binary-package: impose+ (0.2-11) file: /usr/bin/impose Binary-package: mgt (2.31-5) file: /usr/games/mailgo Binary-package: audiolink (0.05-1) file: /usr/bin/audiolink Binary-package: ibackup (2.27-4.1) file: /usr/bin/ibackup Binary-package: emacspeak (26.0-3) file: /usr/share/emacs/site-lisp/emacspeak/etc/extract-table.pl Binary-package: bk2site (1:1.1.9-3.1) file: /usr/lib/cgi-bin/bk2site/redirect.pl Binary-package: datafreedom-perl (0.1.7-1) file: /usr/bin/dfxml-invoice Binary-package: emacs-jabber (0.7.91-1) file:
Please unblock linux-2.6/2.6.26-11, linux-modules-extra-2.6/2.6.26-5, redhat-cluster/2.20081102-1
Hi folks Please unblock linux-2.6/2.6.26-11. It introduces another stable update and fixes several other problems. Please unblock linux-modules-extra-2.6/2.6.26-5. It is a schedules rebuild to introduce new images and build against new modules sources. Please unblock redhat-cluster/2.20081102-1. It is necessary to have working modules on 2.6.26. This is source for l-m-e-2.6. Bastian -- Yes, it is written. Good shall always destroy evil. -- Sirah the Yang, The Omega Glory, stardate unknown signature.asc Description: Digital signature
Re: Handling of linux-modules-*-2.6 during freeze
On Sat, Oct 04, 2008 at 02:03:31PM +0200, Bastian Blank wrote: linux-modules-*-2.6 also produces a source-availability problem, they use source including binary packages from unstable to build binary packages. In unstable this is usualy no problem as we ship the source in at least one variant. For the packages in testing this can be a problem, escpecially during freeze. Current state: not in testing btrfs-source. unstable: btrfs (0.16-3) out of date drbd8-source. drbd8 (2:8.0.13-2 - 2:8.0.14-2) out of date redhat-cluster-source. redhat-cluster (2.20080801-4 - 2.20081102-1) Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438144: Info received (Bug#438144: linux-image-2.6.21-2-686: new kernel does not like my ATI Rage 128 card)
On Sun, Oct 14, 2007 at 10:01:20PM -0700, Itai Seggev wrote: I've now tried it with both the linux-image-2.6.23-rc5-2-686 package in experimental, as well as a self-made kernel compiled from linux-source-2.6.22 in lenny/sid. This self compiled kernel works fine, but the linux-image kernel doesn't work. So perhaps this is some kernel configuration problem? Does the problem still occur with the current kernel/X.org from Lenny? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448503: NFS client problem - writing with group-access fails
On Thu, Jul 03, 2008 at 02:29:02PM +0200, Ruediger Oberhage wrote: I assume that b) is the actually culprit part. Now, I haven't read the specs for nfs and thus can't really tell whether it is the AIX nfs-server, that should allow that two attributes changing call, or the Linux-Client, that shouldn't alter both attributes at once. It workes perfectly the way it used to be and that SUN-code-derived NFS's (IRIX, OPENSTEP, MacOS X) do. But, since Linux used to work that way, too, a few kernel-versions in the past, even when it is playing according to the book now, it would be nice to have an option, so that it works with that server, too, because for us, it is a nuissance at best and a catastrophe in the worst case. On the other hand, it could be a real error the way it is now, and then it should certainly be corrected. Should you need any more information, I'll be glad to provide it wherever I can. Could you try to reproduce this with 2.6.28-rc6 and report this upstream at http://bugzilla.kernel.org if the problem still persists? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299014: marked as done ([PATCH] Non-DMAmode for floppy on PowerPC, recent version)
Your message dated Sat, 29 Nov 2008 00:54:50 +0100
with message-id [EMAIL PROTECTED]
and subject line Re: [PATCH] Non-DMAmode for floppy on PowerPC, recent version
has caused the Debian Bug report #299014,
regarding [PATCH] Non-DMAmode for floppy on PowerPC, recent version
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.)
--
299014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299014
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: kernel-source-2.6.11
Version: 2.6.11-1
Tags: patch
This patch allows to use floppy drive in non-DMA mode on PegasosPPC
and AmigaOne machines (ISA DMA is not supported on these machines). To use it:
1. Do not build floppy driver as a module, link it statically.
Transferring parameters to it from insmod is still problematic, at least
it doesn't work properly on my system. May be i'll clean it up in
future.
2. Specify floppy=nodma in kernel's arguments. Also you'll need to
specify your drive type here using floppy=Drive number,Drive type,cmos.
For example, floppy=0,4,cmos specifies type 4 (1.44 mb 3.5)
for drive 0 on my system. Without specification drive type defaults to 3.5
2.88 mb.
This patch does not affect operation of the driver in DMA mode so it's
safe to use on any platform.
--
Best regards,
Pavel Fedin,
mailto:[EMAIL PROTECTED]
--- kernel-source-2.6.8/include/asm-ppc/floppy.h.orig 2004-08-14
09:36:45.0 +0400
+++ kernel-source-2.6.8/include/asm-ppc/floppy.h2005-03-11
00:16:13.0 +0300
@@ -14,25 +14,148 @@
#define fd_inb(port) inb_p(port)
#define fd_outb(value,port)outb_p(value,port)
-#define fd_enable_dma() enable_dma(FLOPPY_DMA)
-#define fd_disable_dma()disable_dma(FLOPPY_DMA)
-#define fd_request_dma()request_dma(FLOPPY_DMA,floppy)
-#define fd_free_dma() free_dma(FLOPPY_DMA)
-#define fd_clear_dma_ff() clear_dma_ff(FLOPPY_DMA)
-#define fd_set_dma_mode(mode) set_dma_mode(FLOPPY_DMA,mode)
-#define fd_set_dma_addr(addr) set_dma_addr(FLOPPY_DMA,(unsigned
int)virt_to_bus(addr))
-#define fd_set_dma_count(count) set_dma_count(FLOPPY_DMA,count)
+#define fd_disable_dma() fd_ops-_disable_dma(FLOPPY_DMA)
+#define fd_free_dma() fd_ops-_free_dma(FLOPPY_DMA)
+#define fd_get_dma_residue()fd_ops-_get_dma_residue(FLOPPY_DMA)
+#define fd_dma_setup(addr, size, mode, io) fd_ops-_dma_setup(addr, size,
mode, io)
#define fd_enable_irq() enable_irq(FLOPPY_IRQ)
#define fd_disable_irq()disable_irq(FLOPPY_IRQ)
-#define fd_cacheflush(addr,size) /* nothing */
-#define fd_request_irq()request_irq(FLOPPY_IRQ, floppy_interrupt, \
- SA_INTERRUPT|SA_SAMPLE_RANDOM, \
- floppy, NULL)
#define fd_free_irq() free_irq(FLOPPY_IRQ, NULL);
-__inline__ void virtual_dma_init(void)
+static int fd_request_dma(void);
+
+struct fd_dma_ops {
+ void (*_disable_dma)(unsigned int dmanr);
+ void (*_free_dma)(unsigned int dmanr);
+ int (*_get_dma_residue)(unsigned int dummy);
+ int (*_dma_setup)(char *addr, unsigned long size, int mode, int io);
+};
+
+static int virtual_dma_count;
+static int virtual_dma_residue;
+static char *virtual_dma_addr;
+static int virtual_dma_mode;
+static int doing_pdma;
+static struct fd_dma_ops *fd_ops;
+
+static irqreturn_t floppy_hardint(int irq, void *dev_id, struct pt_regs * regs)
+{
+ unsigned char st;
+
+ if (!doing_pdma)
+ return floppy_interrupt(irq, dev_id, regs);
+
+ {
+ int lcount;
+ char *lptr;
+
+ st = 1;
+ for (lcount=virtual_dma_count, lptr=virtual_dma_addr;
+ lcount; lcount--, lptr++) {
+ st=inb(virtual_dma_port+4) 0xa0 ;
+ if (st != 0xa0)
+ break;
+ if (virtual_dma_mode)
+ outb_p(*lptr, virtual_dma_port+5);
+ else
+ *lptr = inb_p(virtual_dma_port+5);
+ }
+ virtual_dma_count = lcount;
+ virtual_dma_addr = lptr;
+ st = inb(virtual_dma_port+4);
+ }
+
+ if (st == 0x20)
+ return IRQ_HANDLED;
+ if (!(st 0x20)) {
+ virtual_dma_residue += virtual_dma_count;
+ virtual_dma_count=0;
+ doing_pdma = 0;
+
Bug#497875: linux-image-2.6.26-1-686 (2.6.26-4): virtualbox-ose - Kernel booting fails.
Dear Moritz, This one fixed can closed. Thanks. On Sat, Nov 29, 2008 at 6:29 AM, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: On Fri, Sep 05, 2008 at 09:55:34AM +0800, Patrick Yuen wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: important Hello, I am running lenny in virtualbox-ose (1.6.2-dfsg-4), kernel 2.6.24 works fine. The new kernel fails with message [0.824031] BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1 Does this error still occur with current Lenny, which has both a more recent kernel and a more recent virtualbox? Cheers, Moritz -- Cheers. ~Pat.
Bug#496410: redhat-cluster tmpfile fixes
here is the patch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496410: redhat-cluster tmpfile fixes
here is the patch
ups. second trydiff -u redhat-cluster-2.20080801/debian/changelog
redhat-cluster-2.20080801/debian/changelog
--- redhat-cluster-2.20080801/debian/changelog
+++ redhat-cluster-2.20080801/debian/changelog
@@ -1,3 +1,11 @@
+redhat-cluster (2.20080801-4+lenny1) testing-proposed-updates; urgency=low
+
+ * Non-maintainer upload by the security team.
+ * Fix several tmpfile race conditions, among them CVE-2008-4192 and
+CVE-2008-4579. (Closes: #496410)
+
+ -- Stefan Fritsch [EMAIL PROTECTED] Fri, 28 Nov 2008 19:15:39 +0100
+
redhat-cluster (2.20080801-4) unstable; urgency=high
* Add dependency on python-pexpect and install missing fencing
diff -u redhat-cluster-2.20080801/debian/patches/00list
redhat-cluster-2.20080801/debian/patches/00list
--- redhat-cluster-2.20080801/debian/patches/00list
+++ redhat-cluster-2.20080801/debian/patches/00list
@@ -3,0 +4 @@
+04_tmpfile_fixes.dpatch
only in patch2:
unchanged:
--- redhat-cluster-2.20080801.orig/debian/rgmanager.dirs
+++ redhat-cluster-2.20080801/debian/rgmanager.dirs
@@ -0,0 +1 @@
+var/log/cluster
only in patch2:
unchanged:
--- redhat-cluster-2.20080801.orig/debian/cman.dirs
+++ redhat-cluster-2.20080801/debian/cman.dirs
@@ -0,0 +1 @@
+var/log/cluster
only in patch2:
unchanged:
--- redhat-cluster-2.20080801.orig/debian/patches/04_tmpfile_fixes.dpatch
+++ redhat-cluster-2.20080801/debian/patches/04_tmpfile_fixes.dpatch
@@ -0,0 +1,456 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: backport various tmpfile fixes from upstream git
+
[EMAIL PROTECTED]@
+diff --git a/ccs/ccs_tool/upgrade.c b/ccs/ccs_tool/upgrade.c
+index a8a2314..b7cecf0 100644
+--- a/ccs/ccs_tool/upgrade.c
b/ccs/ccs_tool/upgrade.c
+@@ -182,7 +182,7 @@ static void ccs_dh_in(ccs_dh_t *dh, char *buf){
+ static int upgrade_device_archive(char *location){
+ int error = 0;
+ int dev_fd=-1, tmp_fd=-1;
+- char tmp_file[64];
++ char tmp_file[128];
+ void *buffer = NULL;
+ char *buffer_p;
+ ccs_dh_t dev_header;
+@@ -220,9 +220,10 @@ static int upgrade_device_archive(char *location){
+ goto fail;
+ }
+
+- sprintf(tmp_file, /tmp/tmp_%d, getpid());
++ memset(tmp_file, 0, 128);
++ sprintf(tmp_file, /tmp/ccs_tool_tmp_XX);
+
+- tmp_fd = open(tmp_file, O_RDWR | O_CREAT |O_TRUNC, S_IRUSR|S_IWUSR);
++ tmp_fd = mkostemp(tmp_file, O_RDWR | O_CREAT |O_TRUNC);
+ if(tmp_fd 0){
+ fprintf(stderr, Unable to create temporary archive: %s\n,
strerror(errno));
+ error = -errno;
+diff --git a/fence/agents/apc_snmp/fence_apc_snmp.py
b/fence/agents/apc_snmp/fence_apc_snmp.py
+index b635193..dad1dc2 100644
+--- a/fence/agents/apc_snmp/fence_apc_snmp.py
b/fence/agents/apc_snmp/fence_apc_snmp.py
+@@ -216,7 +216,7 @@ def usage():
+ print -c community SNMP community (default 'private')
+ print -n num Outlet name/number to act on
+ print -o string Action: Reboot (default), On, Off and
Status
+-print -v Verbose mode - write to /tmp/apclog
++print -v Verbose mode - write to
/var/log/cluster/fence_apc_snmp.log
+ print -V Version
+
+ sys.exit(0)
+@@ -227,7 +227,7 @@ file_log = None
+ def set_logging(verbose):
+ global file_log
+ if verbose:
+- file_log = open('/tmp/apclog', 'a')
++ file_log = open('/var/log/cluster/fence_apc_snmp.log', 'a')
+ file_log.write('\n--- ')
+ file_log.write(datetime.datetime.today().ctime())
+ file_log.write(' ---\n')
+diff --git a/fence/agents/egenera/fence_egenera.pl
b/fence/agents/egenera/fence_egenera.pl
+index 6970a13..e852a45 100644
+--- a/fence/agents/egenera/fence_egenera.pl
b/fence/agents/egenera/fence_egenera.pl
+@@ -284,7 +284,7 @@ sub pserver_shutdown
+ {
+ my $rtrn=1;
+ local *egen_log;
+-open(egen_log,/tmp/eglog);
++ open(egen_log,/var/log/cluster/fence_egenera.log);
+ for (my $trys=0; $trys20; $trys++)
+ {
+ last if (pserver_status != 0);
+diff --git a/fence/agents/vmware/fence_vmware.pl
b/fence/agents/vmware/fence_vmware.pl
+index 9769d15..6f6f78b 100644
+--- a/fence/agents/vmware/fence_vmware.pl
b/fence/agents/vmware/fence_vmware.pl
+@@ -14,13 +14,13 @@ s/.*\///;
+ my $pname = $_;
+
+ # Change these if the text returned by your equipment is different.
+-# Test by running script with options -t -v and checking /tmp/vmlog
++# Test by running script with options -t -v and checking
/var/log/cluster/apclog
+
+ my $immediate = 'immediate'; # # Or 'delayed' - action string prefix on menu
+
+ my $max_open_tries = 3; # How many attempts to make.
+ my $open_wait = 5; # Seconds to wait between each attempt
+-my $debuglog = '/tmp/apclog';# Location of debugging log when in verbose mode
++my $debuglog = '/var/log/cluster/vmlog';# Location of
Bug#497875: marked as done (linux-image-2.6.26-1-686 (2.6.26-4): virtualbox-ose - Kernel booting fails.)
Your message dated Sat, 29 Nov 2008 01:13:24 +0100 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.26-1-686 (2.6.26-4): virtualbox-ose - Kernel booting fails. has caused the Debian Bug report #497875, regarding linux-image-2.6.26-1-686 (2.6.26-4): virtualbox-ose - Kernel booting fails. 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.) -- 497875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497875 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: important Hello, I am running lenny in virtualbox-ose (1.6.2-dfsg-4), kernel 2.6.24 works fine. The new kernel fails with message [0.824031] BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1BUG: unable to handel kernel 1 then loop to the bottom. -- Cheers. ~Pat. ---End Message--- ---BeginMessage--- On Sat, Nov 29, 2008 at 07:35:56AM +0800, Patrick Yuen wrote: Dear Moritz, This one fixed can closed. Thanks. Doing so. Cheers, Moritz ---End Message---
Bug#341961: marked as done (linux-image-2.6.12-1-386: Module sym53c8xx: phase change messages on Iomega ZIP drive)
Your message dated Sat, 29 Nov 2008 01:21:09 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#341961: Module sym53c8xx: phase change messages on Iomega ZIP drive has caused the Debian Bug report #341961, regarding linux-image-2.6.12-1-386: Module sym53c8xx: phase change messages on Iomega ZIP drive 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.) -- 341961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341961 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Subject: linux-image-2.6.12-1-386: Module sym53c8xx: phase change messages on Iomega ZIP drive Package: linux-image-2.6.12-1-386 Version: 2.6.12-10 Severity: normal As soon as during the boot procedure my Iomega SCSI ZIP drive is recognized I get the following message onto the console: sd 0:0:5:0 phase change 6-7 [EMAIL PROTECTED] resid=7. (the number [EMAIL PROTECTED] is different after each booting of the machine) This message is written about 5-10 times per second onto the console making working with it almost impossible. This was especially a problem during installation of the system. Inserting a disk into the ZIP drive improves the situation slightly: The amount of messages drops to about 1 per second - still too much. Despite of the messages, access to such a disk works correctly. Booting the machine with the ZIP drive powered off does not give the message. I located the above message in the linux kernel files: - /usr/src/linux-2.6-2.6.12/drivers/scsi/ncr53c8xx.c - /usr/src/linux-2.6-2.6.12/drivers/scsi/sym53c8xx_2/sym_hipd.c This bug seems to be closely related to #303088 Here is the relevant part of /var/log/messages: Dec 4 08:32:17 df8xq-l2 kernel: PCI: Found IRQ 9 for device :00:13.0 Dec 4 08:32:17 df8xq-l2 kernel: PCI: Sharing IRQ 9 with :00:11.2 Dec 4 08:32:17 df8xq-l2 kernel: sym0: 875 rev 0x4 at pci :00:13.0 irq 9 Dec 4 08:32:17 df8xq-l2 kernel: sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking Dec 4 08:32:17 df8xq-l2 kernel: sym0: open drain IRQ line driver, using on-chip SRAM Dec 4 08:32:17 df8xq-l2 kernel: sym0: using LOAD/STORE-based firmware. Dec 4 08:32:17 df8xq-l2 kernel: sym0: SCSI BUS has been reset. Dec 4 08:32:17 df8xq-l2 kernel: scsi0 : sym-2.2.0 Dec 4 08:32:17 df8xq-l2 kernel: Floppy drive(s): fd0 is 1.44M Dec 4 08:32:17 df8xq-l2 kernel: bt878: AUDIO driver version 0.0.0 loaded Dec 4 08:32:17 df8xq-l2 kernel: FDC 0 is a post-1991 82077 Dec 4 08:32:17 df8xq-l2 kernel: USB Universal Host Controller Interface driver v2.2 Dec 4 08:32:17 df8xq-l2 kernel: Vendor: TEAC Model: CD-R55S Rev: 1.0R Dec 4 08:32:17 df8xq-l2 kernel: Type: CD-ROM ANSI SCSI revision: 02 Dec 4 08:32:17 df8xq-l2 kernel: target0:0:1: Beginning Domain Validation Dec 4 08:32:17 df8xq-l2 kernel: target0:0:1: asynchronous. Dec 4 08:32:17 df8xq-l2 kernel: target0:0:1: Domain Validation skipping write tests Dec 4 08:32:17 df8xq-l2 kernel: target0:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15) Dec 4 08:32:17 df8xq-l2 kernel: target0:0:1: Ending Domain Validation Dec 4 08:32:17 df8xq-l2 kernel: Vendor: IOMEGAModel: ZIP 100 Rev: E.08 Dec 4 08:32:17 df8xq-l2 kernel: Type: Direct-Access ANSI SCSI revision: 02 Dec 4 08:32:17 df8xq-l2 kernel: target0:0:5: Beginning Domain Validation Dec 4 08:32:17 df8xq-l2 kernel: 0:0:5:0: phase change 6-7 [EMAIL PROTECTED] resid=7. Dec 4 08:32:17 df8xq-l2 last message repeated 3 times Dec 4 08:32:17 df8xq-l2 kernel: target0:0:5: Ending Domain Validation Dec 4 08:32:17 df8xq-l2 kernel: uhci_hcd :00:07.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller Dec 4 08:32:17 df8xq-l2 kernel: uhci_hcd :00:07.2: new USB bus registered, assigned bus number 4 Dec 4 08:32:17 df8xq-l2 kernel: uhci_hcd :00:07.2: irq 10, io base 0xe400 Dec 4 08:32:17 df8xq-l2 kernel: hub 4-0:1.0: USB hub found Dec 4 08:32:17 df8xq-l2 kernel: hub 4-0:1.0: 2 ports detected Dec 4 08:32:17 df8xq-l2 kernel: sr0: scsi-1 drive Dec 4 08:32:17 df8xq-l2 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0, type 5 Dec 4 08:32:17 df8xq-l2 kernel: Attached scsi generic sg1 at scsi0, channel 0, id 5, lun 0, type 0 Dec 4 08:32:17 df8xq-l2 kernel: sd 0:0:5:0: phase change 6-7 [EMAIL PROTECTED] resid=7. Dec 4 08:32:17 df8xq-l2 kernel: sd 0:0:5:0: phase change 6-7 [EMAIL PROTECTED] resid=7. Dec 4 08:32:17 df8xq-l2 kernel: sd 0:0:5:0: phase change 6-7 [EMAIL PROTECTED] resid=7. Dec 4 08:32:17 df8xq-l2 kernel: sd 0:0:5:0: phase change 6-7
Bug#290997: pcmcia-cs: cardmgr doesn't recognize new PCMCIA card
On Mon, Jan 17, 2005 at 05:53:05PM +0100, Giuseppe Sacco wrote: Package: pcmcia-cs Version: 3.2.5-9 Severity: normal I have a problem with PCMCIA on a Powerbook Titanium G4 15 I am using a Sarge machine, but I also recompiled the vanilla kernel 2.6.10 in order to gather more informations. When I insert my PCMCIA SCSI card nothing happens. If I issue 'cardctl insert' command, then I hear only one beep. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487103: Somewhat merged upstream
On Thu, Jul 31, 2008 at 11:48:26PM -0700, Matt Kraai wrote: Howdy, The patch has been merged upstream by Patrick McHardy, one of the netfilter maintainers, so I assume it'll be merged into the official tree eventually. This commit (c8942f1f0a7e2160ebf2e51ba89e50ee5895a1e7) was merged into 2.6.26. Can you confirm that this fixes your problem? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344791: Problem with pcmcia fixed disk
On Mon, Dec 26, 2005 at 12:26:22PM +0100, Alain Prignet wrote: Package: linux-image-2.6.14-2-686 Version: 2.6.14-6 When I insert a pcmcia fixed ide disk, I get the following messages in /var/log/syslog. I have also compiled a 2.6.14.3 and get the same problem. All is working well with 2.6.12 debian kernel, and 2.4.17 recompiled. The pcmcia system was tested with different combination of pcmcia-cs, pcmciautils, hotplug, udev giving the same phenomena. The pcmcia system is working for a wifi card. Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348739: kernel-image-2.6-686: [module cdc-acm] ELSA Microlink 56 K USB does not attach to any device under /dev/
On Wed, Jan 18, 2006 at 07:40:59PM +0100, Sebastian Niehaus wrote: Package: kernel-image-2.6-686 Severity: normal -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-15) ELSA Microlink 56 K USB Modem: when I plug in te modem, the logs say: , | Jan 18 19:26:51 crystalline usb.agent[22170]: cdc-acm: loaded successfully | Jan 18 19:26:51 crystalline kernel: drivers/usb/class/cdc-acm.c: Ignoring extra header | Jan 18 19:26:51 crystalline kernel: usbcore: registered new driver cdc_acm | Jan 18 19:26:51 crystalline kernel: drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver for USB modems and ISDN adapters ` Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367026: linux-image-2.6.15-1-486: HID sermouse driver fails to detect Logitech mouse on ttyS0
On Fri, May 12, 2006 at 05:35:45PM -0400, Daniel Dickinson wrote: Package: linux-image-2.6.15-1-486 Version: 2.6.15-8 Severity: normal Using the mousedev module doesn't work with sermouse, for my mouse (the mouse is not detected, as evidenced by udev not create a new /dev/input/mouse0 when modprobe sermouse is performed, and X loading, but with a frozen mouse pointer (because /dev/input/mice always exists when mousedev is in use, but there really isn't a detected mouse). My mouse is an old Logitech (which uses the Microsoft protocol, when using /dev/ttyS0 for X) PS/2 mouse with a PS/2 mouse to serial computer adapter (which works, since specifying /dev/ttyS0 and Microsoft mode results in a working mouse for X). This is probably an upstream issue, as I found one reference while Googling. Unfortunately there didn't seem to be any followups, only an indication that it didn't work. The URL of that message is: http://www.ussg.iu.edu/hypermail/linux/kernel/0312.2/0778.html Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406419: [powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150
On Thu, Jan 11, 2007 at 12:20:12AM +0100, Ulrich Teichert wrote: Package: kernel-image-2.6-powerpc Version: 2.6.18+5 during working on another bug, I tried to install the daily d-i build: cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso on an IBM RS/6000 43p 150. This is a CHRP system, so I used the CHRP-initrd image and tried to netboot it (serial console): ---server TFTP log- Jan 8 00:31:36 mosna dhcpd: BOOTREQUEST from 00:04:ac:97:14:87 via eth0 Jan 8 00:31:36 mosna dhcpd: BOOTREPLY for 192.168.22.58 to cholos (00:04:ac:97:14:87) via eth0 Jan 8 00:31:38 mosna in.tftpd[3649]: RRQ from 192.168.22.58 filename vmlinuz-chrp.initrd ---server TFTP log- As you can see, the image is loaded just fine. ---client boot log- 0 boot net:192.168.22.51,vmlinuz-chrp.initrd,192.168.22.58 LOAD: Waiting 60 seconds for Spanning Tree BOOTP R = 1 BOOTP S = 1 FILE: vmlinuz-chrp.initrd Load Addr=0x4000 Max Size=0xbfc000 FINAL Packet Count = 10753 Final File Size = 5505188 bytes. zImage starting: loaded at 0x0040 (sp: 0x00efffe0) Allocating 0x36f658 bytes for kernel ... OF version = 'IBM,TCP04195' Allocating 0x3bb2ca bytes for initrd ... initial ramdisk moving 0x137 - 0x574000 (0x3bb2ca bytes) initrd head: 0x1f8b0808 gunzipping (0x100 - 0x407000:0x573abe)...done 0x33e654 bytes OF stdout device is: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] command line: console=ttyS0,9600 console=tty0 memory layout at init: alloc_bottom : 0172c000 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 Looking for displays found display : /[EMAIL PROTECTED]/[EMAIL PROTECTED], opening ... done instantiating rtas at 0x1ffe5000 ... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x0172d000 - 0x0172dd6d Device tree struct 0x0172e000 - 0x01732000 Calling quiesce ... returning from prom_init Using CHRP machine description Total memory = 512MB; using 1024kB for hash table (at cff0) Linux version 2.6.18-3-powerpc (Debian 2.6.18-8) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 Sun Dec 10 17:59:01 CET 2006 Found initrd at 0xc137:0xc172b2ca chrp type = 5 PCI buses 0..1 controlled by pci at 8000 Built 1 zonelists. Total pages: 131072 Kernel command line: console=ttyS0,9600 console=tty0 OpenPIC at f9e8 OpenPIC irqs 0..15 in IDU mpic: Setting up MPIC MPIC version 1.0 at f9e8, max 4 CPUs mpic: ISU size: 16, shift: 4, mask: f mpic: Initializing for 16 sources i8259 legacy interrupt controller initialized PID hash table entries: 4096 (order: 12, 16384 bytes) ---client boot log- Booting just stops here, nothing is displayed on the front LED. As this box has a video card inside, I tried booting over the graphical console, too. There it stops dead after the line: coming back from prom_init Booting from CD isn't working at all, stops with a front LED error display of 185 - which can be anything. Most likely, this bug can't be resolved before etch, but I thought I should report it nonetheless, Does this error still occur with more recent kernel versions, e.g. with the Lenny d-i RC1? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502326: firmware update
I can also confirm (2) that given the provided firmware by Zhu Yi the issue is fixed on the same 2.6.27.7 kernel I built and talked about before (1) for Lenny, using the iwl4965 driver. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502326#41 2: http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703#c53 David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421775: marked as done (linux-2.6: Quirky console)
Your message dated Sat, 29 Nov 2008 01:51:21 +0100 with message-id [EMAIL PROTECTED] and subject line Re: linux-2.6: Still there has caused the Debian Bug report #421775, regarding linux-2.6: Quirky console 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.) -- 421775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421775 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Severity: normal When viewing a lot of text is output on the console (cat /var/log/syslog), the cursor ends up below the visible area, together with the last lines of text. The visible area will still be scrolled upward appropriately as more text is entered. Switching VT back and forth will correct the problem. I'm using fbcon on nvidiafb. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Tue, Nov 18, 2008 at 07:16:29PM +0100, Vincent Lönngren wrote: tis 2008-11-11 klockan 00:19 +0100 skrev Moritz Muehlenhoff: Does this error still occur with more recent kernel versions? Cheers, Moritz I don't know and I can't check, because I'm not using that computer anymore. Closing the bug then, since it's rather old anyway. Cheers, Moritz ---End Message---
Bug#421779: linux-source-2.6.18: Poweroff doesn't work on Sony VAIO S4M
On Tue, May 01, 2007 at 02:28:28PM +0200, Marcello Maggioni wrote: Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12 Severity: normal I've tried recompiling the kernel , playing with ACPI options (kernel configurations and acpi= parameters) , but POWEROFF doesn't work. When I do shutdown -h now the system starts powering off and then stops with the line : acpi_power_off called I've also tried the lastest mainline vanilla kernel 2.6.21.1 and I've got the same problem. I've also tried powering off by APM and what I've got is a black screen after shutdown -h now finish to umounting the filesystems , but the system remains on (Fan spinning and the screen is black , but the LCD backlight is still on). I will attach my dmesg in the next message . Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500065: marked as done (linux-image-2.6.26-1-amd64: Please add support for Attansic Technology Corp. L2 100 Mbit Ethernet Adapter)
Your message dated Sat, 29 Nov 2008 02:39:11 +0100 with message-id [EMAIL PROTECTED] and subject line Re: linux-image-2.6.26-1-amd64: Please add support for Attansic Technology Corp. L2 100 Mbit Ethernet Adapter has caused the Debian Bug report #500065, regarding linux-image-2.6.26-1-amd64: Please add support for Attansic Technology Corp. L2 100 Mbit Ethernet Adapter 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.) -- 500065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500065 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-5 Severity: wishlist Hi, my mother (Asus P5LD2-X) has an Attansic Technology Corp. L2 100 Mbit Ethernet Adapter onboard but I am not able to use it with current 2.6.26 kernel. I found a patch at: http://people.redhat.com/csnook/atl2/, and applied it to vanilla 2.6.26.2 (it applied cleany) and make my network card work ok. I am using the kernel with this patch applied since a month ago and with no problem at all. If I am not wrong, it would be merged into 2.6.28 [1] and [2]) Also, as http://people.redhat.com/csnook/atl2/ says, seems that fedora is shipping with support for this network card. Please consider applying it, as its going to be merged upstream and other distros are shipping with this patch. If you want me to test something or there's some other way I can help, please let me know. Thanks a lot, Rodrigo [1]: http://people.redhat.com/csnook/atl2/ [2]: http://marc.info/?t=12209413338r=1w=2 -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.2 (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.26-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.23 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-amd64 recommends no packages. Versions of packages linux-image-2.6.26-1-amd64 suggests: ii grub 0.97-47GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- On Thu, Nov 27, 2008 at 09:51:41PM -0200, Rodrigo Campos wrote: On Thu, Nov 27, 2008 at 4:59 PM, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: On Mon, Nov 24, 2008 at 09:10:01PM -0200, Rodrigo Campos wrote: On Sun, Nov 23, 2008 at 4:54 PM, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: On Wed, Sep 24, 2008 at 02:25:08PM -0300, Rodrigo Campos wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-5 Severity: wishlist Hi, my mother (Asus P5LD2-X) has an Attansic Technology Corp. L2 100 Mbit Ethernet Adapter onboard but I am not able to use it with current 2.6.26 kernel. I found a patch at: http://people.redhat.com/csnook/atl2/, and applied it to vanilla 2.6.26.2 (it applied cleany) and make my network card work ok. I am using the kernel with this patch applied since a month ago and with no problem at all. For Lenny you can use the modules built by linux-modules-extra-2.6: http://packages.qa.debian.org/l/linux-modules-extra-2.6.html Sorry, I saw this after reporting :S Just curious, is it possible to use them with lenny netinstall ? I guess you could integrate the source package as outlined in the docs below, but it's probably easier to fetch them from a USB stick or floppy: http://wiki.debian.org/DebianInstaller/NetInstWithThirdPartyNetworkDriver Cool, thanks a lot! I think you can close this bug too =) Thanks again :) Doing so. Cheers, Moritz ---End Message---
Bug#421896: linux-image-2.6.18-4-686: cpufreq-info reports wrong frequency for 2nd core
On Wed, May 02, 2007 at 02:24:29PM +0200, Christian Pernegger wrote: Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12 Severity: normal Modules: speedstep-centrino, cpufreq-ondemand The frequency cpufreq-info reports conflicting info for the frequency of the second core: -f switch (normal user): always shows max frequency -w switch (root only): shows frequency matching the first core For the first core the frequencies match regardless of the query method. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423084: maxmem parameter apparently ignored
On Wed, May 09, 2007 at 12:45:43PM -0400, Tom Allen wrote: Package: xen-linux-system-2.6.20-1-xen-amd64 Version: 2.6.20-3 The maxmem parameter in Xen config files does not work, that is, regardless of the use of that setting, domU can never be ballooned to a value greater than the value set in the memory field. Does this error still occur with more recent kernel/Xen versions, such as the ones from Lenny? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423248: linux-image-2.6.18-4-486: [r8169] drops received TCP packets when using jumbo frames
On Thu, May 10, 2007 at 10:37:01PM +0200, Josselin Mouette wrote: Package: linux-2.6 Version: 2.6.18.dfsg.1-12, 2.6.18.dfsg.1-12etch1 When upgrading to the etch version of the kernel, I noticed a complete NFS lockup as soon as a client tries to write something. I tracked this down to the TCP layer; I'm using jumbo frames (tried with MTU ranging from 2000 to 7200) and all *received* TCP packets exceeding 1500 bytes are simply dropped. They don't even appear in tcpdump. This does not affect UDP nor ICMP packets, and this does not affect sent TCP packets. It is a regression from 2.6.18.dfsg.1-8, and I think it is related to the r8169 changes introduced in -9, as the network controller is a D-Link DGE-528T using this driver. Does this error still occur with more recent kernel versions? If that machine still runs Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421779: marked as done (linux-source-2.6.18: Poweroff doesn't work on Sony VAIO S4M)
Your message dated Sat, 29 Nov 2008 03:32:30 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#421779: linux-source-2.6.18: Poweroff doesn't work on Sony VAIO S4M has caused the Debian Bug report #421779, regarding linux-source-2.6.18: Poweroff doesn't work on Sony VAIO S4M 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.) -- 421779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421779 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12 Severity: normal I've tried recompiling the kernel , playing with ACPI options (kernel configurations and acpi= parameters) , but POWEROFF doesn't work. When I do shutdown -h now the system starts powering off and then stops with the line : acpi_power_off called I've also tried the lastest mainline vanilla kernel 2.6.21.1 and I've got the same problem. I've also tried powering off by APM and what I've got is a black screen after shutdown -h now finish to umounting the filesystems , but the system remains on (Fan spinning and the screen is black , but the LCD backlight is still on). I will attach my dmesg in the next message . -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Versions of packages linux-source-2.6.18 depends on: ii binutils 2.17-3 The GNU assembler, linker and bina ii bzip2 1.0.3-6high-quality block-sorting file co Versions of packages linux-source-2.6.18 recommends: ii gcc 4:4.1.1-15 The GNU C compiler ii libc6-dev [libc-dev]2.3.6.ds1-13 GNU C Library: Development Librari ii make3.81-2 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.26-1 On Sat, Nov 29, 2008 at 03:28:07AM +0100, Michele Cascella wrote: Hi, On Sat, Nov 29, 2008 at 2:23 AM, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: On Tue, May 01, 2007 at 02:28:28PM +0200, Marcello Maggioni wrote: Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12 Severity: normal I've tried recompiling the kernel , playing with ACPI options (kernel configurations and acpi= parameters) , but POWEROFF doesn't work. When I do shutdown -h now the system starts powering off and then stops with the line : acpi_power_off called I've also tried the lastest mainline vanilla kernel 2.6.21.1 and I've got the same problem. I've also tried powering off by APM and what I've got is a black screen after shutdown -h now finish to umounting the filesystems , but the system remains on (Fan spinning and the screen is black , but the LCD backlight is still on). I will attach my dmesg in the next message . Does this error still occur with more recent kernel versions? problems is fixed in 2.6.26 (but this kernel has other issues with the sony S5 hw) Ok, please file separate bugs for these issues if necessary. I'm closing this bug. If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html I'm running testing now. I think the kernel from etch-and-a-half is not compatible with my HAL. I'll see if I can try it. If you're running testing by now, running the tests with 2.6.24 isn't really necessary. This is mostly a suggestion for people running Etch on their systems. Cheers, Moritz ---End Message---
Bug#421779: linux-source-2.6.18: Poweroff doesn't work on Sony VAIO S4M
Hi, On Sat, Nov 29, 2008 at 2:23 AM, Moritz Muehlenhoff [EMAIL PROTECTED] wrote: On Tue, May 01, 2007 at 02:28:28PM +0200, Marcello Maggioni wrote: Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12 Severity: normal I've tried recompiling the kernel , playing with ACPI options (kernel configurations and acpi= parameters) , but POWEROFF doesn't work. When I do shutdown -h now the system starts powering off and then stops with the line : acpi_power_off called I've also tried the lastest mainline vanilla kernel 2.6.21.1 and I've got the same problem. I've also tried powering off by APM and what I've got is a black screen after shutdown -h now finish to umounting the filesystems , but the system remains on (Fan spinning and the screen is black , but the LCD backlight is still on). I will attach my dmesg in the next message . Does this error still occur with more recent kernel versions? problems is fixed in 2.6.26 (but this kernel has other issues with the sony S5 hw) If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html I'm running testing now. I think the kernel from etch-and-a-half is not compatible with my HAL. I'll see if I can try it. Regards, Emme Cheers, Moritz -- To unsubscribe, send mail to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487103: Somewhat merged upstream
On Sat, Nov 29, 2008 at 01:06:46AM +0100, Moritz Muehlenhoff wrote: On Thu, Jul 31, 2008 at 11:48:26PM -0700, Matt Kraai wrote: Howdy, The patch has been merged upstream by Patrick McHardy, one of the netfilter maintainers, so I assume it'll be merged into the official tree eventually. This commit (c8942f1f0a7e2160ebf2e51ba89e50ee5895a1e7) was merged into 2.6.26. Can you confirm that this fixes your problem? I don't think it does. #487103 is about netfilter.h not including in.h, whereas this patch fixes the problem of it not including types.h. -- Matt http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#507220: linux-source-2.6.24: Kernel panic when accessing Adaptec 1542CF SCSI controller (aha1542 driver)
Package: linux-source-2.6.24 Version: 2.6.24-6~etchnhalf.6 Severity: critical Justification: breaks the whole system I've moved an Adaptec 1542CF with a SCSI chain of: scanner, tape drive and CD writer into a P3. This hardware worked just fine in a pentium 133 years ago under 2.4 kernels. On this newer machine any access to the controller or any scsi device causes a kernel panic. Both on kernel 2.6.18 and 2.6.24 (the latest kernel available for Etch via aptitude). Both kernels were locally compiled, via make-kpkg. What works: the BIOS recognizes the controller and the connected devices. The Adaptec SCSI utility can run DMA tests with no problem. Manually loading the aha1542 driver with this command: modprobe -v aha1542 aha1542=0x134,5,10 causes no errors and identifies the connected devices. Since this is an old ISA device, it had to be manually configured for I/O address of 0x134, dma 5 and irq 10. In the bios, dma 5 and irq 10 were allocated to legacy devices. Strangely, even with the options in the /etc/modules.conf file and an explicit mention of aha1542 in /etc/modules, the driver is not loaded on boot. Furthermore, any access to the controller causes an immediate panic and crash. For instance, running lshw after the driver is loaded causes this: (kernel 2.6.18) Bad segment list supplied to aha1542.c (1,0) 0: c009 255 cptr c0366e00: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Kernel panic - not syncing: Fod fight! or (kernel 2.6.24) Bad segment list supplied to aha1542.c (1,0) 0: c0c2 255 cptr c0c1be00: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0 Kernel panic - not syncing: Fod fight! Any hints? Looks like a genuine bug to me. What could be causing a bad segment list to be supplied to the scsi driver? If I can supply more information, just ask and I'll perform the tests required. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.241 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-source-2.6.24 depends on: ii binutils 2.17-3 The GNU assembler, linker and bina ii bzip2 1.0.3-6high-quality block-sorting file co Versions of packages linux-source-2.6.24 recommends: ii gcc4:4.1.1-15The GNU C compiler ii libc6-dev [libc-dev] 2.3.6.ds1-13etch7 GNU C Library: Development Librari ii make 3.81-2The GNU version of the make util -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#507224: linux-image-2.6.26-1-amd64: oops in autofs4
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-10 Severity: normal I got an oops when autofs4 tried to mount a directory that it had mounted successfully many times previously. It may be the same race condition reported here: http://lkml.org/lkml/2008/6/3/76 , although at least one of those patches presumably made it into this debian kernel. My syslog log is here: PGD 6577c067 PUD b9ca0067 PMD 0 CPU 0 Modules linked in: mos7720 usbserial nfs lockd nfs_acl sunrpc nvidia(P) ppdev lp autofs4 video output ac battery acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_stats freq_table cpufreq_conservative ipv6 fuse loop parport_pc parport serio_raw psmouse snd_intel8x0 i2c_i801 i2c_core pcspkr snd_ac97_codec ac97_bus snd_pcm snd_seq snd_timer snd_seq_device snd iTCO_wdt button soundcore snd_page_alloc rng_core dcdbas evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sd_mod ide_cd_mod cdrom usbhid hid ff_memless ata_generic ata_piix libata scsi_mod dock piix floppy ide_pci_generic ide_core ehci_hcd uhci_hcd tg3 thermal processor fan thermal_sys Pid: 28263, comm: mount.nfs Tainted: P 2.6.26-1-amd64 #1 RIP: 0010:[802af516] [802af516] graft_tree+0x2e/0xf8 RSP: 0018:81001c38be08 EFLAGS: 00010246 RAX: 8100733732f0 RBX: 81001c38be68 RCX: RDX: 8100bf63c380 RSI: 81001c38be68 RDI: 810021ce7980 RBP: ffec R08: 0292 R09: 8100af37e3a8 R10: 83712fac R11: R12: 810021ce7980 R13: R14: 0003 R15: 8100bc316000 FS: 7f697b6fd6e0() GS:8053b000() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 00b2 CR3: 22fba000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process mount.nfs (pid: 28263, threadinfo 81001c38a000, task 8100253054b0) Stack: 810021ce7980 81001c38be68 802af7de 0003 0006 81001c38be68 802b16ec 81008cfe2000 810004e46000 Call Trace: [802af7de] ? do_add_mount+0xa6/0x124 [802b16ec] ? do_mount+0x1bd/0x1e7 [802af12f] ? copy_mount_options+0xc9/0x126 [802b17a0] ? sys_mount+0x8a/0xce [8020be9a] ? system_call_after_swapgs+0x8a/0x8f RSP 81001c38be08 ---[ end trace e510ca244b9cab4c ]--- -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-10) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Nov 8 18:25:23 UTC 2008 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.26-1-amd64 root=/dev/mapper/debian-root ro quiet ** Tainted: P (1) ** Kernel log: [7.061142] sd 0:0:0:0: [sda] 31250 512-byte hardware sectors (16 MB) [7.061142] sd 0:0:0:0: [sda] Write Protect is off [7.061142] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [7.061142] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [7.061142] sda: sda1 sda2 sda3 sda4 sda5 [7.100758] sd 0:0:0:0: [sda] Attached SCSI disk [7.870621] hiddev96hidraw2: USB HID v1.10 Device [American Power Conversion Back-UPS CS 500 FW:808.q8.I USB FW:q8] on usb-:00:1d.2-2 [7.870621] usbcore: registered new interface driver usbhid [7.870621] usbhid: v2.6:USB HID core driver [8.006623] device-mapper: uevent: version 1.0.3 [8.006623] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] [8.122619] PM: Starting manual resume from disk [8.224390] kjournald starting. Commit interval 5 seconds [8.224390] EXT3-fs: dm-0: orphan cleanup on readonly fs [8.224969] ext3_orphan_cleanup: deleting unreferenced inode 316071 [8.236969] ext3_orphan_cleanup: deleting unreferenced inode 98790 [8.236969] ext3_orphan_cleanup: deleting unreferenced inode 73558 [8.236969] ext3_orphan_cleanup: deleting unreferenced inode 69412 [8.313632] ext3_orphan_cleanup: deleting unreferenced inode 68226 [8.328969] ext3_orphan_cleanup: deleting unreferenced inode 737333 [8.328969] ext3_orphan_cleanup: deleting unreferenced inode 737296 [8.328969] ext3_orphan_cleanup: deleting unreferenced inode 65567 [8.328969] ext3_orphan_cleanup: deleting unreferenced inode 69323 [8.349171] ext3_orphan_cleanup: deleting unreferenced inode 69265 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738569 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738567 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738566 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738564 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738563 [8.364240] ext3_orphan_cleanup: deleting unreferenced inode 738562 [8.364241]
Bug#484753: linux-image-2.6.24-1-amd64: Fails to boot. Unable to mount root fs
On Mon, Nov 24, 2008 at 11:00:38PM +0100, Moritz Muehlenhoff wrote: On Sun, Jun 29, 2008 at 04:29:38PM +0200, maximilian attems wrote: 2.6.25 from unstable should just install fine, please report the error message you are seeing on boot. please follow those instructions for debug - http://wiki.debian.org/InitramfsDebug Does this error still occur with more recent kernel versions? Seems I forgot to follow up on this report. No, the problem is no longer occuring on newer kernels. Currently, the machine is using 2.6.26-8 and is behaving fine. -- --John GruenenfelderSystems Manager, MKS Imaging Technology, LLC. Try Weasel Reader for PalmOS -- http://weaselreader.org This is the most fun I've had without being drenched in the blood of my enemies! --Sam of Sam Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
