Re: Bug#387767: Installation Failure
The RC2 installer with the 2.6.18 kernel does NOT fix this bug. I tried it today on two different PCs (same hardware). The motherboard is an Intel AL440LX PII-233 with a PhoenixBIOS 4.0 Release 6.0. During post the CD drive is detected by the BIOS as an FX240S. The last couple lines on the screen are as follows: EIP: [d482b9ch] ide_execute_command+0x16/0x73 [ide_core] SS:ESP 0068:c030fe94 0Kernel panic - not syncing: Fatal exception in interrupt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415709: linux-image-2.6.18-4-686: dv1394 oops on device removal
Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-11 Severity: normal Tags: patch, upstream I plugged in a CardBus 1394/USB card and used it to capture video from a DV camera. When I unplugged the card this resulted in an oops, though I didn't notice that immediately. When I plugged the card in again the system hung, apparently due to deadlock in the kernel. This is a known upstream bug in the dv1394 module and the upstream patch fixed it for me (it applies to 2.6.18 at a small offset). http://bugzilla.kernel.org/show_bug.cgi?id=7121 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy linux-image-2.6.18-4-686 recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Wed, Mar 21, 2007 at 06:54:55PM +1100, Hamish Moffatt wrote: [] It runs perfectly stable after 'cpufreq-set -g performance', so I don't think I can rule out the cpufreq stuff. Or ACPI, or SMP PREEMPT. Can you redo your previous observations without taining also? Maybe powernow-k8 and nvidia just can't go together. Which previous observations do you mean? Same results you've mentioned before. With either cpufreq-userspace or cpufreq-ondemand, it crashes, with or without nvidia. With cpufreq set to performance mode it is stable. I don't know of any other cases to test? So, if you are getting relieble crashes, please try * to get minimal test-case, * kernel targeted for experimental/sid: deb http://kernel-archive.buildserver.net/debian-kernel trunk main * or latest upsteam one. And please collect and send all fault logs. This can be useful, when tracing problems. There's one similar report in lkml, i've found: Archived-At: http://permalink.gmane.org/gmane.linux.kernel/474449 Message-ID: [EMAIL PROTECTED] But it have no follow-ups. Thus, as more info you can collect, more chance we can get upsteam interested. _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415740: linux-image-2.6.18-4-xen-vserver-amd64: DHCP does not work well over XEN virtual networking
Package: linux-image-2.6.18-4-xen-vserver-amd64 Version: 2.6.18.dfsg.1-11 Severity: normal I have configured dhcp3-server in dom0 and dhcp3-client in domU. In domU syslog I get: Mar 21 14:58:33 firewall dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Mar 21 14:58:33 firewall dhclient: DHCPOFFER from 192.168.1.1 Mar 21 14:58:33 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 14:58:33 firewall dhclient: DHCPACK from 192.168.1.1 Mar 21 14:58:33 firewall dhclient: bound to 192.168.1.179 -- renewal in 263 seconds. Mar 21 15:02:56 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:00 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:00 firewall dhclient: 6 bad udp checksums in 11 packets Mar 21 15:03:07 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:18 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:25 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:37 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:03:37 firewall dhclient: 4 bad udp checksums in 5 packets Mar 21 15:03:46 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:04:05 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:04:24 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:04:24 firewall dhclient: 3 bad udp checksums in 5 packets Mar 21 15:04:32 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:04:46 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:04:54 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:05:07 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:05:16 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:05:16 firewall dhclient: 5 bad udp checksums in 5 packets Mar 21 15:05:25 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:05:38 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:05:54 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:06:08 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:06:20 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:06:20 firewall dhclient: 5 bad udp checksums in 5 packets Mar 21 15:06:38 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:06:57 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:07:17 firewall dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Mar 21 15:07:34 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:07:34 firewall dhclient: 4 bad udp checksums in 5 packets Mar 21 15:07:42 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:07:54 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:08:15 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:08:32 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:08:32 firewall dhclient: 4 bad udp checksums in 5 packets Mar 21 15:08:35 firewall dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Mar 21 15:08:35 firewall dhclient: DHCPOFFER from 192.168.1.1 Mar 21 15:08:35 firewall dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 21 15:08:35 firewall dhclient: DHCPACK from 192.168.1.1 Mar 21 15:08:35 firewall dhclient: bound to 192.168.1.179 -- renewal in 265 seconds. and in dom0 syslog (timezone differs by 1 hour): Mar 21 15:58:33 p5bvm dhcpd: DHCPDISCOVER from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 15:58:33 p5bvm dhcpd: DHCPOFFER on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 15:58:33 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 (192.168.1.1) from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 15:58:33 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:02:55 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:02:55 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:02:59 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:02:59 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:06 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:06 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:17 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:17 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:24 p5bvm dhcpd: DHCPREQUEST for 192.168.1.179 from 06:18:f3:06:85:75 (firewall) via eth0 Mar 21 16:03:24 p5bvm dhcpd: DHCPACK on 192.168.1.179 to 06:18:f3:06:85:75 (firewall) via
chink virtuosi
Here's your chance CEO AMERICA SYmb-CEO A Stron g B reccomended at 6 Cents Easy 300% on this one in Short term AN ALL AMERICAN COMPANY Get IN Before the rush TOMORROW of the night when his third attempt at a putback resulted in the whistle, and his handle on any night.'' At one point, both Iverson and Anthony were 12-for-16 from the floor. ''When you're in a zone, it doesn't matter if guys are on Iverson said. ''To win four games in a row, you get a certain swagger about -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415474: mkinitramfs fails with monolithic kernels
On Wed, Mar 21, 2007 at 10:20:40PM +0100, Martin Godisch wrote: On Tue, Mar 20, 2007 at 00:36:12 +0100, maximilian attems wrote: mkinitramfs fails when building a ramfs for a monolithic kernel, and so does postinst of kernel-package-generated kernel packages. uuh why do you want an initramfs on a monolithic kernel? I need it to activate the LVM root volume. ok, so please post current errors? when building the initramfs. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415474: mkinitramfs fails with monolithic kernels
On Wed, Mar 21, 2007 at 11:00:38PM +0100, maximilian attems wrote: On Wed, Mar 21, 2007 at 10:20:40PM +0100, Martin Godisch wrote: On Tue, Mar 20, 2007 at 00:36:12 +0100, maximilian attems wrote: mkinitramfs fails when building a ramfs for a monolithic kernel, and so does postinst of kernel-package-generated kernel packages. uuh why do you want an initramfs on a monolithic kernel? I need it to activate the LVM root volume. ok, so please post current errors? when building the initramfs. hmm seems evident after reading your patch. no can't go in in that form, but i'll cook something up. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the -12 question
Steve asked on IRC about doing a -12 for 4.0r0. There are a few RC bugs and a few security bugs that we could fix before then. Of those present on IRC (vorlon, fjp, fs and myself), there was a consensus to proceed. Does anyone on the kernel team object to this? The details... * This would not involve a spin of d-i[1] * No ABI changes would be permitted (obviously) * We would upload to unstable * I've already merged my changes from the etch-security branches onto the etch branch. There are other pending CVEs, but nothing I think is a must before etch (but I might add others while -12 is open) * vorlon would like to see this uploaded over the weekend, I propose an upload before Monday's dinstall. waldi: is it possible to get snapshot builds of the etch branch going for this? * I also propose we use the requirements in my etch-updates proposal for fixes (must have bug filed, must be important or greater) Here's the current list of stuff I'd been tracking for an etch update - this doesn't mean they were approved by the SRM team, just that they are on my list of things to review: http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED];which=tagdata=dkt-etch-update [1] dannf does it mean a spin of d-i? vorlon no dannf (no ABI change would be allowed of course) vorlon it's likely that fjp won't approve, but I've done the due diligence for the GPL source issues, and I see no reason to re-spin d-i over a simple kernel upgrade fjp Unless there are functional fixes in there too that would improve d-i, I guess I can live with it. -- dann frazier | HP Open Source and Linux Organization -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: the -12 question
From: dann frazier Newsgroups: gmane.linux.debian.devel.kernel Subject: the -12 question Date: Wed, 21 Mar 2007 18:44:08 -0600 [] * I also propose we use the requirements in my etch-updates proposal for fixes (must have bug filed, must be important or greater) Is it possible to have a way for ti-usb serial patches (removing firmware and hotplug, tested by upsteam author) there? Shall i file a bug for that? Thanks. _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ltmodem installation kernel source
Dear all, I wanna to install ltmodem,But i must install linux source linux headers at first. When i use uname -a i see 686 in output. When i use ./configure for source of ltmodem,I see following outputs: Checking for kernel headers ... in /usr/src/linux: nope ... in /usr/src/kernel-headers-2.6.18-4-686: nope ... in /usr/src/linux-2.6.18: nope ... in /usr/src/linux-2.6.18-4-686: nope ... in /lib/modules/2.6.18-4-686/build: Kernel headers found in /lib/modules/2.6.18-4-686/build using /lib/modules/2.6.18-4-686/build However, when i use ls command in /usr/src , i see following output: debian:/usr/src# ls kernel-patches linux-headers-2.6.18-4-686 linux-source-2.6.18 linux-headers-2.6.18-4 linux-kbuild-2.6.18 linux-source-2.6.18.tar.bz2 debian:/usr/src# Because i installed related packages. Please help me that i what i do with those directories. Yours,Mohsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415805: Kernel panic on machines with 8 Gbytes of memory
Package: linux-image-2.6.18-4-xen-686 Version: 2.6.18.dfsg.1-11 A server with 8 Gbytes of memory crashes when using xen-create-image or when downloading a very big file. I contacted the xen-devel mailing list, and they gave me a solution for the problem .See this email for details: http://lists.xensource.com/archives/html/xen-devel/2007-03/msg00874.html BUG: unable to handle kernel paging request at virtual address f57ae000 printing eip: c01be5d4 2d747000 - *pde = :d5afe001 2b8fe000 - *pme = :0768a067 0168a000 - *pte = : Oops: [#1] SMP Modules linked in: bridge netloop ipv6 dm_snapshot dm_mirror dm_mod loop i2c_i8n CPU:0 EIP:0061:[c01be5d4]Not tainted VLI EFLAGS: 00010206 (2.6.18-4-xen-686 #1) EIP is at __sync_single+0xa0/0x12a eax: f57ae000 ebx: 1000 ecx: 0400 edx: 0063 esi: f57ae000 edi: c8e7c000 ebp: 0001 esp: ea78bd90 ds: 007b es: 007b ss: 0069 Process perl (pid: 2861, ti=ea78a000 task=c0dc1000 task.ti=ea78a000) Stack: 0001 c8e7c000 0001 f57ae000 c46a7000 6310 0078 0001 c46a7000 c01bead3 0001 0001 c9d0cc3c 8000 c8e7c000 0020 c46a7000 c9d0cc38 00018c40 0078 Call Trace: [c01bead3] map_single+0x16b/0x179 [c01bf11b] swiotlb_map_sg+0x146/0x1c2 [c0108ff3] dma_map_sg+0x74/0x14e [ee09f9b1] ide_build_sglist+0x67/0x6c [ide_core] [ee09f9e1] ide_build_dmatable+0x2b/0x151 [ide_core] [c0122f99] lock_timer_base+0x15/0x2f [ee09fb2a] ide_dma_setup+0x23/0x85 [ide_core] [ee056f49] ide_do_rw_disk+0x344/0x497 [ide_disk] [c01f5513] __add_entropy_words+0x58/0x176 [ee0996da] ide_do_request+0x55a/0x717 [ide_core] [c01ad5b7] freed_request+0x1d/0x37 [ee09914f] ide_end_request+0xc7/0xcf [ide_core] [ee099b05] ide_intr+0x16b/0x194 [ide_core] [c013a823] handle_IRQ_event+0x27/0x51 [c013a8e0] __do_IRQ+0x93/0xe8 [c010612c] do_IRQ+0x43/0x53 [c020c0dc] evtchn_do_upcall+0x64/0x9b [c0104a51] hypervisor_callback+0x3d/0x48 Code: 7c 24 04 89 c6 03 74 24 10 89 44 24 0c 01 ef 2b 7c 24 08 83 3c 24 02 75 0 EIP: [c01be5d4] __sync_single+0xa0/0x12a SS:ESP 0069:ea78bd90 0Kernel panic - not syncing: Fatal exception in interrupt BUG: warning at arch/i386/kernel/smp-xen.c:526/smp_call_function() [c010cdc9] smp_call_function+0x53/0xf8 [c011b4aa] printk+0x14/0x18 [c010ce81] smp_send_stop+0x13/0x1e [c011aad7] panic+0x45/0xde [c0105235] die+0x242/0x276 [c0111cf1] do_page_fault+0xa53/0xb76 [c011129e] do_page_fault+0x0/0xb76 [c0104a0f] error_code+0x2b/0x30 [c01be5d4] __sync_single+0xa0/0x12a [c01bead3] map_single+0x16b/0x179 [c01bf11b] swiotlb_map_sg+0x146/0x1c2 [c0108ff3] dma_map_sg+0x74/0x14e [ee09f9b1] ide_build_sglist+0x67/0x6c [ide_core] [ee09f9e1] ide_build_dmatable+0x2b/0x151 [ide_core] [c0122f99] lock_timer_base+0x15/0x2f [ee09fb2a] ide_dma_setup+0x23/0x85 [ide_core] [ee056f49] ide_do_rw_disk+0x344/0x497 [ide_disk] [c01f5513] __add_entropy_words+0x58/0x176 [ee0996da] ide_do_request+0x55a/0x717 [ide_core] [c01ad5b7] freed_request+0x1d/0x37 [ee09914f] ide_end_request+0xc7/0xcf [ide_core] [ee099b05] ide_intr+0x16b/0x194 [ide_core] [c013a823] handle_IRQ_event+0x27/0x51 [c013a8e0] __do_IRQ+0x93/0xe8 [c010612c] do_IRQ+0x43/0x53 [c020c0dc] evtchn_do_upcall+0x64/0x9b [c0104a51] hypervisor_callback+0x3d/0x48 (XEN) Domain 0 crashed: rebooting machine in 5 seconds. -- Marc Petit-Huguenin Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401916: #401916
Hi David Do you know if your patch [1] you posted to #401916 is going to make it into etch? A few users have been asking about whether it is possible to use an LVM root partition with an external USB drive on the Linksys/NSLU2. I haven't tested your patch on the NSLU2, but I do know that adding a delay before the call to vgchange in /scripts/local-top/lvm in the initramfs allows the NSLU2 to use an LVM root partition on a USB disk. It is not critical because there are other issues with LVM on the NSLU2, such as the installer runs out of memory when setting up the LVM partitions, and one needs to recompile the second stage boot loader to add the rootdelay parameter to the kernel command line. Gordon [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401916;msg=227;filename=udev-support_rootdelay.patch;att=1 -- Gordon Farquharson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
