Re: Scheduling linux-2.6 2.6.18-9
Norbert Tretkowski wrote: * Norbert Tretkowski wrote: * Aneesh Kumar K.V wrote: http://userweb.kernel.org/~akpm/2.6.20-rc1-mm1/broken-out/alpha-increase-percpu_enough_room.patch It's on my TODO list for this weekend. This patch gets us back to the Relocation overflow problem, which was also reported by James Andrewartha on debian-alpha. That could be a binutils bug too. I don't have alpha around to debug. BTW I guess this was there always it didn't throw this error because the percpu error caused the module load to fail. Now that we were able to cross the per cpu error it is hitting the relocation error. -aneesh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403630: installationreport etch
Frans Pop schrieb: reassign 403630 linux-2.6 retitle 403630 Hangs while detecting CD-ROM devices thanks After install I update the Kernel, but get problems booting it. It allways stop at detecting the cdrom-devices. (Kernel 2.6.18-3-k7 and 2.6.18-3-486). With the working kernel 2.6.17-2-486 ther is no CD-ROM device (there must exist hda and hdb) That sounds like a kernel problem. Reassigning to the kernel team. Can you provide the exact messages you see on the console just before the system hangs? Please provide as much context as possible. Now I discovered, that it is no system hang, it yust pause for 30s, and I was to impatient to wait wich leads to this bug-report. some examples for positions where the system pause: SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 hdb ATAPI 52 X DVD-ROM drive, 256kb Cache, UDMA(33) sd 0:0:0:0: atached scsi disk sda then pause for 30s and then continue with Attempting manual resume ... then it stops allways at Compaq touchscreen protocol output for additional 30s another example: SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sd 0:0:0:0: atached scsi disk sda hdb ATAPI 52 X DVD-ROM drive, 256kb Cache, UDMA(33) then pause for 30s and then continue with Attempting manual resume ... But everything was working now with the exception of taking a lot of time to boot, so I removed the 3c905 NIC. The result was that everything was working perfekt after the removal of the additional NIC. No pause during boot anymore. For me this Problem is solved now. best regards, Hubert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403426: linux-image-2.6.18-3-ixp4xx: kernel corrupts LUKS partition header on arm NSLU2
On Mon, Dec 18, 2006 at 12:06:21PM +0100, Martin Michlmayr wrote: Is there some easy way I can reproduce this? Format a disk with LUKS on one PC, connect it to the slug and do what exactly to trigger the corruption? -- Martin Michlmayr http://www.cyrius.com/ Backup the header of the partition for comparison, install cryptsetup, then just: cryptsetup luksOpen partition tag It always corrupts it for me. Sign is the message about header version of cryptsetup and the hang. I am running the root of the slug off a cf card in a usb card reader at the moment - I wonder if that changes the timing. I'm at work at the moment but will try the older kernel on getting home. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403630: marked as done (Hangs while detecting CD-ROM devices)
Your message dated Tue, 19 Dec 2006 14:16:13 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#403630: installationreport etch has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/etch_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso Date: 18.12.06, 16:00 Uhr Machine: Asus M2N-MX Board with nvidia 7300 Graphics Processor: AMD-Athlon64 X2 Memory: Partitions: Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 10199819234367 HPFS/NTFS /dev/sda2 10200 1992578124095 83 Linux /dev/sda3 19926 20654 5855692+ 82 Linux swap / Solaris Output of lspci -nn and lspci -vnn: -nn: 00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1) 00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e0] (rev a2) 00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2) 00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03f5] (rev a2) 00:01.3 Co-processor [0b40]: nVidia Corporation MCP61 SMU [10de:03f4] (rev a2) 00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f1] (rev a2) 00:02.1 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f2] (rev a2) 00:04.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI bridge [10de:03f3] (rev a1) 00:05.0 Audio device [0403]: nVidia Corporation MCP61 High Definition Audio [10de:03f0] (rev a2) 00:06.0 IDE interface [0101]: nVidia Corporation MCP61 IDE [10de:03ec] (rev a2) 00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2) 00:08.0 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2) 00:08.1 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2) 00:09.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e8] (rev a2) 00:0b.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2) 00:0c.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:07.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M [Tornado] [10b7:9200] (rev 74) 02:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown device [10de:0393] (rev a1) -vnn: 00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8234] Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [dc] HyperTransport: MSI Mapping 00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e0] (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8234] Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8234] Flags: 66MHz, fast devsel, IRQ 10 I/O ports at cc00 [size=64] I/O ports at 0600 [size=64] I/O ports at 0700 [size=64] Capabilities: [44] Power Management version 2 00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03f5] (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8234] Flags: 66MHz, fast devsel 00:01.3 Co-processor [0b40]: nVidia Corporation MCP61 SMU [10de:03f4] (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:8234] Flags: bus master, 66MHz, fast devsel, latency 0 Memory at fec8 (32-bit, non-prefetchable) [size=512K] 00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f1] (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc.
Bug#403669: initramfs-tools: framebuffer script assumes module name is same as frame buffer name
On Mon, 18 Dec 2006, Rob Walker wrote: Package: initramfs-tools Version: 0.85c Severity: normal Tags: patch The framebuffer script (/usr/share/initramfs-tools/scripts/init-top/framebuffer) assumes that the name of the option on the command line is the same as the name of the module for the framebuffer. This is not correct for Matrox cards: the command line option is matroxfb, but the module is matroxfb_base. The attached patch adds a map from command line name to module name (only matroxfb for now). thanks applied for 0.85e! same remarks than previous patch :) --- framebuffer.orig 2006-11-14 06:54:08.0 + +++ framebuffer.matroxfb_map 2006-12-18 20:09:51.0 + @@ -72,6 +75,16 @@ esac done +# Map command line name to module name +case $FB in + matroxfb) +FB=matroxfb_base +;; + + *) +;; +esac + if [ -n $FB ]; then modprobe -q fbcon modprobe -q $FB $OPTS best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
* Jeff Licquia [EMAIL PROTECTED] [2006-10-20 19:17]: From a recent run of the LSB 3.1 tests: 10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario ref 858-0 FSG internal testing showed that Fedora Core 5's 2.6.18 kernel does not fail in the same way. I believe I've traced it to a backported change from 2.6.19 development. The specific commit touching msync() is 204ec841fbea3e5138168edbc3a76d46747cc987 in git; it relies on several commits immediately preceding it. I've built Linus's tree on amd64, and it passes the test. I have not, however, built a 2.6.18 kernel with this patch and tested it, though it's the only patch in the Fedora kernel which touches the msync() code. So it seems that the patches needed for msync() conformance we applied from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current discussion on this on lkml. From what I understand it, plain 2.6.18 is not LSB 3.1 conform and you need some fixes which are associated with filesystem corruption. While Andrew, Linus and co are currently trying to come up with a patch, I think it might be better for us to simply back out these patches. What doe it take to get an exception for this LSB test? Surely the reasons cited above (fails with 2.6.18, a fairly current kernel and the patches to fix it are associated with fs corruption) are pretty good arguments for an exception... -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403667: Updated patch for /usr/share/initramfs-tools/scripts/init-top/framebuffer
On 12/19/06, maximilian attems [EMAIL PROTECTED] wrote: On Mon, 18 Dec 2006, Rob Walker wrote: Ooops, I accidentally used some bash specific syntax in the first patch. The attached patch fixes this and should work now. It also makes sure the right option is passed into parse_video_opts (was $TMP, should be $x) applied for 0.85e thanks a lot --- framebuffer.orig 2006-11-14 06:54:08.0 + +++ framebuffer.fixed_parse_video_opts2006-12-18 20:09:51.0 + just nitpicking, such a patch can never apply: Sorry, I was working directly on the script /usr/share/initramfs-tools/, then made a safe copy and re-installed the package to get the diff. I'll grab the debian source package next time. Regards Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401384: fixed in mkvmlinuz 28
found 401384 29 thanks On Fri, Dec 15, 2006 at 11:17:03PM +, Sven Luther wrote: mkvmlinuz (28) unstable; urgency=low . * Added support for 2.6.19 kernels. * Added portuguese translation. (Closes: #401384) pt.po doesn't actually appear to be in the tarball (I'm looking at mkvmlinuz_29.tar.gz); did you maybe forget to 'svn add' it? Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#401384: fixed in mkvmlinuz 28
Processing commands for [EMAIL PROTECTED]: found 401384 29 Bug#401384: [INTL:pt] Portuguese translation for mkvmlinuz (debconf) Bug marked as found in version 29. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402083: bug#402083: your problem is evbug
Please see http://forums.debian.net/viewtopic.php?t=8457 for help with stopping that message from logging. The culprit is evbug and I just stumbled across that via Google (I had the same messages on my box). signature.asc Description: Digital signature
Bug#402083: bug#402083: your problem is evbug
More info about evbug: CONFIG_INPUT_EVBUG: │ │ │ │ Say Y here if you have a problem with the input subsystem and │ │ want all events (keypresses, mouse movements), to be output to │ │ the system log. While this is useful for debugging, it's also │ │ a security threat - your keypresses include your passwords, of │ │ course. │ │ │ │ If unsure, say N. ...but that forum post that I included in the previous email should resolve that for you signature.asc Description: Digital signature
超過激レズの決定版！
女子大生同士が、壮絶！レズシーン！ ディープキス！相互オナニー！迫力ある動画を提供！ http://www1.fgter.com/?bc=wkt15[EMAIL PROTECTED] 受信拒否 [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
On Tue, 2006-12-19 at 17:08 +0100, Martin Michlmayr wrote: So it seems that the patches needed for msync() conformance we applied from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current discussion on this on lkml. From what I understand it, plain 2.6.18 is not LSB 3.1 conform and you need some fixes which are associated with filesystem corruption. While Andrew, Linus and co are currently trying to come up with a patch, I think it might be better for us to simply back out these patches. What doe it take to get an exception for this LSB test? Surely the reasons cited above (fails with 2.6.18, a fairly current kernel and the patches to fix it are associated with fs corruption) are pretty good arguments for an exception... I brought this up at our weekly conference call, which generated quite a lot of discussion. The argument against issuing a waiver is that this isn't strictly required; a distro could fix the problem by downgrading the kernel to 2.6.16. I've also forwarded your message to Ian Murdock, who is the current chair of the LSB Steering Committee. The process for getting an exception is as follows: - Release a product with a problem. - Run the tests, and fail in some way. - Request a waiver from the LSB Specification Authority. There's a link for doing so from the certification site. Of course, the problem is that we have to make a decision now, so we also have an unofficial process of discussing known issues. That process has already been started. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403782: linux-source-2.6.18: realtek 8169 slow (slower than ubuntu)
Package: linux-source-2.6.18 Version: 2.6.18-8 Severity: normal Hi, the kernel I use is built from debian source and 2.6.18-8 patches are applied. The r8169 is on a dlink pci card in a SIS 671 system with a 2.4 GHz P4 CPU. Symptom: Download speed is ok (25 MB/s) but Upload, e.g. the send speed at maximum reaches 13 MB/s. This does not happend under Ubuntu 6.10 where I get 25 MB/s in both directions. You might be amused to read that the 50% send speed reduction also comes for free with window 2003 (driver from dlink cd). Cables and Hub are ok and were checked against other computers. I remember that there was a similar bug report a while ago that got closed. Please merge and reopen. Yours Juergen -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-8-sis Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 05:08:24PM +0100, Martin Michlmayr wrote: So it seems that the patches needed for msync() conformance we applied from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current discussion on this on lkml. From what I understand it, plain 2.6.18 is not LSB 3.1 conform and you need some fixes which are associated with filesystem corruption. While Andrew, Linus and co are currently trying to come up with a patch, I think it might be better for us to simply back out these patches. What doe it take to get an exception for this LSB test? Surely the reasons cited above (fails with 2.6.18, a fairly current kernel and the patches to fix it are associated with fs corruption) are pretty good arguments for an exception... -- Martin Michlmayr http://www.cyrius.com/ why not wait for the fix and backport it?! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330664: feed back: logs of crashing SMP kernel with QLA1040
On remote, I ran: cat /dev/ttyS1 a24_0_5 cat a24_0_5 | tr -d \000\007 |sed s_^$'\x20'\$_REMOVETHISLINE_g |sed s_^\$_REMOVETHISLINE_g | grep -v REMOVETHISLINE |uniq a24_0_5.txt and I ll past below the second file; otherwise, you d have pages or blank lines. The system is Debian on Alpha EV56, AS4100, with one or more QLA1040 in; the ramdisk will thus load QLA12xx driver, and fail if the kernel is SMP, suceed if no SMP support. Truncated the end, pages of missing line number, maybe bad interraction of console on serial with the prompt. *** BEGIN Linux version 2.6.15-1-alpha-smp (Debian 2.6.15-8) ([EMAIL PROTECTED]) (gcc version 4.0.3 20060212 (prerelease) (Debian 4.0.2-9)) #1 SMP Mon Mar 6 13:51:42 UTC 2006 Booting GENERIC on Rawhide variation Dodge using machine vector Rawhide from SRM Major Options: SMP MAGIC_SYSRQ Command line: ro root=/dev/md0 root=/dev/sdb3 console=ttyS1,9600 memcluster 0, usage 1, start0, end 256 memcluster 1, usage 0, start 256, end 262139 memcluster 2, usage 1, start 262139, end 262144 freeing pages 256:2048 freeing pages 2965:262139 reserving pages 2965:2969 Initial ramdisk at: 0xfc007f6fe000 (7560874 bytes) 4096K Bcache detected; load hit latency 31 cycles, load miss latency 122 cycles SMP: 2 CPUs probed -- cpu_present_mask = 3 Built 1 zonelists Kernel command line: ro root=/dev/md0 root=/dev/sdb3 console=ttyS1,9600 mcpcia_init_hoses: found 2 hoses PID hash table entries: 4096 (order: 12, 131072 bytes) HWRPB cycle frequency bogus. Estimated 532810909 Hz Using epoch = 2000 Turning on RTC interrupts. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 9, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 8, 2097152 bytes) Memory: 2047424k/2097112k available (2026k kernel code, 46936k reserved, 673k data, 432k init) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 SMP starting up secondaries. Brought up 2 CPUs SMP: Total of 2 processors activated (2294.21 BogoMIPS). checking if image is initramfs... it is Freeing initrd memory: 7383k freed NET: Registered protocol family 16 EISA bus registered MCPCIA machine check: vector=0x660 pc=0xfc0001013480 code=0x202 pci: enabling save/restore of SRM state machine check type: unknown pc = [fc0001013480] ra = [fc0001013494] ps = Not tainted pc is at cpu_idle+0x28/0x48 ra is at cpu_idle+0x3c/0x48 v0 = t0 = 0010 t1 = 0001 t2 = fc00014ff180 t3 = 000ee66dab0905d2 t4 = t5 = t6 = t7 = fc00012f8000 a0 = 0003 a1 = fc00012f8048 a2 = a3 = 0002 a4 = fc007e0dfbd8 a5 = t8 = t9 = 98737af5 t10= t11= fc007fe33418 pv = fc000102dae0 at = MCPCIA machine check: vector=0x660 pc=0xfc000103c9cc code=0x202 machine check type: unknown pc = [fc000103c9cc] ra = [fc000103cad0] ps = Not tainted pc is at __do_softirq+0x78/0x124 ra is at do_softirq+0x58/0x70 v0 = 0007 t0 = fc00015a61c0 t1 = fc00015b6c00 t2 = 0100 t3 = fc00015b1d28 t4 = 0083 t5 = 0003 t6 = 007d t7 = fc00012f8000 a0 = a1 = 0040 a2 = 0002 a3 = a4 = fc00012fba8c a5 = 0001 t8 = t9 = fc000102ed10 t10= 4000 t11= 0080 pv = fc000103cbe8 at = gp = fc00015a7000 sp = fc00012fbaa8 paltmp[0-1] =7 fc00015a61c0 paltmp[2-3] = fc00010113d0 4400 paltmp[4-5] = fc00015b1d28 83 paltmp[6-7] =3 fc0001011350 paltmp[8-9] = 1f1e171515020100 fc0001011630 paltmp[10-11] = fc000103c9cc fc0001011190 paltmp[12-13] = fc0001011210 6e80 paltmp[14-15] =0 11 paltmp[16-17] = 20306610 paltmp[18-19] =0 fc00012fbc00 paltmp[20-21] = 100 fc0001011290 paltmp[22-23] = fc00015a7000 12f8000 shadow[0-1] =00 shadow[2-3] =00 shadow[4-5] = 4b360 shadow[6-7] =00 Addr of excepting instruction = fc000103c9cc Summary of arithmetic traps=0 Exception mask =0 Base address for PALcode =14000 Interrupt Status Reg = 20 CURRENT SETUP OF EV5 IBOX = c16402 I-CACHE Reg Tag parity error =0 D-CACHE error Reg =0
Processed: tagging 402787
Processing commands for [EMAIL PROTECTED]: tags 402787 + pending Bug#402787: linux-image-2.6.18-3-686: cciss - cannot access to disks on MSA20 enclosure There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403790: linux-image-2.6.18-vserver-k7: Kernel assert on vserver stop
Package: linux-image-2.6.18-3-vserver-k7 Version: 2.6.18-8 Severity: normal When I run vserver server stop vserver stops all services and after unmounting non-root fs it says: === Dec 19 22:10:39 vice kernel: BUG: unable to handle kernel paging request at virtual address 0001af10 Dec 19 22:10:39 vice kernel: printing eip: Dec 19 22:10:39 vice kernel: 0001af10 Dec 19 22:10:39 vice kernel: *pde = Dec 19 22:10:39 vice kernel: Oops: [#1] Dec 19 22:10:40 vice kernel: SMP Dec 19 22:10:40 vice kernel: Modules linked in: isofs nls_koi8_r nls_cp866 vfat fat nvidia ipv6 button ac battery iptable_filter iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables asb100 hwmon_vid eeprom fuse snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq tuner snd_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss saa7134 snd_pcm video_buf compat_ioctl32 ir_kbd_i2c parport_pc parport i2c_viapro snd_seq_device snd_timer snd_page_alloc snd_util_mem floppy i2c_core via_ircc pcspkr ir_common rtc snd_hwdep irda psmouse serio_raw crc_ccitt videodev v4l1_compat v4l2_common snd via_agp agpgart soundcore shpchp pci_hotplug emu10k1_gp gameport tsdev evdev reiserfs usbhid dm_mirror dm_snapshot dm_mod usb_storage raid1 md_mod ide_generic ide_cd cdrom ide_disk sd_mod generic ehci_hcd uhci_hcd sata_promise via82cxxx ide_core usbcore libata scsi_mod b44 mii thermal processor fan Dec 19 22:10:40 vice kernel: CPU:0 Dec 19 22:10:40 vice kernel: EIP:0060:[0001af10]Tainted: P VLI Dec 19 22:10:40 vice kernel: EFLAGS: 00010087 (2.6.18-3-vserver-k7 #1) Dec 19 22:10:40 vice kernel: EIP is at 0x1af10 Dec 19 22:10:40 vice kernel: eax: d07f23e0 ebx: d07f23e0 ecx: edx: 0001 Dec 19 22:10:40 vice kernel: esi: 0001bda3 edi: 0001 ebp: f5caff48 esp: f5caff28 Dec 19 22:10:40 vice kernel: ds: 007b es: 007b ss: 0068 Dec 19 22:10:40 vice kernel: Process rc (pid: 29218[#49152], ti=f5cae000 task=e12d2bb0 task.ti=f5cae000) Dec 19 22:10:40 vice kernel: Stack: c011623b 0001 f6445a60 0509 f6445a60 0001 Dec 19 22:10:40 vice kernel: f5caff6c c0116682 0001 0292 f6445000 f658d220 Dec 19 22:10:40 vice kernel: 0010 c18e15b0 c0131ef6 f5caff90 e12d2bb0 c01207f0 Dec 19 22:10:40 vice kernel: Call Trace: Dec 19 22:10:40 vice kernel: [c011623b] __wake_up_common+0x2f/0x53 Dec 19 22:10:40 vice kernel: [c0116682] __wake_up+0x2a/0x3d Dec 19 22:10:40 vice kernel: [c0131ef6] unhash_vx_info+0xa9/0xad Dec 19 22:10:40 vice kernel: [c01207f0] do_exit+0x751/0x791 Dec 19 22:10:40 vice kernel: [c01208a5] sys_exit_group+0x0/0xd Dec 19 22:10:40 vice kernel: [c0102c57] syscall_call+0x7/0xb Dec 19 22:10:40 vice kernel: Code: Bad EIP value. Dec 19 22:10:40 vice kernel: EIP: [0001af10] 0x1af10 SS:ESP 0068:f5caff28 Dec 19 22:10:40 vice kernel: 1Fixing recursive fault but reboot is needed! === -- System Information: Debian Release: 4.0 APT prefers testing-proposed-updates APT policy: (720, 'testing-proposed-updates'), (720, 'testing'), (670, 'proposed-updates'), (670, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-vserver-k7 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages linux-image-2.6.18-3-vserver-k7 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85c tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-vserver-k7 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i ii util-vserver 0.30.211-6 user-space tools for Linux-VServer -- debconf information: linux-image-2.6.18-3-vserver-k7/postinst/old-system-map-link-2.6.18-3-vserver-k7: true shared/kernel-image/really-run-bootloader: true * linux-image-2.6.18-3-vserver-k7/preinst/lilo-initrd-2.6.18-3-vserver-k7: false linux-image-2.6.18-3-vserver-k7/preinst/failed-to-move-modules-2.6.18-3-vserver-k7: linux-image-2.6.18-3-vserver-k7/postinst/depmod-error-initrd-2.6.18-3-vserver-k7: false linux-image-2.6.18-3-vserver-k7/preinst/abort-overwrite-2.6.18-3-vserver-k7: linux-image-2.6.18-3-vserver-k7/preinst/overwriting-modules-2.6.18-3-vserver-k7: true linux-image-2.6.18-3-vserver-k7/preinst/abort-install-2.6.18-3-vserver-k7: linux-image-2.6.18-3-vserver-k7/preinst/bootloader-initrd-2.6.18-3-vserver-k7: true linux-image-2.6.18-3-vserver-k7/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-vserver-k7/prerm/would-invalidate-boot-loader-2.6.18-3-vserver-k7: true
Bug#330664: feed back: logs of crashing SMP kernel with QLA1040
* DEMAINE Benoit-Pierre wrote: Could not allocate 16 bytes percpu data 2.6.18-2 and newer include a workaround for this problem. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401384: fixed in mkvmlinuz 28
On Tue, Dec 19, 2006 at 05:17:45PM +, Colin Watson wrote: found 401384 29 thanks On Fri, Dec 15, 2006 at 11:17:03PM +, Sven Luther wrote: mkvmlinuz (28) unstable; urgency=low . * Added support for 2.6.19 kernels. * Added portuguese translation. (Closes: #401384) pt.po doesn't actually appear to be in the tarball (I'm looking at mkvmlinuz_29.tar.gz); did you maybe forget to 'svn add' it? Possibly, damn, i will investigate and make a new upload. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
* maximilian attems [EMAIL PROTECTED] [2006-12-19 20:30]: why not wait for the fix and backport it?! Well, have you seen the discussion on lkml in which people are basically tapping in the dark? I hope there'll be a clean fix in a few days but... -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 11:25:22PM +0100, Martin Michlmayr wrote: * maximilian attems [EMAIL PROTECTED] [2006-12-19 20:30]: why not wait for the fix and backport it?! Well, have you seen the discussion on lkml in which people are basically tapping in the dark? I hope there'll be a clean fix in a few days but... -- Martin Michlmayr http://www.cyrius.com/ yes there are 2 working hacks around, so the final should come up. but we shouldn't mould our hands to quickly with the first shot. -- maks christmas with dj dsl and mieze medusa - http://www.cabaretrenz.org/programm+M5c858bac7ae.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403692: linux-source-2.6.18: postinst hook script error
On Mon, Dec 18, 2006 at 08:09:40PM -0500, Brent S. Elmer, Ph.D. wrote: The provided postinst hook script [/usr/sbim/update-grub] could not be run. There is most likely a typo in your /etc/kernel-img.conf -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 05:08:24PM +0100, Martin Michlmayr wrote: 10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario ref 858-0 FSG internal testing showed that Fedora Core 5's 2.6.18 kernel does not fail in the same way. I believe I've traced it to a backported change from 2.6.19 development. The specific commit touching msync() is 204ec841fbea3e5138168edbc3a76d46747cc987 in git; it relies on several commits immediately preceding it. I've built Linus's tree on amd64, and it passes the test. I have not, however, built a 2.6.18 kernel with this patch and tested it, though it's the only patch in the Fedora kernel which touches the msync() code. So it seems that the patches needed for msync() conformance we applied from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current discussion on this on lkml. From what I understand it, plain 2.6.18 is not LSB 3.1 conform and you need some fixes which are associated with filesystem corruption. While Andrew, Linus and co are currently trying to come up with a patch, I think it might be better for us to simply back out these patches. What doe it take to get an exception for this LSB test? Surely the reasons cited above (fails with 2.6.18, a fairly current kernel and the patches to fix it are associated with fs corruption) are pretty good arguments for an exception... Reverting this is an ABI change which may be installer-affecting (I don't know if it is, but unlike most of the other pressing ABI changes this one would apply to the kernels used by the installer). If we think the fix may be available soon, I think we're better off pushing forward rather than reverting. If the decision *is* made to revert, release-wise it's best if the kernel team can bundle up any final ABI changes they want to make for etch at the same time so that we can get it done with and get d-i RC2 out. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403692: linux-source-2.6.18: postinst hook script error
Yes! I changed sbim to sbin and the kernel installed. So, what package does kernel-img.conf come with? That is the package that has the bug. Thanks! On Tue, 2006-12-19 at 15:47 -0700, dann frazier wrote: On Mon, Dec 18, 2006 at 08:09:40PM -0500, Brent S. Elmer, Ph.D. wrote: The provided postinst hook script [/usr/sbim/update-grub] could not be run. There is most likely a typo in your /etc/kernel-img.conf -- Brent S. Elmer, Ph.D. [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330664: feed back: logs of crashing SMP kernel with QLA1040
On Tue, Dec 19, 2006 at 08:28:12PM +0100, DEMAINE Benoit-Pierre wrote: On remote, I ran: cat /dev/ttyS1 a24_0_5 cat a24_0_5 | tr -d \000\007 |sed s_^$'\x20'\$_REMOVETHISLINE_g |sed s_^\$_REMOVETHISLINE_g | grep -v REMOVETHISLINE |uniq a24_0_5.txt and I ll past below the second file; otherwise, you d have pages or blank lines. The system is Debian on Alpha EV56, AS4100, with one or more QLA1040 in; the ramdisk will thus load QLA12xx driver, and fail if the kernel is SMP, suceed if no SMP support. Truncated the end, pages of missing line number, maybe bad interraction of console on serial with the prompt. *** BEGIN Linux version 2.6.15-1-alpha-smp (Debian 2.6.15-8) ([EMAIL PROTECTED]) can you please try current 2.6.18 that is the etch release kernel. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398948: linux-2.6: I can confirm that intelfb is not working
Package: linux-2.6 Version: 2.6.18+5 Followup-For: Bug #398948 Hi! I can confirm that the module intelfb isn't working. Trying to load it I get intelfb: cannot acquire agp It's reproducible with latest Debian's Kernel and with an own compiled 2.6.19 Kernel + beyound patch [1] (so it seems that the problem is still present on more recent versions of the Kernel). I am attaching the outputs of dmesg, lspci -vv and lsmod. Thank you very much! Best regards, Nelson [1] http://iphitus.loudas.com/beyond.html -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Linux version 2.6.18-3-686 (Debian 2.6.18-8) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Sun Dec 10 19:37:06 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 0010 - 1f6d3400 (usable) BIOS-e820: 1f6d3400 - 2000 (reserved) BIOS-e820: f000 - f4007000 (reserved) BIOS-e820: f4008000 - f400c000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed2 - feda (reserved) BIOS-e820: fee0 - fee1 (reserved) BIOS-e820: ffb0 - 0001 (reserved) 0MB HIGHMEM available. 502MB LOWMEM available. On node 0 totalpages: 128723 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 124627 pages, LIFO batch:31 DMI 2.4 present. ACPI: RSDP (v000 DELL ) @ 0x000fc1f0 ACPI: RSDT (v001 DELLM07 0x27d60c0b ASL 0x0061) @ 0x1f6d3a0f ACPI: FADT (v001 DELLM07 0x27d60c0b ASL 0x0061) @ 0x1f6d4800 ACPI: HPET (v001 DELLM07 0x0001 ASL 0x0061) @ 0x1f6d4f00 ACPI: MADT (v001 DELLM07 0x27d60c0b ASL 0x0047) @ 0x1f6d5000 ACPI: MCFG (v016 DELLM07 0x27d60c0b ASL 0x0061) @ 0x1f6d4fc0 ACPI: SLIC (v001 DELLM07 0x27d60c0b ASL 0x0061) @ 0x1f6d509c ACPI: SSDT (v001 PmRefCpuPm 0x3000 INTL 0x20050624) @ 0x1f6d3a4b ACPI: DSDT (v001 INT430 SYSFexxx 0x1001 INTL 0x20050624) @ 0x ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:14 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 6:14 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs ACPI: HPET id: 0x8086a201 base: 0xfed0 Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:d000) Detected 1662.599 MHz processor. Built 1 zonelists. Total pages: 128723 Kernel command line: root=/dev/sda5 ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 502968k/514892k available (1543k kernel code, 11268k reserved, 574k data, 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. hpet0: at MMIO 0xfed0 (virtual 0xe000), IRQs 2, 8, 0 hpet0: 3 64-bit timers, 14318180 Hz Using HPET for base-timer Calibrating delay using timer specific routine.. 3328.69 BogoMIPS (lpj=6657384) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfe9fbff 0010 c189 CPU: After vendor identify, caps: bfe9fbff 0010 c189 monitor/mwait feature present. using mwait in idle threads. CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 CPU: After all inits, caps: bfe9fbff 0010 0940 c189 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code ACPI: Core
