Bug#273569: kernel-image-2.6.8: CONFIG_PCI_MSI should NOT be enabled!
Package: kernel-image-2.6.8-1-k7 Version: 2.6.8-3 Severity: serious Between 2.6.7 and 2.6.8 the CONFIG_PCI_MSI config option was enabled it was previously called CONFIG_PCI_USE_VECTOR for reference. This is normally defaulted off and suggests to be turned off as well. It causes some systems including my laptop to no longer work at all under linux since it changes how interrupt routing works. Also on lkml there are threads suggesting not all drivers even work properly with MSI. This bug also affects both pure64 (amd64) and Ubuntu linux kernels, since both are derived from the official Debian ones. Chris -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8.1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Bug#273527: possible deadlock in kmem_alloc (mode 0x50)
Package: kernel-image-2.6.8-1-686 Version: 2.6.8-3 My gateway/fileserver machine running Debian Unstable was unresponsive this morning. When I plugged in a monitor and keyboard, I saw: possible deadlock in kmem_alloc (mode 0x50) on the screen. I was unable to get the machine to reboot, so I hit the reset button. After a reboot, I looked at /var/log/syslog and found thousands of messages (see below). I'm not a kernel hacker by any means, so I'm submitting this in hopes that someone else can make sense of it and forward it upstream, if appropriate. Just briefly, the machine is a Pentium III 1.0 Ghz, ASUS TUSI-M motherboard, 384MB SDRAM. I have XFS on /dev/md0 mounted at /raid is a RAID1 array over two parallel ATA drives (/dev/hde and /dev/hdg); Debian is installed on an EXT3 partition on /dev/hda, also a parallel ATA drive. Here is the first message in syslog. I have the entire relevant portion of syslog saved (size is ~690k), as well as the machine's dmesg, if necessary. Please let me know if I can help in any other way. kernel: kswapd0: page allocation failure. order:4, mode:0x50 kernel: [__alloc_pages+760/880] __alloc_pages+0x2f8/0x370 kernel: [__get_free_pages+37/64] __get_free_pages+0x25/0x40 kernel: [kmem_getpages+34/192] kmem_getpages+0x22/0xc0 kernel: [cache_grow+186/384] cache_grow+0xba/0x180 kernel: [cache_alloc_refill+362/544] cache_alloc_refill+0x16a/0x220 kernel: [__kmalloc+116/128] __kmalloc+0x74/0x80 kernel: [__crc_dq_data_lock+456637/3868974] kmem_alloc+0x59/0xc0 [xfs] kernel: [__crc_dq_data_lock+456927/3868974] kmem_realloc+0x2b/0x80 [xfs] kernel: [__crc_dq_data_lock+315547/3868974] xfs_iext_realloc+0xf7/0x150 [xfs] kernel: [__crc_dq_data_lock+136029/3868974] xfs_bmap_insert_exlist +0x39/0x90 [xfs] kernel: [__crc_dq_data_lock+111221/3868974] xfs_bmap_add_extent_delay_real+0x7b1/0x16b0 [xfs] kernel: [__crc_dq_data_lock+470791/3868974] _pagebuf_ioapply +0x243/0x2f0 [xfs] kernel: [scheduler_tick+364/1104] scheduler_tick+0x16c/0x450 kernel: [__crc_dq_data_lock+108936/3868974] xfs_bmap_add_extent +0x3a4/0x4e0 [xfs] kernel: [__crc_dq_data_lock+144882/3868974] xfs_bmapi+0x73e/0x1610 [xfs] kernel: [__crc_dq_data_lock+468880/3868974] pagebuf_rele+0x2c/0x120 [xfs] kernel: [__crc_dq_data_lock+174467/3868974] xfs_bmbt_get_state +0x2f/0x40 [xfs] kernel: [__crc_dq_data_lock+137200/3868974] xfs_bmap_do_search_extents +0xbc/0x3f0 [xfs] kernel: [__crc_dq_data_lock+341475/3868974] xfs_log_reserve+0xbf/0xd0 [xfs] kernel: [__crc_dq_data_lock+330222/3868974] xfs_iomap_write_allocate +0x2aa/0x4d0 [xfs] kernel: [__crc_dq_data_lock+326131/3868974] xfs_iomap+0x3ff/0x560 [xfs] kernel: [__crc_dq_data_lock+457788/3868974] xfs_map_blocks+0x58/0xa0 [xfs] kernel: [__crc_dq_data_lock+462167/3868974] xfs_page_state_convert +0x513/0x680 [xfs] kernel: [free_buffer_head+57/112] free_buffer_head+0x39/0x70 kernel: [__crc_dq_data_lock+464592/3868974] linvfs_release_page +0xbc/0xe0 [xfs] kernel: [try_to_release_page+81/128] try_to_release_page+0x51/0x80 kernel: [shrink_list+998/1248] shrink_list+0x3e6/0x4e0 kernel: [shrink_cache+335/832] shrink_cache+0x14f/0x340 kernel: [shrink_slab+120/416] shrink_slab+0x78/0x1a0 kernel: [shrink_zone+170/224] shrink_zone+0xaa/0xe0 kernel: [balance_pgdat+469/576] balance_pgdat+0x1d5/0x240 kernel: [kswapd+210/240] kswapd+0xd2/0xf0 kernel: [autoremove_wake_function+0/96] autoremove_wake_function +0x0/0x60 kernel: [ret_from_fork+6/20] ret_from_fork+0x6/0x14 kernel: [autoremove_wake_function+0/96] autoremove_wake_function +0x0/0x60 kernel: [kswapd+0/240] kswapd+0x0/0xf0 kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18 -- [EMAIL PROTECTED] Administrator, tgpsolutions http://www.tgpsolutions.com signature.asc Description: This is a digitally signed message part
Bug#273524: kernel-image-2.6.8-1-386: Panics when mounting initrd.
Package: kernel-image-2.6.8-1-386 Version: 2.6.8-3 Severity: important Fails to boot. Panics when mounting initrd (cramfs). Worked fine with kernels up to 2.6.8-2. Reinstalled 2.6.8-2 and it again works fine. This machine is fairly old, has an AMD CPU upgrade module, is a desktop machine not a laptop. The info from /proc is: [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 8 model name : AMD-K6(tm) 3D processor stepping: 12 cpu MHz : 397.948 cache size : 64 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr bogomips: 786.43 It has been working fine with stock Debian kernels up until now. When it had "woody" on it, I used a K6 kernel, which seems to have gone by the wayside in "sarge", but as I said -1-386 was working with recent 2.6.7 and 2.6.8 kernels. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.8-1-386 Locale: LANG=C, LC_CTYPE=C Versions of packages kernel-image-2.6.8-1-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.74 tools to create initrd image for p ii module-init-tools 3.1-pre5-7 tools for managing Linux kernel mo -- no debconf information
Re: tcp window problem in 2.6.8.1
On Sun, Sep 26, 2004 at 03:37:18PM +0200, Norbert Tretkowski wrote: > * Jaakko Niemi wrote: > [...] > > Has anyone looked at this issue? I could not find anything from list > > archives or from bts with quick search. > > A few days ago, Christoph mention that this has been fixed in svn > already. I wouldn't call this a fix. It's a really bad hack to work around broken non-linux systems..
Re: tcp window problem in 2.6.8.1
On Sun, 26 Sep 2004, Jaakko Niemi wrote: > Has anyone looked at this issue? I could not find anything > from list archives or from bts with quick search. ok, quick enough search to miss all relevan bits, namely: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272983 Sorry for the noise. --j
Re: tcp window problem in 2.6.8.1
* Jaakko Niemi wrote: [...] > Has anyone looked at this issue? I could not find anything from list > archives or from bts with quick search. A few days ago, Christoph mention that this has been fixed in svn already. http://lists.debian.org/debian-kernel/2004/09/msg00658.html Norbert
tcp window problem in 2.6.8.1
Hello, Tcp window scaling behaviour was changed in 2.6.8, and this causes problems with some sites. Details are in: http://lwn.net/Articles/92727/ These changes seem to have been reverted, or at least reworked in 2.6.9-rc. This is bound to become faq if we release sarge with 2.6.8 packages as they are now. While the workaround is rather simple, it might make sense to fetch the patch from 2.6.9-rc. Has anyone looked at this issue? I could not find anything from list archives or from bts with quick search. --j
Bug#273478: Warnings introduced 2.6.8-2 -> 2.6.8-3
Package: kernel-image-2.6.8-1-686 Version: 2.6.8-3 Severity: normal New, nasty looking warnings during hotplug loading: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 ACPI-1133: *** Error: Method execution failed [\_SB_.LNKA._STA] (Node c7b022e0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKA._STA] (Node c7b022e0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKB._STA] (Node c7b021e0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKB._STA] (Node c7b021e0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKC._STA] (Node c7b02fc0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKC._STA] (Node c7b02fc0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKD._STA] (Node c7b02ec0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKD._STA] (Node c7b02ec0), AE_AML_NO_RETURN_VALUE pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 ACPI-1133: *** Error: Method execution failed [\_SB_.LNKA._STA] (Node c7b022e0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKA._STA] (Node c7b022e0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKB._STA] (Node c7b021e0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKB._STA] (Node c7b021e0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKC._STA] (Node c7b02fc0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKC._STA] (Node c7b02fc0), AE_AML_NO_RETURN_VALUE ACPI-1133: *** Error: Method execution failed [\_SB_.LNKD._STA] (Node c7b02ec0), AE_AML_NO_RETURN_VALUE ACPI-0154: *** Error: Method execution failed [\_SB_.LNKD._STA] (Node c7b02ec0), AE_AML_NO_RETURN_VALUE shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5 shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5 These modules also failed in 2.6.8-2, but without the same verbosit. Should this be a hotplug bug for trying to load these? puck% lspci :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) :00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03) :00:0a.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) :00:0a.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) :00:0d.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator :00:0d.1 Communication controller: ESS Technology ES1983S Maestro-3i PCI Modem Accelerator :01:00.0 VGA compatible controller: Silicon Motion, Inc. SM710 LynxEM (rev a3) -- Ian Gulliver Penguin Hosting "Failure is not an option; it comes bundled with your Microsoft products." signature.asc Description: Digital signature binMFr68eh8SE.bin Description: application/postage-hashcash
Bug#273474: APM broken in image-2.6.8-1 version 2.6.8-3, worked in 2.6.8-1
Package: kernel-image-2.6.8-1-686 Version: 2.6.8-3 I have been using version 2.6.8-1 just fine on a Dell Latitude C400 notebook and upgraded to the recent version 2.6.8-3. After upgrading, a) the built-in, APM-related function keys (e.g for triggering a BIOS-controlled suspend or for entering the BIOS) stopped working. b) a user-initiated suspend (apm --suspend) leads to a suspended system, but it won't wake up again. After having pressed the power button on a suspended system, a few LEDs blink as usual, but the system immediately goes dead/sleeping/... again. After downgrading back to 2.6.8-1 (the deb was still on my disk), everything is working again. I'm running a mixed stable/testing system, apmd and libapm1 are from testing (3.2.2-2). Cheers, Marcus -- Marcus C. Gottwald · <[EMAIL PROTECTED]> · http://cheers.de
Bug#273278: kernel-image-2.4.27-1-k7: No PCMCIA inside
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I understand why you put them out, but you should warn the user you did so, either by a message in apt, or by sending a mail to root ... because the name of that module do not sound obvious to me ... Horms wrote: | On Sat, Sep 25, 2004 at 12:48:14AM +0100, DEMAINE Benoit-Pierre wrote: | |>Package: kernel-image-2.4.27-1-k7 |>Version: 2.4.27-2 |>Severity: important |> |> |>Impossible to find any PCMCIA module in /lib/modules/2.4.27-1-k7 tree; |>thus I can not use any PCMCIA device on my laptop. |> |>$ ls /lib/modules/2.4.27-1-k7/ |>initrd modules.generic_string modules.parportmap modules.usbmap |>kernel modules.ieee1394map modules.pcimap |> |>[EMAIL PROTECTED]:/lib/modules/2.4.27-1-k7$ find | grep pcmcia |>[EMAIL PROTECTED]:/lib/modules/2.4.27-1-k7$ | | | Please install the pcmcia modules package, | kernel-pcmcia-modules-2.4.27-1-k7 | - -- DEMAINE Benoît-Pierre http:/www.demaine.info/ \_o< apt-get remove ispell >o_/ There're 10 types of people: those who can count in binary and those who can't -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBVWFdGWSTLbOSw8IRAomIAKClIcHiEUvk7RVvZ3HZ/sX714+bKwCgjrQH eHmWjrRI8m9NQwmtJuorlcs= =J6nM -END PGP SIGNATURE-
Bug#268352: 2.6.* radeonfb regression
On Mon, Sep 13, 2004 at 11:44:55AM +0200, Sven Luther wrote: > On Mon, Sep 13, 2004 at 10:44:32AM +0200, Francesco P. Lovergine wrote: > > On Sun, Sep 12, 2004 at 09:00:19AM +0200, Sven Luther wrote: > > > > > > > I'm having the same problem on a HP Pavilion zt3020EA, which has an ATI > > > > Radeon 9000 chipset. Native res is 1280x800. Again blank screen with > > > > cursor moving on it, and all working fine in 2.4 or X. The problem > > > > apparently > > > > is the same so I'm sending a followup for that. > > > > > > Mmm, Can you clarify if it works fine in 1280x800 mode or not ? I have > > > some > > > doubts about the wisdom of using an LCD with bigger than native > > > resolution. > > > > > > > That's the native resolution and looks very good. This is one of those > > new displays in 16/9 ratio, used for video playing. As well as 1400x1050 > > is the native resolution for the other box which has a SXVGA unit. > > All resolutions are stolen from those detected and used under 2.4. > > The old kernel starts directly in the high resolution mode. > > BTW, I'm using the same resoltion under X which also appears as the best > > one for font and textures rendering. > > Ok, so you have two laptops, one with 1400x1050 native resolution and the > other with 1280x800 native resolution, exact ? > Right, and I know personally at least other 2-3 people with the same problem, all with different Compaq/HP laptops. > In both case, running the fbdev in native resolution worked for 2.4 radeonfb, > but not for 2.6 radeonfb, and in both case X is working fine. > Right too. > Furthermore, your laptops displays are not-DDC capable, and thus new_radeonfb > is doing strange things with monitor timings, and is failing to setup your > native panel mode. > Definitively yes. > Benh, any insight on this ? > I hope so :) Using vesafb with ordinary (non native) resolutions is not so great... -- Francesco P. Lovergine
Bug#268208: Possible solution for smp problem
I've been having the same problem both with 2.6.7 and 2.6.8 images (always with 686 smp). The problem is directly related to acpi and I was using the parameter "acpi=off" at boot time to solve it. Today, I recompiled the kernel, changing as follows: --- /boot/config-2.6.8-1-686-smp2004-08-28 13:48:08.0 -0300 +++ .config 2004-09-26 02:25:08.0 -0300 @@ -141,14 +141,14 @@ CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y -CONFIG_ACPI_AC=m -CONFIG_ACPI_BATTERY=m -CONFIG_ACPI_BUTTON=m -CONFIG_ACPI_FAN=m -CONFIG_ACPI_PROCESSOR=m -CONFIG_ACPI_THERMAL=m -CONFIG_ACPI_ASUS=m -CONFIG_ACPI_TOSHIBA=m +CONFIG_ACPI_AC=y +CONFIG_ACPI_BATTERY=y +CONFIG_ACPI_BUTTON=y +CONFIG_ACPI_FAN=y +CONFIG_ACPI_PROCESSOR=y +CONFIG_ACPI_THERMAL=y +# CONFIG_ACPI_ASUS is not set +# CONFIG_ACPI_TOSHIBA is not set # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y This solved the problem. The rest of the config file is exactly the same, but by changing this, I could boot normally without the "acpi=off" parameter. I'm not sure if it's all or just some of the options that made the real difference. This is being tested in an Intel Pentium IV, with Intel Motherboard D865GBF. I'm attaching my cat /proc/cpuinfo and my lspci just in case you want to know the exact details of the box. I can provide extra information if needed. I hope this helps in fixing the bug. -- Bezitos, Maggie. :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01) :01:04.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) :01:04.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) :01:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 01) processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping: 3 cpu MHz : 2794.468 cache size : 1024 KB physical id : 0 siblings: 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni monitor ds_cpl cid bogomips: 5537.79 processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping: 3 cpu MHz : 2794.468 cache size : 1024 KB physical id : 0 siblings: 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni monitor ds_cpl cid bogomips: 5570.56
