Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
On Tue, 2010-03-23 at 19:42 -0700, William Pitcock wrote: Package: linux-image-2.6.32-4-xen-amd64 Version: 2.6.32-10 Severity: grave Justification: renders package unusable Hello, The new 2.6.32 kernel packages fail to boot, resulting in a 100% CPU busy loop and blank screen at startup, when Xen relinquishes the VGA console. Standard Xen troubleshooting measures, like pci=nomsi and clocksource=jiffies, fail to affect the startup process. As this is a production machine, unfortunately I cannot try to reproduce this right now. IIRC these kernels require a newer hypervisor than is in stable at the moment, at a minimum you need 3.4.3, RC's are available in testing. Ian. -- Ian Campbell Pascal Users: To show respect for the 313th anniversary (tomorrow) of the death of Blaise Pascal, your programs will be run at half speed. signature.asc Description: This is a digitally signed message part
Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686
Hi, yesterday i mad an aptitude full-upgrade because i saw the new kernel image 2.6.32-3-686, which may correct my problem. But now i have really serious problem. The Ethernet is still not working with this kernel and Knoppix too!!! So my rtl8169 is broken and i cannot make that workaround with Knoppix. I had no time to investigate this more. But maybe it's a firmware problem, because if i made aptitude full-upgrade i saw this: update-initramfs: Generating /boot/initrd.img-2.6.32-3-686 W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169 Running update-grub. I tried also Adrien Clerc tip, without success. Hopefully my onboard network cards have no hardware damage. Any Suggestion? Thanks! Spitzauer -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324072120.62...@gmx.net
Processed: severity of 575183 is important
Processing commands for cont...@bugs.debian.org: severity 575183 important Bug #575183 [linux-image-2.6.32-4-xen-amd64] fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor Ignoring request to change severity of Bug 575183 to the same value. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126941858730078.transcr...@bugs.debian.org
Bug#575207: linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card
Package: linux-2.6 Version: 2.6.33-1~experimental.4 Severity: normal Plugging a TT-budget S2-1600 DVb pci card into my system causes a kernel Oops while loading the budget.ko module. The system continues to boot but the card is unusable. With latest kernel 2.6.32 package the system stops at boot time with a kernel panic while loading budget.ko. -- Package-specific info: ** Version: Linux version 2.6.33-2-686 (Debian 2.6.33-1~experimental.4) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Mar 18 07:30:30 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.33-2-686 root=/dev/mapper/system-root ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [2.472362] sd 1:0:0:0: Attached scsi generic sg2 type 0 [2.472663] sd 1:0:1:0: Attached scsi generic sg3 type 0 [2.519311] usbcore: registered new interface driver hiddev [2.535187] input: CHICONY Compaq USB Keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input2 [2.535442] generic-usb 0003:049F:0051.0001: input,hidraw0: USB HID v1.10 Keyboard [CHICONY Compaq USB Keyboard] on usb-:00:1d.0-1/input0 [2.567625] input: CHICONY Compaq USB Keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input3 [2.568403] generic-usb 0003:049F:0051.0002: input,hiddev0,hidraw1: USB HID v1.10 Device [CHICONY Compaq USB Keyboard] on usb-:00:1d.0-1/input1 [2.568734] usbcore: registered new interface driver usbhid [2.568740] usbhid: USB HID core driver [2.897873] md: raid1 personality registered for level 1 [2.973195] md: md0 stopped. [2.979797] md: bindsdc [2.981272] md: bindsdb [2.988393] raid1: raid set md0 active with 2 out of 2 mirrors [2.988445] md0: detected capacity change from 0 to 160041795584 [2.992616] md0: [3.025325] device-mapper: uevent: version 1.0.3 [3.026488] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-de...@redhat.com [3.043118] unknown partition table [3.459304] PM: Starting manual resume from disk [3.459313] PM: Resume from partition 253:1 [3.459317] PM: Checking hibernation image. [3.474166] PM: Error -22 checking image file [3.474172] PM: Resume from disk failed. [3.487075] JFS: nTxBlock = 3958, nTxLock = 31666 [5.586654] udev: starting version 151 [6.735101] i801_smbus :00:1f.3: PCI INT B - GSI 17 (level, low) - IRQ 17 [6.967739] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [7.150907] intel_rng: Firmware space is locked read-only. If you can't or [7.150912] intel_rng: don't want to disable this in firmware setup, and if [7.150915] intel_rng: you are certain that your system has a functional [7.150917] intel_rng: RNG, try using the 'no_fwh_detect' option. [7.200137] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [7.496390] parport_pc 00:07: reported by Plug and Play ACPI [7.496453] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [8.163922] input: PC Speaker as /devices/platform/pcspkr/input/input4 [8.172821] saa7146: register extension 'budget dvb'. [8.172883] budget dvb :05:04.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.172949] IRQ 16/: IRQF_DISABLED is not guaranteed on shared IRQs [8.172978] saa7146: found saa7146 @ mem e0916000 (revision 1, irq 16) (0x13c2,0x101c). [8.172992] saa7146 (0): dma buffer size 192512 [8.172997] DVB: registering new adapter (TT-Budget S2-1600 PCI) [8.209018] adapter has MAC addr = 00:d0:5c:cc:a7:29 [8.328665] Intel ICH :00:1f.5: PCI INT B - GSI 17 (level, low) - IRQ 17 [8.328753] Intel ICH :00:1f.5: setting latency timer to 64 [8.562047] DVB: Unable to find symbol stv090x_attach() [8.562117] BUG: unable to handle kernel NULL pointer dereference at 00ac [8.562239] IP: [e08b04a3] dvb_frontend_detach+0x4/0x67 [dvb_core] [8.562338] *pde = [8.562417] Oops: [#1] SMP [8.562532] last sysfs file: /sys/devices/virtual/net/lo/operstate [8.562581] Modules linked in: snd_intel8x0(+) snd_ac97_codec ac97_bus budget(+) snd_pcsp budget_core saa7146 ttpci_eeprom dvb_core snd_pcm snd_timer snd parport_pc soundcore parport snd_page_alloc shpchp tpm_tis tpm tpm_bios rng_core pci_hotplug i2c_i801 serio_raw psmouse i2c_core processor evdev jfs dm_mod raid1 md_mod usbhid hid sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix uhci_hcd e100 libata intel_agp mii floppy ehci_hcd scsi_mod usbcore agpgart nls_base button thermal fan thermal_sys [last unloaded: scsi_wait_scan] [8.564753] [8.564798] Pid: 537, comm: modprobe Not tainted 2.6.33-2-686 #1 07E8h/Evo D310 [8.564860] EIP: 0060:[e08b04a3] EFLAGS: 00010246 CPU: 0 [8.564921] EIP is at dvb_frontend_detach+0x4/0x67 [dvb_core] [8.564979] EAX: EBX: ECX: d75c9e88 EDX: e0904b79 [8.565038] ESI: EDI: e0904b63 EBP: ESP: d75c9e7c [8.565096] DS: 007b ES: 007b
Re: Xen dom0 2.6.32 stable branch
On Thu, Mar 18, 2010 at 01:52:34AM +0100, joy wrote: On Wed, Feb 24, 2010 at 01:05:53PM +0100, joy wrote: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/stable It's great to see the new packages :) I didn't want to rain on the parade by instantly filing bug reports, but I must point out a bit of a problem with the .32 kernel that may have something to do with (the lack of) the NX bit: http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00243.html http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00658.html I'm getting ready to start bisecting. Sadly that didn't help, but regardless, that problem was fixed yesterday with http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=de67ec8b23629776f786d62c3109552ea7f8cc27 Please update the package with the up-to-date xen/stable. Want a critical bug report as a reminder? :) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324092424.ga16...@orion.carnet.hr
Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
Ian Campbell wrote: IIRC these kernels require a newer hypervisor than is in stable at the moment, at a minimum you need 3.4.3, RC's are available in testing. I'd just like to confirm this, I distinctly recall seeing the mention of the exact Mercurial changeset on the xen-devel list for a new hypercall. Russell also mentioned it implicitly at http://etbe.coker.com.au/2010/03/21/xen-debian-squeeze/ William, did you try the hypervisor upgrade, does it work then? The new paravirt_ops Xen dom0 kernel packages should probably simply have a: Conflicts: xen-hypervisor-3.4-$ARCH ( 3.4.3~rc3), xen-hypervisor-3.2-$ARCH, xen-hypervisor-3.0-$ARCH -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324094420.ga19...@orion.carnet.hr
Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
On Wed, Mar 24, 2010 at 10:44:20AM +0100, Josip Rodin wrote: Ian Campbell wrote: IIRC these kernels require a newer hypervisor than is in stable at the moment, at a minimum you need 3.4.3, RC's are available in testing. William, did you try the hypervisor upgrade, does it work then? Also this kernel will only work on SMP machines. The new paravirt_ops Xen dom0 kernel packages should probably simply have a: Conflicts: xen-hypervisor-3.4-$ARCH ( 3.4.3~rc3), xen-hypervisor-3.2-$ARCH, xen-hypervisor-3.0-$ARCH No. Kernels are co-installable. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324100944.ga6...@wavehammer.waldi.eu.org
Processed (with 1 errors): Re: Bug#575207: linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card
Processing commands for cont...@bugs.debian.org: clone 575207 -1 Bug#575207: linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card Bug 575207 cloned as bug 575223. retitle -1 Unknown command or malformed arguments to command. severity -1 wishlist Bug #575223 [linux-2.6] linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card Severity set to 'wishlist' from 'normal' found -1 2.6.32-10 Bug #575223 [linux-2.6] linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card There is no source info for the package 'linux-2.6' at version '2.6.32-10' with architecture '' Unable to make a source version for version '2.6.32-10' Bug Marked as found in versions 2.6.32-10. tags 575207 + patch Bug #575207 [linux-2.6] linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126942822010730.transcr...@bugs.debian.org
Bug#575207: linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card
clone 575207 -1 retitle -1 severity -1 wishlist found -1 2.6.32-10 tags 575207 + patch thanks Fladischer Michael fladischermich...@fladi.at writes: [8.172997] DVB: registering new adapter (TT-Budget S2-1600 PCI) [8.209018] adapter has MAC addr = 00:d0:5c:cc:a7:29 [8.328665] Intel ICH :00:1f.5: PCI INT B - GSI 17 (level, low) - IRQ 17 [8.328753] Intel ICH :00:1f.5: setting latency timer to 64 [8.562047] DVB: Unable to find symbol stv090x_attach() There are actually two bugs here. This is one of them, and local to the Debian kernel: I assume it is built without 'CONFIG_DVB_STV090x=m', like the 2.6.32 kernels seem to be? I'm cloning that as a wishlist bug. [8.562117] BUG: unable to handle kernel NULL pointer dereference at 00ac [8.562239] IP: [e08b04a3] dvb_frontend_detach+0x4/0x67 [dvb_core] This is the second and far worse bug. I'll followup with a patch for upstream and stable. Bjørn pgpo3VHQFTzud.pgp Description: PGP signature
Bug#575207: [PATCH] V4L/DVB: budget: Oops: BUG: unable to handle kernel NULL pointer dereference
Never call dvb_frontend_detach if we failed to attach a frontend. This fixes
the following oops, which will be triggered by a missing stv090x module:
[8.172997] DVB: registering new adapter (TT-Budget S2-1600 PCI)
[8.209018] adapter has MAC addr = 00:d0:5c:cc:a7:29
[8.328665] Intel ICH :00:1f.5: PCI INT B - GSI 17 (level, low) - IRQ
17
[8.328753] Intel ICH :00:1f.5: setting latency timer to 64
[8.562047] DVB: Unable to find symbol stv090x_attach()
[8.562117] BUG: unable to handle kernel NULL pointer dereference at 00ac
[8.562239] IP: [e08b04a3] dvb_frontend_detach+0x4/0x67 [dvb_core]
Ref http://bugs.debian.org/575207
Signed-off-by: Bjørn Mork bj...@mork.no
Cc: sta...@kernel.org
Cc: 575...@bugs.debian.org
---
This patch should apply cleanly to 2.6.32, 2.6.33, 2.6.34-rc2 and with an
offset to git://linuxtv.org/v4l-dvb.git
Please apply to all of them
drivers/media/dvb/ttpci/budget.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/drivers/media/dvb/ttpci/budget.c b/drivers/media/dvb/ttpci/budget.c
index e48380c..95a463c 100644
--- a/drivers/media/dvb/ttpci/budget.c
+++ b/drivers/media/dvb/ttpci/budget.c
@@ -643,9 +643,6 @@ static void frontend_init(struct budget *budget)
budget-i2c_adap,
tt1600_isl6423_config);
- } else {
- dvb_frontend_detach(budget-dvb_frontend);
- budget-dvb_frontend = NULL;
}
}
break;
--
1.5.6.5
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1269428277-6709-1-git-send-email-bj...@mork.no
Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
On Wed, Mar 24, 2010 at 11:09:45AM +0100, Bastian Blank wrote: IIRC these kernels require a newer hypervisor than is in stable at the moment, at a minimum you need 3.4.3, RC's are available in testing. The new paravirt_ops Xen dom0 kernel packages should probably simply have a: Conflicts: xen-hypervisor-3.4-$ARCH ( 3.4.3~rc3), xen-hypervisor-3.2-$ARCH, xen-hypervisor-3.0-$ARCH No. Kernels are co-installable. Oh, crap, I forgot, yes. Maybe postinst messages then? Since the alternative is usually an instant reboot loop, which will inevitably result in people complaining. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324114720.ga17...@orion.carnet.hr
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
On Wed, Mar 24, 2010 at 12:40:36 +0100, Mathieu Roy wrote: Regarding X, only xserver-xorg-core, xserver-xorg, xserver-xorg-video-radeon was recently upgraded. The latest xserver-xorg-video-radeon package enables kernel mode setting. This is incompatible with the radeonhd X driver. You should use the radeon driver instead. Cheers, Julien signature.asc Description: Digital signature
Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
On Wed, 2010-03-24 at 12:47 +0100, Josip Rodin wrote: On Wed, Mar 24, 2010 at 11:09:45AM +0100, Bastian Blank wrote: IIRC these kernels require a newer hypervisor than is in stable at the moment, at a minimum you need 3.4.3, RC's are available in testing. The new paravirt_ops Xen dom0 kernel packages should probably simply have a: Conflicts: xen-hypervisor-3.4-$ARCH ( 3.4.3~rc3), xen-hypervisor-3.2-$ARCH, xen-hypervisor-3.0-$ARCH No. Kernels are co-installable. Oh, crap, I forgot, yes. Maybe postinst messages then? Since the alternative is usually an instant reboot loop, which will inevitably result in people complaining. The kernel should probably catch the ENOSYS from the new PHYSDEVOP_setup_gsi hypercall (which is what the hypervisor update is required for) and panic with a more useful/specific error message. I'm not sure if that would prevent a reboot loop though so perhaps that wouldn't help much. Ian. -- Ian Campbell Current Noise: Coffins - Deadly Sinners The nice thing about standards is that there are so many of them to choose from. -- Andrew S. Tanenbaum -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269432940.10129.67145.ca...@zakaz.uk.xensource.com
Re: linux perf tool
On Wed, 2010-03-24 at 14:43 +0900, Miles Bader wrote: Is the perf tool in recent linux kernel trees packaged anywhere in debian? No, see bug #548715. Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Processed: Re: [Pkg-utopia-maintainers] Bug#575229: network-manager: Wireless performance problems with ath5k driver
Processing commands for cont...@bugs.debian.org: reassign 575229 linux-image-2.6.32-3-686 Bug #575229 [network-manager] network-manager: Wireless performance problems with ath5k driver Bug reassigned from package 'network-manager' to 'linux-image-2.6.32-3-686'. Bug No longer marked as found in versions network-manager/0.8-1. forwarded 575229 https://bugzilla.kernel.org/show_bug.cgi?id=12635 Bug #575229 [linux-image-2.6.32-3-686] network-manager: Wireless performance problems with ath5k driver Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=12635'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12694335857102.transcr...@bugs.debian.org
Processed: merging 548715 568844
Processing commands for cont...@bugs.debian.org: merge 548715 568844 Bug#548715: please ship tools/perf/perf Bug#568844: linux-image-2.6-686: are we packaging the upstream shipped tools Merged 548715 568844. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12694336387567.transcr...@bugs.debian.org
Processed: retitle 575223 linux-2.6: please enable STV0900/STV0903(A/B) based DVB frontends (CONFIG_DVB_STV090x)
Processing commands for cont...@bugs.debian.org: retitle 575223 linux-2.6: please enable STV0900/STV0903(A/B) based DVB frontends (CONFIG_DVB_STV090x) Bug #575223 [linux-2.6] linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card Changed Bug title to 'linux-2.6: please enable STV0900/STV0903(A/B) based DVB frontends (CONFIG_DVB_STV090x)' from 'linux-image-2.6.33-2-686: budget.ko causes kernel Oops with TT-budget S2-1600 DVB pci card' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12694338769529.transcr...@bugs.debian.org
Bug#575207: [PATCH] V4L/DVB: budget: Oops: BUG: unable to handle kernel NULL pointer dereference
Hi,
Bjørn Mork wrote:
Never call dvb_frontend_detach if we failed to attach a frontend. This fixes
the following oops, which will be triggered by a missing stv090x module:
[8.172997] DVB: registering new adapter (TT-Budget S2-1600 PCI)
[8.209018] adapter has MAC addr = 00:d0:5c:cc:a7:29
[8.328665] Intel ICH :00:1f.5: PCI INT B - GSI 17 (level, low) -
IRQ 17
[8.328753] Intel ICH :00:1f.5: setting latency timer to 64
[8.562047] DVB: Unable to find symbol stv090x_attach()
[8.562117] BUG: unable to handle kernel NULL pointer dereference at
00ac
[8.562239] IP: [e08b04a3] dvb_frontend_detach+0x4/0x67 [dvb_core]
...
Ref http://bugs.debian.org/575207
Signed-off-by: Bjørn Mork bj...@mork.no
Cc: sta...@kernel.org
Cc: 575...@bugs.debian.org
---
This patch should apply cleanly to 2.6.32, 2.6.33, 2.6.34-rc2 and with an
offset to git://linuxtv.org/v4l-dvb.git
Please apply to all of them
drivers/media/dvb/ttpci/budget.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/drivers/media/dvb/ttpci/budget.c
b/drivers/media/dvb/ttpci/budget.c
index e48380c..95a463c 100644
--- a/drivers/media/dvb/ttpci/budget.c
+++ b/drivers/media/dvb/ttpci/budget.c
@@ -643,9 +643,6 @@ static void frontend_init(struct budget *budget)
budget-i2c_adap,
tt1600_isl6423_config);
- } else {
- dvb_frontend_detach(budget-dvb_frontend);
- budget-dvb_frontend = NULL;
}
}
break;
This patch fixes only one of three possible problems.
Could you please extend your patch in a way
that it will also catch, if
- dvb_attach(stv6110x_attach,...)
- dvb_attach(isl6423_attach,...)
fail?
CU
Oliver
--
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201003241325.52...@orion.escape-edv.de
Bug#575226: missed libdrm
I found out that libdrm may be relevant too: http://packages.debian.org/changelogs/pool/main/libd/libdrm/libdrm_2.4.18-3/changelog#versionversion2.4.18-1 libdrm (2.4.17-1) unstable; urgency=low [...] * Enable libdrm_radeon, interface to kernel graphics memory management on radeon (closes: #558786). [...] -- Brice Goglin bgog...@debian.org Sun, 31 Jan 2010 20:12:38 +0100 I'll try to revert this package as well. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003241252.47...@bender.stalag13.ici
Re: Bug#516374 Help with Xen kernel
I'm now using the most recent update in stable. No crashes in last week. I have ~ 70 DomUs in ~ 8 Dom0 , most of them in 64 because i was thinking that 64 OS is better for 64 architecture, not for a specific use. Dom0 never crashes, just DomUs. For now i will stay with xen-amd64 Lenny kernels and see how it goes. I dont want to migrate 64 - 32 because i dont have time for that. If it became necessary, then i will do it with the 2.6.32 stuff in my deploy servers to provide you a feedback. Provide feedback in this list/thread ? I'm been using Debian for 10 years and i'm happy to see this great support. Thank you. On Tue, Mar 23, 2010 at 6:02 AM, Ian Campbell i...@hellion.org.uk wrote: On Mon, 2010-03-22 at 15:24 -0300, Jorge Eduardo Birck wrote: Ok, this bug is fixed in non Xen-specific packages (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516374) The 120 seconds message is a very generic symptom which can have lots of root causes. As Ben notes towards the end of the bug that particular bug has basically become useless because so many different root causes have been mixed together. , how about the Xen-specific kernels, how to use a non-xen kernel in 64 xen servers? How to keep it stable? There's a lot of people using Xen and Debian, how is the best solution for a stable (production) kernel? (Xen+Lenny) ? Use the 2.6.32-10-xen sid kernel in production servers?!? 1) Today Dom0 - 2.6.26-2-xen-amd64 DomU - 2.6.26-2-xen-amd64 - BUG #516374 very unstable Have you tried the most recent kernel in stable-proposed-updates? I think that has a few fixes relating to Xen in it (I don't know if they specifically relate to any 120 seconds issue though). As far as I know your other choices are: * run a backport of the 2.6.32 kernel (for domU either the -amd64 one or the -xen-amd64 one, I'd lean towards the former unless you need features only present in the later). * Build your own kernel from one of the upstream kernels (either from xen.org or kernel.org) * Grab and rebuild a supported Xen kernel from another distro I am of the opinion that the 2.6.32 stuff is pretty good for domU use, although you might want to start with a test deployment on some of you less critical production servers until you build some confidence of your own. You'd certainly be doing Debian a valuable service by providing feedback on how this works for you in practice. If you have suitable hardware support you might also consider running a native 64 bit kernel in an HVM domU. 2) Not possible Dom0 - 2.6.26-2-xen-amd64 DomU - 2.6.26-2-amd64 - Error: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images') There was no 64-bit pvops support in 2.6.26 so that kernel has no Xen support. 3) Ok, but no security Dom0 - 2.6.26-2-xen-amd64 DomU - 2.6.18-6-xen-amd64 - OK, etch kernel stable, but no security upgrades. Correct. 4) Not 64 Dom0 - 2.6.26-2-xen-686 - NOT 64 :( , incompatible DomU - 2.6.26-2-686-bigmem - OK! , but i want to use 64 servers. You can run 64 bit dom0 with 32 bit domUs, or a mixture or 32 and 64bit domUs. Probably not what you want from the sounds of things. I'm not sure why you need specifically 64 bit servers, in general Xen's sweet spot performance wise is 32 bit guests on a 64 bit hypervisor so if you have no specific need for 64 bit I'd recommend using 32 bit guests. Ian. -- Ian Campbell You can go anywhere you want if you look serious and carry a clipboard. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/dd1d2e611003240553q5ec1727cxeaf603282b3d7...@mail.gmail.com
Bug#575183: fails to boot on SGI C2108-F6 server under Xen 3.4 hypervisor
On Wed, Mar 24, 2010 at 12:15:40PM +, Ian Campbell wrote: The kernel should probably catch the ENOSYS from the new PHYSDEVOP_setup_gsi hypercall (which is what the hypervisor update is required for) and panic with a more useful/specific error message. I'm not sure if that would prevent a reboot loop though so perhaps that wouldn't help much. This would not help because current kernels calls this before the console setup. This should be also fixed with my last patches. Bastian -- The face of war has never changed. Surely it is more logical to heal than to kill. -- Surak of Vulcan, The Savage Curtain, stardate 5906.5 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324125408.ga12...@wavehammer.waldi.eu.org
Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686
On Wed, 2010-03-24 at 08:21 +0100, spitzauer...@gmx.de wrote: Hi, yesterday i mad an aptitude full-upgrade because i saw the new kernel image 2.6.32-3-686, which may correct my problem. But now i have really serious problem. The Ethernet is still not working with this kernel and Knoppix too!!! So my rtl8169 is broken and i cannot make that workaround with Knoppix. I had no time to investigate this more. But maybe it's a firmware problem, because if i made aptitude full-upgrade i saw this: update-initramfs: Generating /boot/initrd.img-2.6.32-3-686 W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169 Running update-grub. Only the RTL8168D chips want this firmware, and they appear to mostly work without it. I tried also Adrien Clerc tip, without success. Hopefully my onboard network cards have no hardware damage. Any Suggestion? Thanks! I don't think I saw your original bug report, but the problem seems to be that the hardware is failing to read all of the MAC address out of EEPROM: bad: [4.867561] eth0: RTL8169sc/8110sc at 0xf7c94000, 00:00:00:00:c0:e7, XID 1800 IRQ 18 [4.875112] eth1: RTL8169sc/8110sc at 0xf7cf, 00:00:00:00:c0:e8, XID 1800 IRQ 19 good: [4.868080] eth0: RTL8169sc/8110sc at 0xf7ce2000, 00:30:18:b0:c0:e7, XID 1800 IRQ 18 [4.937598] eth1: RTL8169sc/8110sc at 0xf7d2e000, 00:30:18:b0:c0:e8, XID 1800 IRQ 19 I don't see any changes to r8169 between kernel versions 2.6.26 and 2.6.32 that might explain this, but it could be dependent on timing. You may be able to work around this for now: 1. In /etc/udev/rules.d/70-persistent-net.rules, map the broken MAC addresses to eth0 and eth1. 2. In /etc/network/interfaces, use the hwaddress setting to fix the MAC addresses. Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Processed: reassign 575226 to xserver-xorg-video-radeonhd, retitle 575226 to radeonhd does not support KMS
Processing commands for cont...@bugs.debian.org: reassign 575226 xserver-xorg-video-radeonhd Bug #575226 [firmware-linux-nonfree] firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770 Bug reassigned from package 'firmware-linux-nonfree' to 'xserver-xorg-video-radeonhd'. Bug No longer marked as found in versions firmware-nonfree/0.23. retitle 575226 radeonhd does not support KMS Bug #575226 [xserver-xorg-video-radeonhd] firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770 Changed Bug title to 'radeonhd does not support KMS' from 'firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770' # so I assume tags 575226 wontfix Bug #575226 [xserver-xorg-video-radeonhd] radeonhd does not support KMS Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126943577726843.transcr...@bugs.debian.org
Re: Bug#516374 Help with Xen kernel
On Wed, 2010-03-24 at 09:53 -0300, Jorge Eduardo Birck wrote: I'm now using the most recent update in stable. No crashes in last week. Excellent news! i will do it with the 2.6.32 stuff in my deploy servers to provide you a feedback. Provide feedback in this list/thread ? If you find issues then I think filing bugs would be useful. It would be useful to hear on the list even if you don't have any issues -- it's always useful to know when something works! Thanks, Ian. -- Ian Campbell You have Egyptian flu: you're going to be a mummy. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269437181.10129.67573.ca...@zakaz.uk.xensource.com
Bug#575241: initramfs-tools: long delay with nouveau module in the initramfs
Package: initramfs-tools Version: 0.93.4 I decided to give nouveau a try and built a vanilla 2.6.33.1 kernel with it. This works okay if the nouveau module is not in the initramfs, it then gets loaded by udev in runlevel S. But when I added it to /etc/initramfs-tools/modules to set the resolution as early as possible, the next boot took ~1 minute before the module got loaded and the resolution was set. This is reproducible both with video=nouveau and without any video or vga parameter on the commandline. Any advice how to debug this is appreciated. -- Package-specific info: -- /proc/cmdline root=LABEL=/ ro acpi_enforce_resources=lax quiet -- /proc/filesystems ext2 ext3 ext4 iso9660 -- lsmod Module Size Used by aes_generic26034 2 coretemp4133 0 w83627ehf 19961 0 hwmon_vid 1700 1 w83627ehf hwmon 1321 2 coretemp,w83627ehf arc41258 2 ecb 1809 2 cryptomgr 93318 0 crypto_hash 9875 1 cryptomgr aead4402 1 cryptomgr pcompress 1249 1 cryptomgr crypto_blkcipher8212 2 ecb,cryptomgr crypto_algapi 10322 8 aes_generic,arc4,ecb,cryptomgr,crypto_hash,aead,pcompress,crypto_blkcipher rt73usb19312 0 crc_itu_t 1259 1 rt73usb rt2x00usb 6471 1 rt73usb rt2x00lib 19021 2 rt73usb,rt2x00usb mac80211 68 2 rt2x00usb,rt2x00lib cfg80211 108371 2 rt2x00lib,mac80211 snd_hda_codec_realtek 239093 1 snd_hda_intel 17410 0 snd_hda_codec 45768 2 snd_hda_codec_realtek,snd_hda_intel snd_intel8x0 23690 0 snd_ac97_codec 97889 1 snd_intel8x0 ac97_bus1054 1 snd_ac97_codec snd_pcm_oss29453 0 snd_mixer_oss 12211 1 snd_pcm_oss snd_pcm54271 5 snd_hda_intel,snd_hda_codec,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_seq_oss22664 0 snd_seq_midi_event 4516 1 snd_seq_oss snd_seq40365 5 snd_seq_oss,snd_seq_midi_event sg 20821 0 snd_timer 15357 2 snd_pcm,snd_seq snd_seq_device 4429 2 snd_seq_oss,snd_seq snd42638 13 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_seq,snd_timer,snd_seq_device soundcore 4575 1 snd snd_page_alloc 5817 3 snd_hda_intel,snd_intel8x0,snd_pcm sr_mod 10451 0 intel_agp 24421 0 uhci_hcd 17900 0 ehci_hcd 28650 0 usbcore 109948 4 rt73usb,rt2x00usb,uhci_hcd,ehci_hcd sky2 37025 0 cdrom 28292 1 sr_mod pcspkr 1667 0 evdev 7268 4 8250_pnp4468 0 parport_pc 28188 0 8250 17437 1 8250_pnp parport24995 1 parport_pc serial_core14976 1 8250 i2c_i8016756 0 processor 28535 0 thermal11743 0 fan 3250 0 nouveau 367386 2 ttm38346 1 nouveau drm_kms_helper 19697 1 nouveau drm 136450 4 nouveau,ttm,drm_kms_helper i2c_algo_bit4279 1 nouveau button 4570 1 nouveau -- /etc/kernel-img.conf # This is the /etc/kernel-img.conf file # Set to Yes if you want the kernel image vmlinuz in /boot rather # than the default /. link_in_boot = Yes # By default, the kernel image post installation script shall create or # update the /vmlinuz and /vmlinuz.old symbolic links. This is true if # a /vmlinuz link already exists, however, in absence of /vmlinuz, the # script looks to see if this configuration file exists. If it does # not, the configuration script asks the user whether to create the # symbolic link, and stashes the answer in a newly created # /etc/kernel-img.conf. If the configuration file already exists, and # if this option is set to No, no symbolic link is ever created. This # for people who have other means of booting their machines, and do not # like the symbolic links cluttering up their / directory. do_symlink = No # Whether to use symlinks to the image file. Mutually exclusive to # reverse_symlink. Can be used with link_in_boot. If set to Yes, the # image is placed in vmlinuz (instead of /boot/vmlinuz- X.X.XX). The # old vmlinuz is moved to vmlinuz.old unconditionally. (Normally, that # is only done if the version of the new image differs from the old # one). This restricts you to two images, unless you take additional # action and save copies of older images. This is for people who have # boot on a system that does not use symbolic links (and say, they use # loadlin as a boot loader).
Bug#575241: initramfs-tools: long delay with nouveau module in the initramfs
On Wed, Mar 24, 2010 at 02:27:55PM +0100, Sven Joachim wrote: Package: initramfs-tools Version: 0.93.4 I decided to give nouveau a try and built a vanilla 2.6.33.1 kernel with it. This works okay if the nouveau module is not in the initramfs, it then gets loaded by udev in runlevel S. But when I added it to /etc/initramfs-tools/modules to set the resolution as early as possible, the next boot took ~1 minute before the module got loaded and the resolution was set. This is reproducible both with video=nouveau and without any video or vga parameter on the commandline. Any advice how to debug this is appreciated. kms stuff has no place in initramfs, will close. the 1 min hang is due to loading the module while udev is not running this will be cured soon but isn't yet. anyway happ to see that people test out nouveau, also you should see it in latest 2.6.32 in sid. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324132729.gh22...@baikonur.stro.at
Processed: Re: Bug#575226: Info received (Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770)
Processing commands for cont...@bugs.debian.org: reassign 575226 firmware-linux-nonfree Bug #575226 [xserver-xorg-video-radeonhd] firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- Bug reassigned from package 'xserver-xorg-video-radeonhd' to 'firmware-linux-nonfree'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126944021212975.transcr...@bugs.debian.org
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
On Wed, Mar 24, 2010 at 02:51:40PM +0100, Mathieu Roy wrote: I did not know that. To me, it seemed like radeonhd driver was the future and radeon some kind of legacy driver. Apparently, it is not. It was the future until radeon included its own support for r500+ boards. For some time, both had their advantages and drawbacks. But now KMS/DRI2 (and probably r800 support too) is only in radeon. And radeonhd gets pretty much no development anymore. I think it should be documented somewhere. I just updated the radeon NEWS file accordingly. And considering the results of running firmware-linux-nonfree with xserver-xorg-video-radeonhd (blank screen,, maybe it would be nice to add a conflict against xserver-xorg-video- radeonhd and a suggest in favor of xserver-xorg-video-radeon. I think radeonhd should work a recent firmware and libdrm if KMS is disabled. So this conflicts would be wrong. Brice -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324142137.ga13...@loulous.org
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
On Wed, Mar 24, 2010 at 14:51:40 +0100, Mathieu Roy wrote: severity 575226 minor retitle 575226 firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- video-radeonhd and should suggest xserver-xorg-video-radeon thanks firmware-linux-nonfree has nothing to do with this. Le mercredi 24 mars 2010, Julien Cristau a écrit : On Wed, Mar 24, 2010 at 12:40:36 +0100, Mathieu Roy wrote: Regarding X, only xserver-xorg-core, xserver-xorg, xserver-xorg-video-radeon was recently upgraded. The latest xserver-xorg-video-radeon package enables kernel mode setting. This is incompatible with the radeonhd X driver. You should use the radeon driver instead. I did not know that. To me, it seemed like radeonhd driver was the future and radeon some kind of legacy driver. Apparently, it is not. Right, radeonhd is dying at this point. I switched to the radeon driver and now it works (only with the latest kernel). I think it should be documented somewhere. And considering the results of running firmware-linux-nonfree with xserver-xorg-video-radeonhd (blank screen), maybe it would be nice to add a conflict against xserver-xorg-video- radeonhd and a suggest in favor of xserver-xorg-video-radeon. If nothing else, it will be documented in radeon's NEWS.Debian file (http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=blob;f=debian/xserver-xorg-video-radeon.NEWS), and probably in the release notes for squeeze. Cheers, Julien signature.asc Description: Digital signature
Re: Processed: Re: Bug#575226: Info received (Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770)
reassign 575226 xserver-xorg-video-radeonhd retitle 575226 radeonhd broken with KMS severity 575226 serious tag 575226 sid kthxbye On Wed, Mar 24, 2010 at 14:18:03 +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 575226 firmware-linux-nonfree Bug #575226 [xserver-xorg-video-radeonhd] firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- Bug reassigned from package 'xserver-xorg-video-radeonhd' to 'firmware-linux-nonfree'. thanks Stopping processing here. Please don't second-guess package maintainers. Cheers, Julien signature.asc Description: Digital signature
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
Le mercredi 24 mars 2010, vous avez écrit : On Wed, Mar 24, 2010 at 14:51:40 +0100, Mathieu Roy wrote: severity 575226 minor retitle 575226 firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- video-radeonhd and should suggest xserver-xorg-video-radeon thanks firmware-linux-nonfree has nothing to do with this. I get your point. The real issue is having both firmware-linux-nonfree and radeonhd installed, as radeonhd will automatically call the firmware contained in firmware-linux- nonfree, which will result in a blank screen (not very user friendly). Maybe it is best if radeonhd driver include a conflict against firmware-linux- nonfree 0.22, so the issue remains fully in the responsible hands of radeonhd people. I cannot say. Feel free to reassign back the bug to radeonhd in that case. I spent quite some time to find out exactly why it stopped working this morning (and since you get a blank screen with no way back to the console, you have to reboot at each failure), I'd just like to avoid other users to waste their time the same way. It does not matter to me whether it is achieved by adding a conflit in one package control file or another. I think it should be documented somewhere. And considering the results of running firmware-linux-nonfree with xserver-xorg-video-radeonhd (blank screen), maybe it would be nice to add a conflict against xserver-xorg-video- radeonhd and a suggest in favor of xserver-xorg-video-radeon. If nothing else, it will be documented in radeon's NEWS.Debian file (http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=blob ;f=debian/xserver-xorg-video-radeon.NEWS), and probably in the release notes for squeeze. That's good. It would make sense to also mention it in xserver-xorg-video-radeonhd or firmware-linux-nonfree, since it is unusual to look unused packages docs to find out solutions about the one we use (I mean, if you encounter the bug only when using radeonhd driver, you are likely to check NEWS and README for radeonhd and all the other pieces of software you rely on, instead of looking in the NEWS of the alternatives). Regards, -- Mathieu Roy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003241606.49...@bender.stalag13.ici
Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770
Le mercredi 24 mars 2010, Brice Goglin a écrit : And considering the results of running firmware-linux-nonfree with xserver-xorg-video-radeonhd (blank screen,, maybe it would be nice to add a conflict against xserver-xorg-video- radeonhd and a suggest in favor of xserver-xorg-video-radeon. I think radeonhd should work a recent firmware and libdrm if KMS is disabled. So this conflicts would be wrong. Ok. In that case, radeonhd should first test whether KMS is enabled and behave accordingly - or at least send a warning to the user. -- Mathieu Roy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003241611.47...@bender.stalag13.ici
Processed: Re: Processed: Re: Bug#575226: Info received (Bug#575226: firmware-linux-nonfree: firmware shipped in 0.23 cause radeonhd xorg drivers to be unusable with RV770)
Processing commands for cont...@bugs.debian.org: reassign 575226 xserver-xorg-video-radeonhd Bug #575226 [firmware-linux-nonfree] firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- Bug reassigned from package 'firmware-linux-nonfree' to 'xserver-xorg-video-radeonhd'. retitle 575226 radeonhd broken with KMS Bug #575226 [xserver-xorg-video-radeonhd] firmware-linux-nonfree 0.23 is in conflict with xserver-xorg- Changed Bug title to 'radeonhd broken with KMS' from 'firmware-linux-nonfree 0.23 is in conflict with xserver-xorg-' severity 575226 serious Bug #575226 [xserver-xorg-video-radeonhd] radeonhd broken with KMS Severity set to 'serious' from 'minor' tag 575226 sid Bug #575226 [xserver-xorg-video-radeonhd] radeonhd broken with KMS Added tag(s) sid. kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126944454113317.transcr...@bugs.debian.org
Bug#575241: initramfs-tools: long delay with nouveau module in the initramfs
On 2010-03-24 14:27 +0100, maximilian attems wrote: On Wed, Mar 24, 2010 at 02:27:55PM +0100, Sven Joachim wrote: Package: initramfs-tools Version: 0.93.4 I decided to give nouveau a try and built a vanilla 2.6.33.1 kernel with it. This works okay if the nouveau module is not in the initramfs, it then gets loaded by udev in runlevel S. But when I added it to /etc/initramfs-tools/modules to set the resolution as early as possible, the next boot took ~1 minute before the module got loaded and the resolution was set. This is reproducible both with video=nouveau and without any video or vga parameter on the commandline. Any advice how to debug this is appreciated. kms stuff has no place in initramfs, will close. Well, i915 works perfectly fine from initramfs on my laptop. the 1 min hang is due to loading the module while udev is not running this will be cured soon but isn't yet. Okay, I removed nouveau from initramfs for now. anyway happ to see that people test out nouveau, also you should see it in latest 2.6.32 in sid. Actually it is me who started to work on getting xserver-xorg-video-nouveau into shape, see #568162 and #568168. Cheers, Sven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87hbo5ww20@turtle.gmx.de
Bug#575264: linux-image-2.6-amd64: This package depends on 2.6.32-3, but 2.6.32-4 is the latest
Package: linux-image-2.6-amd64 Version: 2.6.32+25 Severity: normal linux-image-2.6-amd64 currently depends on linux-image-2.6.32-3-amd64, but it should in theory depend on linux-image-2.6.32-4-amd64, which is the latest Linux version available in Debian. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/4 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-amd64 depends on: ii linux-image-2.6.32-3-amd642.6.32-9 Linux 2.6.32 for 64-bit PCs linux-image-2.6-amd64 recommends no packages. linux-image-2.6-amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324155037.2989.40229.report...@thue-desktop.kollegiegaarden.dk
Bug#575264: linux-image-2.6-amd64: This package depends on 2.6.32-3, but 2.6.32-4 is the latest
On Wed, Mar 24, 2010 at 04:50:37PM +0100, Thue Janus Kristensen wrote: Package: linux-image-2.6-amd64 Version: 2.6.32+25 Severity: normal linux-image-2.6-amd64 currently depends on linux-image-2.6.32-3-amd64, but it should in theory depend on linux-image-2.6.32-4-amd64, which is the latest Linux version available in Debian. it is not yet build on all archs yet, please check next time before reporting. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324171544.gl22...@baikonur.stro.at
Bug#575283: /usr/sbin/update-initramfs: treats kernel version 2.6.32-trunk-amd64 as newer than 2.6.32-3-amd64
Package: initramfs-tools Version: 0.93.4 Severity: normal File: /usr/sbin/update-initramfs Hi, update-initramfs considers linux-image-2.6.32-trunk-amd64 to be newer than linux-image-2.6.32-3-amd64 causing the initrd of an outdated kernel to be updated. Even though the 2.6.32-trunk kernels are no longer available in the archive, they are probably installed on some machines tracking sid or squeeze and are not going to be removed automatically (that is a good thing), so they will continue to confuse update-initramfs unless they are uninstalled manually. From popcon I got the following counts: $ zgrep image-2.6.32-trunk all-popcon-results.txt.gz | sort -nr -k 3 Package: linux-image-2.6.32-trunk-6864075 756 313 7 Package: linux-image-2.6.32-trunk-amd64 2907 611 200 6 So there seems to be a significant amount of machines having them still installed (only looking at the main variants amd64 and 686). See also bugs #568160 and #570318 covering grub-legacy/grub2 to wrongly sort the -trunk kernel ahead of the newer kernels. Andreas -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-1 GNU cpio -- a program to manage ar ii findutils4.4.2-1 utilities for finding files--find, ii klibc-utils 1.5.15-1small utilities built with klibc f ii module-init-tools3.12~pre2-1 tools for managing Linux kernel mo ii udev 151-3 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.14.2-2 Tiny utilities for small and embed initramfs-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324180716.21446.73279.report...@calzone.localnet
Bug#575283: /usr/sbin/update-initramfs: treats kernel version 2.6.32-trunk-amd64 as newer than 2.6.32-3-amd64
On Wed, Mar 24, 2010 at 07:07:16PM +0100, Andreas Beckmann wrote: Package: initramfs-tools Version: 0.93.4 Severity: normal File: /usr/sbin/update-initramfs Hi, update-initramfs considers linux-image-2.6.32-trunk-amd64 to be newer than linux-image-2.6.32-3-amd64 causing the initrd of an outdated kernel to be updated. Even though the 2.6.32-trunk kernels are no longer available in the archive, they are probably installed on some machines tracking sid or squeeze and are not going to be removed automatically (that is a good thing), so they will continue to confuse update-initramfs unless they are uninstalled manually. From popcon I got the following counts: $ zgrep image-2.6.32-trunk all-popcon-results.txt.gz | sort -nr -k 3 Package: linux-image-2.6.32-trunk-6864075 756 313 7 Package: linux-image-2.6.32-trunk-amd64 2907 611 200 6 So there seems to be a significant amount of machines having them still installed (only looking at the main variants amd64 and 686). See also bugs #568160 and #570318 covering grub-legacy/grub2 to wrongly sort the -trunk kernel ahead of the newer kernels. Andreas dpkg asses it to be greater than numbered, just see get_sorted_versions() uses dpkg --compare-versions. trunk is gone and was a mistake in the first place. people will get over it with 2.6.33 or whatever.. unless someone comes up with clean noninvasive patch i'll close away. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324181239.gn22...@baikonur.stro.at
Bug#575241: initramfs-tools: long delay with nouveau module in the initramfs
On Wed, Mar 24, 2010 at 04:58:47PM +0100, Sven Joachim wrote: On 2010-03-24 14:27 +0100, maximilian attems wrote: On Wed, Mar 24, 2010 at 02:27:55PM +0100, Sven Joachim wrote: Package: initramfs-tools Version: 0.93.4 I decided to give nouveau a try and built a vanilla 2.6.33.1 kernel with it. This works okay if the nouveau module is not in the initramfs, it then gets loaded by udev in runlevel S. But when I added it to /etc/initramfs-tools/modules to set the resolution as early as possible, the next boot took ~1 minute before the module got loaded and the resolution was set. This is reproducible both with video=nouveau and without any video or vga parameter on the commandline. Any advice how to debug this is appreciated. kms stuff has no place in initramfs, will close. Well, i915 works perfectly fine from initramfs on my laptop. [...] The general conditions for the bug are: 1. Module is manually loaded using /etc/initramfs-tools/modules 2. Module needs to load firmware i915 doesn't need to load firmware and is enabled for auto-loading. nouveau does require firmware and will not be enabled for auto-loading until we have user-space packages that work with it. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324183859.gn16...@decadent.org.uk
Bug#572123: marked as done (linux-image-2.6.33-2-amd64: loading fschmd module reboots the machine)
Your message dated Wed, 24 Mar 2010 20:10:06 +0100 with message-id 4baa638e.9000...@abeckmann.de and subject line works in 2.6.33.1 has caused the Debian Bug report #572123, regarding linux-image-2.6.33-2-amd64: loading fschmd module reboots the machine to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 572123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.33-1~experimental.2 Severity: normal Hi, something is broken with the fschmd module in 2.6.33, once the module is loaded the machine reboots immediately. Also on the serial console there is no output from the module except for (sometimes) a timestamp starting a truncated message. If you need more information, please let me know. Andreas -- Package-specific info: ** Version: Linux version 2.6.33-2-amd64 (Debian 2.6.33-1~experimental.2) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Sun Feb 28 18:30:42 UTC 2010 ** Command line: root=UUID=bfc4d8de-5304-4285-adf0-1a5f7f57e765 ro console=tty0 console=ttyS0,115200n8 ** Not tainted ** Kernel log: [3.309687] sda: sda1 sda2 sda3 [3.326628] input: USB Keyboard as /devices/pci:00/:00:1a.1/usb2/2-2/2-2:1.0/input/input1 [3.326671] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-:00:1a.1-2/input0 [3.333581] sda5 [3.353597] Uniform CD-ROM driver Revision: 3.20 [3.358338] sr 2:0:0:0: Attached scsi CD-ROM sr0 [3.358434] sd 0:0:0:0: [sda] Attached SCSI disk [3.372848] sd 0:0:0:0: Attached scsi generic sg0 type 0 [3.378240] sr 2:0:0:0: Attached scsi generic sg1 type 5 [3.435526] input: USB Keyboard as /devices/pci:00/:00:1a.1/usb2/2-2/2-2:1.1/input/input2 [3.444659] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID v1.10 Device [ USB Keyboard] on usb-:00:1a.1-2/input1 [3.456122] usbcore: registered new interface driver usbhid [3.461733] usbhid: USB HID core driver [3.849364] device-mapper: uevent: version 1.0.3 [3.854181] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-de...@redhat.com [3.870378] PM: Starting manual resume from disk [3.875447] PM: Resume from partition 8:2 [3.875448] PM: Checking hibernation image. [3.875577] PM: Error -22 checking image file [3.875579] PM: Resume from disk failed. [3.883284] REISERFS (device sda1): found reiserfs format 3.6 with standard journal [3.891601] REISERFS (device sda1): using ordered data mode [3.929610] REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [3.945203] REISERFS (device sda1): checking transaction log (sda1) [3.991520] REISERFS (device sda1): Using r5 hash to sort names [6.135026] udevd version 125 started [6.482635] EDAC MC: Ver: 2.1.0 Feb 28 2010 [6.704201] EDAC MC0: Giving out device to 'x38_edac' 'x38': DEV :00:00.0 [6.821417] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [6.830412] ACPI: Power Button [PWRB] [6.846189] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [6.872169] ACPI: Power Button [PWRF] [7.230071] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 19 [8.127185] HDA Intel :00:1b.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [8.134538] alloc irq_desc for 30 on node -1 [8.134540] alloc kstat_irqs on node -1 [8.134551] HDA Intel :00:1b.0: irq 30 for MSI/MSI-X [8.134586] HDA Intel :00:1b.0: setting latency timer to 64 [8.336169] hda_codec: ALC262: BIOS auto-probing. [8.342099] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 83.411874] Adding 7815612k swap on /dev/sda2. Priority:-1 extents:1 across:7815612k [ 92.353447] loop: module loaded [ 92.996100] fuse init (API version 7.13) [ 93.141444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 93.152693] SGI XFS Quota Management subsystem [ 93.167912] XFS mounting filesystem sda5 [ 93.256338] Ending clean XFS mount for filesystem: sda5 [ 94.060633] ip_tables: (C) 2000-2006 Netfilter Core Team [ 94.474674] Netfilter messages via NETLINK v0.30. [ 94.516043] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 94.520753] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 94.522347] CONFIG_NF_CT_ACCT is deprecated and
Collecting additional bootloader/hypervisor information from reportbug hooks?
#575183 suggests that it would be useful to know which hypervisor was
installed when reportbug is used to report a bug against the kernel.
Any objection to adding xen-hypervisor to
linux-2.6/debian/templates/image.plain.bug/control? It seems from a
quick test that this follow dependencies and generates what seems to be
the right thing to me e.g
Versions of packages linux-image-2.6.32-3-xen-amd64 is related to:
pn firmware-bnx2none (no description available)
pn firmware-bnx2x none (no description available)
pn firmware-ipw2x00 none (no description available)
ii firmware-ivtv0.23Binary firmware for
iTVC15-family
pn firmware-iwlwifi none (no description available)
pn firmware-linux none (no description available)
ii firmware-linux-nonfree 0.23Binary firmware for
various driver
pn firmware-qlogic none (no description available)
pn firmware-ralink none (no description available)
ii xen-hypervisor-3.4-amd64 [xe 3.4.3~rc3-1 The Xen Hypervisor on AMD64
Given that I would like to make changes in both trunk and the sid branch
is there a normal procedure there or should I just make equivalent
commits in both places?
I was also thinking it might also be useful to include the output of ls
-lRt /boot and/or /boot/grub/{grub.cfg,menu.lst}/other-bootloader-cfgs
via one of the report bug hooks. I was wondering if that had been
considered and rejected for some reason (privacy issues perhaps?) I
guess perhaps the bootloader config thing might be appropriately handled
by having bootloader packages drop some control info in the right
place (whatever that might be).
Ian.
--
Ian Campbell
In matters of principle, stand like a rock; in matters of taste, swim with
the current.
-- Thomas Jefferson
signature.asc
Description: This is a digitally signed message part
Bug#531604: Stability issues - CPU stuck issues
On Sun, Feb 14, 2010 at 11:01:35PM +0100, Moritz Muehlenhoff wrote: On Tue, Jun 02, 2009 at 12:33:29PM -0500, Adam Majer wrote: Package: linux-image-2.6.26-2-vserver-686 Version: 2.6.26-15lenny2 Severity: important I haven't checked severity of this problem, but this kernel does not seem to be very stable. It seems almost every hour, whenever there is lots of IO, the CPU gets stuck. I'm attaching log entries for the 2 of the occurrences. Is this a known problem with stable kernels? We've had a few scheduler related fixes in previous point updates. Does this still occur with up-to-date Lenny kernels? Unfortunately, I cannot really test this anymore. I have migrated off of vservers to lxc so I'm using 2.6.32+ kernel now. Furthermore, the machine that did originally run this kernel has suffered a hardware failure (at least electrolytic capacitors reached their EOL and need to be replaced). - Adam -- Adam Majer ad...@zombino.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324202721.ga7...@mira.lan.galacticasoftware.com
Bug#521615: 2.6.26.8 and hpet=force works
Moritz Muehlenhoff schrieb: tags 521615 moreinfo thanks Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. I have this kernel currently running and it works without this problem. Maybe this can be closed. Thanks, Henrik -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4baa8333.9050...@nachtwindheim.de
Bug#521615: marked as done (linux-image-2.6.26-1-686: Clock hangs for exactly 300 seconds)
Your message dated Wed, 24 Mar 2010 23:10:08 +0100 with message-id 20100324221008.ga2...@galadriel.inutil.org and subject line Re: 2.6.26.8 and hpet=force works has caused the Debian Bug report #521615, regarding linux-image-2.6.26-1-686: Clock hangs for exactly 300 seconds to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 521615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal In the last days I noticed some strange behaviour on my Toshiba Laptop. My clock stops for exactly 300 seconds, then it continues running as if nothing happened, but 300s in the past. I'm working under high cpu-load (kernel-compiling and number crunching), at a cpu temerature of 54°C, imho is okay. Also I'm working with icewm, having serveral xterms open. In these 300s the mouse and keyboard work fine. Only horizontally workspace switching (mouse) does not work, but I think this is timer based and if time stands still on my system switching can't work. The xterm stops responding if I make auto completion (TAB) or sommething filesystem releated (calling cat), for these 300s also. These hangs can also happen two times in a row. The only kernel message releated with this is this Clocksource tsc unstable, but it is the first time I notice it and it doesn't happen at every hang. I reported this under linux-image, cause the kernel is responsible for the clock. I'm going to try a newer kernel and look if that problem still occours on my laptop. Atm I have only two ideas: 1) Hardware failure 2) or some 300s timeout which gets triggered and doesn't inform the user. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 13 18:08:45 UTC 2009 ** Command line: root=/dev/hda1 ro hpet=force usbcore.autosuspend=1 ** Not tainted ** Kernel log: [ 22.662603] iTCO_wdt: Found a ICH4-M TCO device (Version=1, TCOBASE=0xd860) [ 22.662711] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 23.450372] ACPI: PCI Interrupt :00:1f.6[B] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 [ 23.450523] PCI: Setting latency timer of device :00:1f.6 to 64 [ 23.504328] ieee80211_crypt: registered algorithm 'NULL' [ 23.513893] ieee80211: 802.11 data/management/control stack, git-1.1.13 [ 23.513956] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [ 23.529336] Yenta: CardBus bridge found at :01:0b.0 [1179:0001] [ 23.529421] PCI: Bus 2, cardbus bridge: :01:0b.0 [ 23.529472] IO window: 0xc000-0xc0ff [ 23.529525] IO window: 0xc400-0xc4ff [ 23.529577] PREFETCH window: 0x2840-0x287f [ 23.529631] MEM window: 0x2c00-0x2fff [ 23.565012] input: ImPS/2 Generic Wheel Mouse as /class/input/input6 [ 23.596264] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [ 23.596326] ipw2100: Copyright(c) 2003-2006 Intel Corporation [ 23.661025] parport_pc 00:0b: activated [ 23.661086] parport_pc 00:0b: reported by Plug and Play ACPI [ 23.661184] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 23.662495] Yenta: ISA IRQ mask 0x0038, PCI irq 11 [ 23.662546] Socket status: 3007 [ 23.662596] pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff [ 23.662651] cs: IO port probe 0xc000-0xcfff: clean. [ 23.663378] pcmcia: parent PCI bridge Memory window: 0xcff0 - 0xcfff [ 23.663783] Yenta: CardBus bridge found at :01:0b.1 [1179:0001] [ 23.663859] PCI: Bus 4, cardbus bridge: :01:0b.1 [ 23.663909] IO window: 0xc800-0xc8ff [ 23.663961] IO window: 0xcc00-0xccff [ 23.664902] PREFETCH window: 0x2880-0x28bf [ 23.664955] MEM window: 0x3000-0x33ff [ 23.792636] Yenta: ISA IRQ mask 0x0038, PCI irq 11 [ 23.792696] Socket status: 3007 [ 23.792745] Yenta: Raising subordinate bus# of parent bus (#01) from #04 to #07 [ 23.792822] pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff [ 23.792876] cs: IO port probe 0xc000-0xcfff: clean. [ 23.793606] pcmcia: parent PCI bridge Memory window: 0xcff0 - 0xcfff [ 23.816914] ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11 [ 23.816977] ACPI: PCI Interrupt :01:0a.0[A] - Link [LNKG] - GSI 11 (level, low) - IRQ 11 [ 23.818005] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [ 23.818075] firmware: requesting
Bug#531604: marked as done (Stability issues - CPU stuck issues)
Your message dated Wed, 24 Mar 2010 23:10:41 +0100 with message-id 20100324221041.gb2...@galadriel.inutil.org and subject line Re: Stability issues - CPU stuck issues has caused the Debian Bug report #531604, regarding Stability issues - CPU stuck issues to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 531604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-vserver-686 Version: 2.6.26-15lenny2 Severity: important I haven't checked severity of this problem, but this kernel does not seem to be very stable. It seems almost every hour, whenever there is lots of IO, the CPU gets stuck. I'm attaching log entries for the 2 of the occurrences. Is this a known problem with stable kernels? - Adam ---End Message--- ---BeginMessage--- On Wed, Mar 24, 2010 at 03:27:21PM -0500, Adam Majer wrote: On Sun, Feb 14, 2010 at 11:01:35PM +0100, Moritz Muehlenhoff wrote: On Tue, Jun 02, 2009 at 12:33:29PM -0500, Adam Majer wrote: Package: linux-image-2.6.26-2-vserver-686 Version: 2.6.26-15lenny2 Severity: important I haven't checked severity of this problem, but this kernel does not seem to be very stable. It seems almost every hour, whenever there is lots of IO, the CPU gets stuck. I'm attaching log entries for the 2 of the occurrences. Is this a known problem with stable kernels? We've had a few scheduler related fixes in previous point updates. Does this still occur with up-to-date Lenny kernels? Unfortunately, I cannot really test this anymore. I have migrated off of vservers to lxc so I'm using 2.6.32+ kernel now. Furthermore, the machine that did originally run this kernel has suffered a hardware failure (at least electrolytic capacitors reached their EOL and need to be replaced). Ok, let's close the bug, then. Cheers, Moritz ---End Message---
Bug#574553: Any fix?
Any fix for this bug? I can't install anything due to this update-initramfs error. Thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269471844.5272.20.ca...@gollum.casa.local
Bug#574553: Any fix?
On Thu, Mar 25, 2010 at 12:04:04AM +0100, Jesús Ángel del Pozo Domínguez wrote: Any fix for this bug? I can't install anything due to this update-initramfs error. the easy fix for your issue on your box is to not have multiple bootloader installed. do you still use lilo? if not deinstall it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100324234445.go22...@baikonur.stro.at
Bug#574553: Any fix?
Thanks a lot! I forget to uninstall LILO. I have uninstalled it and now all is OK. Thanks again. El jue, 25-03-2010 a las 00:44 +0100, maximilian attems escribió: On Thu, Mar 25, 2010 at 12:04:04AM +0100, Jesús Ángel del Pozo Domínguez wrote: Any fix for this bug? I can't install anything due to this update-initramfs error. the easy fix for your issue on your box is to not have multiple bootloader installed. do you still use lilo? if not deinstall it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269475269.5272.22.ca...@gollum.casa.local
Re: Collecting additional bootloader/hypervisor information from reportbug hooks?
On Wed, 2010-03-24 at 19:35 +, Ian Campbell wrote:
#575183 suggests that it would be useful to know which hypervisor was
installed when reportbug is used to report a bug against the kernel.
Any objection to adding xen-hypervisor to
linux-2.6/debian/templates/image.plain.bug/control?
If you specify just 'xen-hypervisor' does that cover all package names
beginning with that string? If so we should be doing the same with
'firmware-' rather than listing them all...
It seems from a
quick test that this follow dependencies and generates what seems to be
the right thing to me e.g
Versions of packages linux-image-2.6.32-3-xen-amd64 is related to:
pn firmware-bnx2none (no description
available)
pn firmware-bnx2x none (no description
available)
pn firmware-ipw2x00 none (no description
available)
ii firmware-ivtv0.23Binary firmware for
iTVC15-family
pn firmware-iwlwifi none (no description
available)
pn firmware-linux none (no description
available)
ii firmware-linux-nonfree 0.23Binary firmware for
various driver
pn firmware-qlogic none (no description
available)
pn firmware-ralink none (no description
available)
ii xen-hypervisor-3.4-amd64 [xe 3.4.3~rc3-1 The Xen Hypervisor on
AMD64
Given that I would like to make changes in both trunk and the sid branch
is there a normal procedure there or should I just make equivalent
commits in both places?
Do it in both places.
I was also thinking it might also be useful to include the output of ls
-lRt /boot and/or /boot/grub/{grub.cfg,menu.lst}/other-bootloader-cfgs
via one of the report bug hooks.
When the running kernel matches the package being reported on, then no,
we already have /proc/cmdline.
When the running kernel does not match then maybe the boot loader
configuration could be included. This might be a case where we should
ask the user first (same as with networking).
I was wondering if that had been
considered and rejected for some reason (privacy issues perhaps?)
If we do it then we need to be careful to obscure passwords (we've just
been through this with network configuration and took a few iterations
to cover the various possible WPA credentials).
I guess perhaps the bootloader config thing might be appropriately handled
by having bootloader packages drop some control info in the right
place (whatever that might be).
Historically kernel packages had to know about every boot loader. This
has changed lately and new boot loaders are expected to install hook
scripts. But even that only covers updating the loader configuration;
there is no way to read it. (I think this is something to address in
squeeze+1.) For now I think explicit support for LILO, GRUB 1 and GRUB
2 should cover 99% of the systems out there.
Ben.
--
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.
signature.asc
Description: This is a digitally signed message part
Processed: tagging 574553
Processing commands for cont...@bugs.debian.org: tags 574553 pending Bug #574553 [initramfs-tools] initramfs-tools: PostInst fails (err. 2). awk: fatal: ( o \(desemparejados: /(md/ Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126947676413383.transcr...@bugs.debian.org
Processed: tagging 415474
Processing commands for cont...@bugs.debian.org: tags 415474 pending Bug #415474 [initramfs-tools] mkinitramfs fails with monolithic kernels Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126947746018750.transcr...@bugs.debian.org
Processed: forcibly merging 543568 534324
Processing commands for cont...@bugs.debian.org: forcemerge 543568 534324 Bug#543568: initramfs-tools: usb storage device not recognized at boot after upgrade to kernel 2.6.30 Bug#534324: MODULES=most does not include unusual USB storage drivers Forcibly Merged 534324 543568. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126947754519512.transcr...@bugs.debian.org
Processed: tagging 433708
Processing commands for cont...@bugs.debian.org:
tags 433708 pending
Bug #433708 [initramfs-tools] initramfs-tools: Wants to have
/lib/modules/${version}/ present when creating initramfs even under kernel
without modules support
Bug #445735 [initramfs-tools] image creation fails with a non-modular kernel
Added tag(s) pending.
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.126947746218770.transcr...@bugs.debian.org
Processed: tagging 524534
Processing commands for cont...@bugs.debian.org: tags 524534 pending Bug #524534 [initramfs-tools] initramfs-tools: returns error when attempting to remove an already removed initrd Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126947776321821.transcr...@bugs.debian.org
Re: [Fwd: configure_networking: Raise ipconfig timeout to 180 seconds.]
hello, On Mon, 22 Mar 2010, Anna Jonna Armannsdottir wrote: There is no response from the debian-kernel list, so this patch is forwarded to You. still don't see your post to d-kernel, maybe my spam filter was overly zealous, sorry. thanks for repost. Attached are a jpeg screenshot of the boot sequence and of course the patch. The patch is relative to the present git snapshot. thanks applied: http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary modified to break out of loop on said generated file, to not triply indent loop, please check. I also have two related questions: A) you mention a bug of ipconfig, that it exists with wrong message or such, could you please be more explicit on that. also please try out klibc-1.5.17 it both reached Ubuntu lucid and Debian unstable, has several ipconfig fixes. B) as you seem heavy user of configure_networking() could you please review #, I lack the testing ability: http://bugs.debian.org/566295 thanks + kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100325012705.ga4...@stro.at
Processed: tagging 536195
Processing commands for cont...@bugs.debian.org: tags 536195 pending Bug #536195 [initramfs-tools] dropbear remote boot feature exposes initramfs host keys to regular users Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126948290811747.transcr...@bugs.debian.org
Processed: Re: dropbear remote boot feature exposes initramfs host keys to regular users
Processing commands for cont...@bugs.debian.org: retitle 536195 document UMASK initramfs.conf usage Bug #536195 [initramfs-tools] dropbear remote boot feature exposes initramfs host keys to regular users Changed Bug title to 'document UMASK initramfs.conf usage' from 'dropbear remote boot feature exposes initramfs host keys to regular users' stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126948302413169.transcr...@bugs.debian.org
Bug#536195: dropbear remote boot feature exposes initramfs host keys to regular users
retitle 536195 document UMASK initramfs.conf usage stop ls -l /boot/initrd.img-2.6.33-2-amd64 -rw--- 1 root root 9589266 Mar 25 03:03 /boot/initrd.img-2.6.33-2-amd64 egrep UMASK /etc/initramfs-tools/initramfs.conf UMASK=0077 this was not yet documented in initramfs.conf.5, will be in next upload. thanks for report. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100325021003.gk21...@stro.at
