Bug#674907: reassign 674907 to src:linux-2.6, forcibly merging 599161 674907
On Mon, Oct 01, 2012 at 04:06:27PM +0200, Bastian Blank wrote: reassign 674907 src:linux-2.6 Why was this reassigned to the linux kernel? I explicitely stated (twice) that machines not running Xen are *not* affected, so this is specifically a Xen issue. I do not want to get into an edit war here, if there is proper justification I don't mind having it assigned to anything... But I don't think the bug is in the linux kernel as much as the Xen extensions somehow. A. -- Legislation should outlaw an advertiser's attempts to use its economic relationships with a media enterprise to influence the enterprise not to print or broadcast content that it would otherwise choose to present . . . . There is little reason to allow this use of economic power to censor others' speech and to block the public's access to information or viewpoints. - C. Edwin Baker signature.asc Description: Digital signature
Bug#597664: linux-image-2.6.32-5-686: Xorg crashes with radeon kernel messages
Package: linux-2.6 Version: 2.6.32-23 Severity: important Today I had a very special issue with my workstation. The display would start but freeze. Even though in the back things are still happening, the display isn't updated and the only way out is to go to TTY1 (control-alt-F1) where the console gets flooded with messages like this: Sep 21 17:59:04 lenny kernel: [ 102.324219] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). Sep 21 17:59:04 lenny kernel: [ 102.354242] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! Sep 21 17:59:04 lenny kernel: [ 103.124761] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). Sep 21 17:59:04 lenny kernel: [ 103.155110] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! [...] (The message loops through IB(0) to IB(15).) Stopping gdm (invoke-rc.d gdm stop) stops the warning, but restarting gdm doesn't fix the display (in fact it doesn't affect the display at all) and the messages come back. Oddly enough, sometimes, things just work without an hitch: it seems that the issue is intermittent. The problem mostly happens when I logout and log back in quickly. I have recently upgraded sid twice, once on august 11th (when xorg and linux-image were upgraded) and once today (to try to fix the issue). However, things were working well *after* the august 11th upgrade as far as I remember, so I am unsure when the regression got in. I first noticed the behaviour today *before* the upgrade. The only other change on this machine is that I switch from an old 15 CRT to a new Aceer X193w LCD monitor. I also tried to fiddle with subpixel rendering and anti-aliasing in the fontconfig-config package yesterday, although I fail to see how this would be the cause of this issue. I have tried numerous workarounds I could find on the internet (references below): [1] disables modesetting, by editin /etc/modprobe.d/radeon-kms.conf to: options radeon modeset=0 no luck: display still freezes, and instead the load goes up and up and I can't kill X at all. [2] sets the AGP mode, in the same file. no luck either there. [3] suggests upgrading to a later version of the kernel, which here just crashes the whole machine: total freeze, no display, no keyboard, only a cold reset brings back the machine. [4], [5] and [6] also point to similar workarounds which either do not work or do not work for me. Most end up pointing to the kernel as the culprit. Indeed, [7] is the bug in the kernel itself, which is announced as resolved, but I am not sure if this is in experimental yet. Based on the above evidence from third parties and the fact that the error comes from the kernel (and not X), I am reporting this against the kernel. Thanks, A. References == [1] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/586243 This points to disabling modeset as a workaround. [2] http://bugs.debian.org/585815 suggests to play with agpmode=1 [3] http://bugs.debian.org/588688 suggests upgrading to 2.6.35~rc2. I tried 2.6.35-1~experimental.3 and it crashes. [4] http://bugs.freedesktop.org/show_bug.cgi?id=26144 points to a kernel issue [5] https://bugzilla.redhat.com/show_bug.cgi?id=629427 points to the kernel and KMS, with no clear workaround or fix. [6] http://bugs.debian.org/580208 mistakenly tries to downgrade xorg [7] https://bugzilla.kernel.org/show_bug.cgi?id=15969 is the upstream, closed kernel bug, fixed on 2010-06-13. Unclear if this is 2.6.35. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-23) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-3) ) #1 SMP Sat Sep 18 02:14:45 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=d7ebb9e5-e9f1-4cc1-a7dc-9499e0640eea ro vga=791 quiet ** Not tainted ** Kernel log: [ 16.191743] [drm] radeon kernel modesetting enabled. [ 16.191878] radeon :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 16.198700] [drm] radeon: Initializing kernel modesetting. [ 16.198881] [drm] register mmio base: 0xDFEF [ 16.198886] [drm] register mmio size: 65536 [ 16.200231] [drm] GPU reset succeed (RBBM_STATUS=0x0140) [ 16.200261] [drm] Generation 1 PCI interface in multifunction mode [ 16.200266] [drm] Limiting VRAM to one aperture [ 16.200277] [drm] AGP mode requested: 1 [ 16.200285] agpgart-via :00:00.0: AGP 2.0 bridge [ 16.200313] agpgart-via :00:00.0: putting AGP V2 device into 1x mode [ 16.200382] radeon :01:00.0: putting AGP V2 device into 1x mode [ 16.200395] [drm] radeon: VRAM 128M [ 16.200400] [drm] radeon: VRAM from 0x to 0x07FF [ 16.200404] [drm] radeon: GTT 128M [ 16.200409] [drm] radeon: GTT from 0xE000 to 0xE7FF [ 16.200472] [drm] radeon: irq initialized. [ 16.200849] [drm] Detected VRAM RAM=128M, BAR=128M [ 16.200860] [drm] RAM width 128bits DDR [ 16.201053] [TTM] Zone kernel: Available graphics memory: 441458 kiB. [ 16.201059] [TTM] Zone
Bug#475055: suspend on x31 still fails sometimes
unarchive 475055 found 475055 2.6.26-10 thanks Hello, I'm still seeing this behaviour, from time to time, on my Thinkpad X31. I don't have the exact error message (I would need to take a picture for that ;) but it really looks like the one describe in this bug report and at the end of this page: http://www.thinkwiki.org/wiki/Problems_with_ACPI_suspend-to-ram I feel this issue is not resolved and should be reopened. I'm available for testing new kernels, recompile with patches, anything to get my suspend working. ;) I have tried to turn on/off/disable HPA in the BIOS, nothing works. I include a dmesg and non-verbose lspci (more available upon request). (Should I open a new bug report since this one is archived?) [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-686 (Debian 2.6.26-10) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Nov 8 19:00:26 UTC 2008 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f000 (usable) [0.00] BIOS-e820: 0009f000 - 000a (reserved) [0.00] BIOS-e820: 000dc000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1ff6 (usable) [0.00] BIOS-e820: 1ff6 - 1ff77000 (ACPI data) [0.00] BIOS-e820: 1ff77000 - 1ff79000 (ACPI NVS) [0.00] BIOS-e820: 1ff8 - 2000 (reserved) [0.00] BIOS-e820: ff80 - 0001 (reserved) [0.00] 0MB HIGHMEM available. [0.00] 511MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 130912) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] Normal 4096 - 130912 [0.00] HighMem130912 - 130912 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 130912 [0.00] On node 0 totalpages: 130912 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 991 pages used for memmap [0.00] Normal zone: 125825 pages, LIFO batch:31 [0.00] HighMem zone: 0 pages used for memmap [0.00] Movable zone: 0 pages used for memmap [0.00] DMI present. [0.00] ACPI: RSDP 000F6D70, 0024 (r2 IBM ) [0.00] ACPI: XSDT 1FF69E78, 004C (r1 IBMTP-1Q3020 LTP 0) [0.00] ACPI: FACP 1FF69F00, 00F4 (r3 IBMTP-1Q3020 IBM 1) [0.00] ACPI Warning (tbfadt-0442): Optional field Gpe1Block has zero address or length: 102C/0 [20080321] [0.00] ACPI: DSDT 1FF6A0E7, CD2A (r1 IBMTP-1Q3020 MSFT 10E) [0.00] ACPI: FACS 1FF78000, 0040 [0.00] ACPI: SSDT 1FF6A0B4, 0033 (r1 IBMTP-1Q3020 MSFT 10E) [0.00] ACPI: ECDT 1FF76E11, 0052 (r1 IBMTP-1Q3020 IBM 1) [0.00] ACPI: TCPA 1FF76E63, 0032 (r1 IBMTP-1Q3020 PTL 1) [0.00] ACPI: BOOT 1FF76FD8, 0028 (r1 IBMTP-1Q3020 LTP 1) [0.00] ACPI: PM-Timer IO Port: 0x1008 [0.00] Allocating PCI resources starting at 3000 (gap: 2000:df80) [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000dc000 [0.00] PM: Registered nosave memory: 000dc000 - 0010 [0.00] SMP: Allowing 0 CPUs, 0 hotplug CPUs [0.00] PERCPU: Allocating 37960 bytes of per cpu data [0.00] NR_CPUS: 8, nr_cpu_ids: 1 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129889 [0.00] Kernel command line: root=/dev/mapper/mumia-root ro acpi_sleep=s3_bios,s3_mode video=vesafb:invers vga=791 [0.00] Local APIC disabled by BIOS -- you can enable it with lapic [0.00] mapped APIC to b000 (0140d000) [0.00] Enabling fast FPU save and restore... done. [0.00] Enabling unmasked SIMD FPU exception support... done. [0.00] Initializing CPU#0 [0.00] PID hash table entries: 2048 (order: 11, 8192 bytes) [0.00] Extended CMOS year: 2000 [0.00] Detected 599.501 MHz processor. [0.004000] Console: colour dummy device 80x25 [0.004000] console [tty0] enabled [0.004000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.004000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.004000] Memory: 507716k/523648k available (1768k kernel code, 15416k reserved, 752k data, 244k init, 0k highmem) [0.004000] virtual kernel memory layout: [0.004000] fixmap
Bug#390040: linux-image-2.6.17-2-686: suspend to {disk, mem} fails on toshiba satellite A30
On Tue, Jan 16, 2007 at 04:07:08PM +0100, maximilian attems wrote: On Thu, 28 Sep 2006, The Anarcat wrote: Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: normal So, i got a new laptop... The linux kernel used to be real nice to me on my old thinkpad, but it got stolen so now i'm with a Toshiba Satellite A30. I can't either suspend to disk or ram. i use echo disk or echo mem /sys/power/state to test. how is linux image 2.6.18 doing? not much better. == echo mem /sys/power/state == This just shutsdown the machine spontaneously. I briefly see what looks like a progress bar saying freeing memory but this lasts less than a second so i could be wrong. Is this expected? Seems to me power shouldn't be completely turned off like this... When I boot the machine again, it comes back up, without going through the BIOS (apparently), ends up in a state where caps and num leds are on, nothing is responding and the LCD screen is empty (but active). The fan is turning like crazy so I guess it's doing *something*. I must hold onto the power button to make it turn off. Next power up leads to nothing, i need to hold the power button again to get to the bios and the regular bootup procedure. At this point, i'm stuck after the kernel and the initrd get loaded by grub: it's frozen again. This looks like when this laptop is overheating, btw. Doing a third reboot gets me into a useable session. Also note that i'm running those tests with GDM/X11 stopped. == echo disk /sys/power/state == Ok, so this doesn't work either... Here is what in does, without me intervening at all (this is transcribed by hand again, so bear with me). This starts by Freezing cpus ... Stopping tasks: =... Skinrking memory... done (0 pages freed) pnp: Device 00:07 disabled ACPI: PCI interrupt for device :02:04.0 disabled ACPI: PCI interrupt for device :00:1f.6 disabled ACPI: PCI interrupt for device :00:1f.5 disabled ACPI: PCI interrupt for device :00:1d.7 disabled ACPI: PCI interrupt for device :00:1d.2 disabled ACPI: PCI interrupt for device :00:1d.1 disabled ACPI: PCI interrupt for device :00:1d.0 disabled cpufreq suspend failed to assert current frequency is what timing core thinks it is swsusp: Need to copy 44455 pages swsusp: critical section/: done (44455 pages copied) Intel machine check architecture supported Intel machine check reporting enabled on CPU#0 CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled swsusp: Restoring Highmem cpufreq: resume failed to assert current frequency is what timing core thinks it is PCI: Enabling device :00:1d.0 ( - 0001) ACPI: PCI Interrupt :00:1d.0[A] - GSI 16 (level, low) - IRQ 177 PCI: Enabling device :00:1d.1 ( - 0001) ACPI: PCI Interrupt :00:1d.1[B] - GSI 19 (level, low) - IRQ 193 PCI: Enabling device :00:1d.2 ( - 0001) ACPI: PCI Interrupt :00:1d.2[C] - GSI 18 (level, low) - IRQ 201 I notice how ACPI is not reactivating all the PCI interrupts it originally disabled. I also notice the fans are going pretty fast (although not as if overheating). I also saw a: CPU0: temperature/speed normal while typig the above messages, so i guess this means something is still alive somewhere in there. Indeed, I can switch VTs, but the original echo disk /sys/power/state is just sitting there freezing the terminal. Control-c/z/\ doesn't do anything. I can't login into other vts, characters typed there do not appear on screen (whereas they do in the original console where i called echo). I can do an emergency sync (alt-a-sysreq-s). A showPc shows me: Pid: 0, comm: swapper EIP is at acpi_processor_idle... ... [c0101b52] cpu_idle+0x9f/0xb9 [c03186fd] start_kernel+0x379/0x380 showTasks seems to write a lt of stuff on screen, i guess with all processes call trace. I can umount and poweroff... I might try to hook a serial console onto this thing to copy/paste some of this stuff or do further diagnosis if you think it is useful. So, still a problem with 2.6.18, from etch. I hope this helps at all. A. signature.asc Description: Digital signature
Bug#390040: linux-image-2.6.17-2-686: suspend to {disk, mem} fails on toshiba satellite A30
With 2.6.20-rc4, the system seems to suspend to ram fine. The power led oozes on and off. When powering it back up, however, the LCD still doesn't come up. The console keyboard works, however, and I'm able to pass commands through. I'd be curious to know if there would be a hack to reset the display at this point... reboot(8) doesn't bring back the display, so, again, this is very probably a BIOS issue from Toshiba... Suspend to disk works even better: it goes through the suspend cycle and shuts down cleanly. When rebooting, my console comes back properly. Everything also seems to work properly at first sight in X11. Things are mostly the same in 2.6.19-4 so I guess I'll start using that... I didn't know about kernel-archive.buildserver.net, I'm glad you pointed out this resource to me, very interesting... So I guess the bottom line is: suspend to disk works in 2.6.19-1-686. suspend to ram works a bit better, but not quite there. That's enough for my needs, thanks!! A. PS: would this package make it to etch then? I guess that the answer is no, but asking doesn't hurt... :) signature.asc Description: Digital signature
Bug#396185: similar issues with sky2
Hi, I'm having similar problems with the sky2 driver. We've been avoiding the builtin drivers from the packaged kernels in stable for a while, but we're now using the backports (2.6.17 from backports.org), and we (unvoluntarly) have started using the sky2 module. Traffic on the NIC is usually low, so everything worked pretty well, until I had to rsync data over the wire, at which point everything went black. The NIC was still there, but traffic wasn't going through (can't ping the machine's own IP). I couldn't find error messages in the dmesg or the kernel log. I don't have the courage to upgrade to the 2.6.18 kernel since this is a production machine and I need to resolve this issue very quickly. I apologize for not having a test machine for doing this.. We're putting a new infrastructure live tomorrow and can't afford uncertainty at this point... We've reverted to using the manufacturer's driver at this point: http://www.marvell.com/drivers/driverDisplay.do?dId=153pId=36 :04:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown device 4361 (rev 18) Subsystem: Intel Corp.: Unknown device 3452 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 0x10 (64 bytes) Interrupt: pin A routed to IRQ 177 Region 0: Memory at ff72 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at a800 [size=256] Expansion ROM at ff70 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: fee0 Data: 4042 Capabilities: [e0] #10 [0011] 00: ab 11 61 43 07 01 10 00 18 00 00 02 10 00 00 00 10: 04 00 72 ff 00 00 00 00 01 a8 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 52 34 30: 00 00 70 ff 48 00 00 00 00 00 00 00 0a 01 00 00 signature.asc Description: Digital signature
Bug#390040: linux-image-2.6.17-2-686: suspend to {disk, mem} fails on toshiba satellite A30
Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: normal So, i got a new laptop... The linux kernel used to be real nice to me on my old thinkpad, but it got stolen so now i'm with a Toshiba Satellite A30. I can't either suspend to disk or ram. i use echo disk or echo mem /sys/power/state to test. When suspending to disk, i get this on the console: cpufreq: suspend failed to assert current frequency is what timing core thinks it is swsusp: Need to copy 31320 pages swsusp: critical section/: done (31320 pages copied) ... CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: thermal monitoring enabled swsusp: restoring highmem cpufreq: suspend failed to assert current frequency is what timing core thinks it is ... Those were copied by hand. The cpufreq message makes me think the problem might be related to the frequency scaling drivers. Indeed, the gnome applet tells me the CPU jumps between 1.6Ghz and 3.06Ghz when scaling, when the CPU is supposed to be a 2.50Ghz. I will try disabling frequency scaling and X11 to see if that helps. I found another report[1] of this laptop having problems with ACPI, so it's very likely a problem that's been there for a while. I have started documenting[2] the fun I'm having with Debian on this laptop. I have attached a dmidecode (because I think the problem is ACPI-related) and lspci -vv (because it's always good) and a dmesg (because more is better here). The problem happens in 2.6.16, .17 and .18 (from sid). I am available for debugging and testing this to the death. Thanks, A. [1] http://web.archive.org/web/20050205233442/tiptsoft.com/laptop/linux.html [2] http://wiki.koumbit.net/TheAnarcat/ToshibaSatelliteA30 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.80 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-4 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: *** /tmp/dmidecode # dmidecode 2.8 SMBIOS 2.31 present. 31 structures occupying 1002 bytes. Table at 0x000DF010. Handle 0x, DMI type 0, 20 bytes BIOS Information Vendor: TOSHIBA Version: V1.10 Release Date: 08/19/2003 Address: 0xE6910 Runtime Size: 104176 bytes ROM Size: 512 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported Japanese floppy for Toshiba 1.2 MB is supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported AGP is supported IEEE 1394 boot
Bug#383725: linux-image-2.6.16-2-686: 2.6.17 works
Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Followup-For: Bug #383725 I confirm that 2.6.17 is not affected by this bug. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383725: linux-image-2.6.16-2-686: cannot halt properly Thinkpad T22
Package: linux-image-2.6.16-2-686 Version: 2.6.16-17 Severity: normal Hello, I see a clear regression here after upgrading from 2.6.15 to 2.6.16. The kernel now doesn't shutdown cleanly the power on my laptop, a IBM Thinkpad T22. It used to work real nice on 2.6.15, but now, the machine just sits there after the Shutting down drives: sda (probably not the exact wording, i don't clearly remember, but it's usually the last thing on the console before the shutdown). I can safely poweroff the machine by pressing the power key for 5 seconds, but it's a bit annoying. Usually, i just suspend to disk this machine, using an ugly hack (echo disk /sys/power/state). This is also affect in that I need to poweroff the same way as a shutdown, ie. by pressing the power key. The machine resumes as normal. Available for debugging/testing with right tools/instructions... a. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-686 recommends: ii libc6-i6862.3.6-15 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.16-2-686/preinst/bootloader-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-system-map-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/failed-to-move-modules-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/overwriting-modules-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/old-dir-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-initrd-2.6.16-2-686: false linux-image-2.6.16-2-686/postinst/create-kimage-link-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/bootloader-test-error-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/removing-running-kernel-2.6.16-2-686: true linux-image-2.6.16-2-686/postinst/depmod-error-2.6.16-2-686: false linux-image-2.6.16-2-686/preinst/abort-install-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/bootloader-error-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/kimage-is-a-directory: linux-image-2.6.16-2-686/preinst/abort-overwrite-2.6.16-2-686: linux-image-2.6.16-2-686/prerm/would-invalidate-boot-loader-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/already-running-this-2.6.16-2-686: linux-image-2.6.16-2-686/preinst/elilo-initrd-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/initrd-2.6.16-2-686: linux-image-2.6.16-2-686/postinst/old-initrd-link-2.6.16-2-686: true linux-image-2.6.16-2-686/preinst/lilo-initrd-2.6.16-2-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358424: kernel-image-2.6.8-11-em64t-p4-smp: sk98lin driver not finding my gigabit card
Package: kernel-image-2.6.8-11-em64t-p4-smp Version: 2.6.8-16sarge1 Severity: wishlist The builtin sk98lin driver in that kernel cannot detect properly that gigabit card. sk98lin: No adapter found. Using the manufacturer driver works, however, and the card is properly detected: http://www.marvell.com/drivers/driverDisplay.do?dId=107pId=10 sk98lin: Network Device Driver v8.28.1.3 (C)Copyright 1999-2005 Marvell(R). ACPI: PCI interrupt :04:00.0[A] - GSI 17 (level, low) - IRQ 17 PCI: Setting latency timer of device :04:00.0 to 64 eth1: Marvell Yukon 88E8050 Gigabit Ethernet Controller PrefPort:A RlmtMode:Check Link State Things are not really critical since the driver installs pretty cleanly and works very well, but i'd be nice to avoid relying on that external driver, especially for upgrades. This machine is a Intel(R) Pentium(R) 4 CPU 3.40GHz (hyperthreaded, so SMP) with 2 gigs of ram. lspci -vvv for the device: :04:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown device 4361 (rev 18) Subsystem: Intel Corp.: Unknown device 3452 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR+ PERR- Latency: 0, Cache Line Size: 0x10 (64 bytes) Interrupt: pin A routed to IRQ 17 Region 0: Memory at ff72 (64-bit, non-prefetchable) [size=16K] Region 2: I/O ports at a800 [size=256] Expansion ROM at ff70 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Address: Data: Capabilities: [e0] #10 [0011] There.. I'm not sure if this actually belongs here, but it seems to me it's something to keep in mind, and I'm pretty sure the LKML guys would hit me on the head for complaining about this. :) -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.8-romulus-em64t-p4-smp+vserver Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.8-11-em64t-p4-smp depends on: ii coreutils [fileutils] 5.2.1-2 The GNU core utilities ii e2fsprogs 1.37-2sarge1 ext2 file system utilities and lib ii initrd-tools0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
Package: yaird Version: 0.0.11-12 Severity: important Hello, I just upgraded to sid from sarge, and I'm having problems moving to the kernel 2.6. First off, let me mention that the upgrade didn't go as smoothly as planned, which was to be expected nowadays... My packages for kernel-image-2.6 were removed somehow, probably due to the new linux-image kernels. Anyways... Now that I actually try to switch to 2.6, some weird problem doesn't want to let me. I tried this: # aptitude install yaird [...] # tail -1 /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitrd.yaird # : note that I also tried without the above line # aptitude install linux-image-k7 [...] The following NEW packages will be installed: linux-image-2.6-k7 linux-image-2.6.14-2-k7 linux-image-k7 [...] Selecting previously deselected package linux-image-2.6.14-2-k7. (Reading database ... 230480 files and directories currently installed.) Unpacking linux-image-2.6.14-2-k7 (from .../linux-image-2.6.14-2-k7_2.6.14-4_i386.deb) ... You are attempting to install an initrd kernel image (version 2.6.14-2-k7) while running a kernel of version 2.4.27-2-k7, but you have no suitable ramdisk generation tool installed among /usr/sbin/mkinitrd.yaird. This will break the installation, unless a suitable ramdisk generation tool is also being installed right now. Could not find . at /var/lib/dpkg/tmp.ci/preinst line 228. Selecting previously deselected package linux-image-2.6-k7. Unpacking linux-image-2.6-k7 (from .../linux-image-2.6-k7_2.6.14-4_i386.deb) ... Selecting previously deselected package linux-image-k7. Unpacking linux-image-k7 (from .../linux-image-k7_2.6.14-4_i386.deb) ... Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 Seems to me that yaird doesn't support migration from 2.4 to 2.6.14. It does support anything below 2.6.13 though: # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.12 echo 1 1 # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.13 echo 1 # That is after adding the line to kernel-img.conf but i had the same result before. Now, I *was* able to upgrade, using the initramfs-tools package. Maybe the dependency list for linux-image should be reversed for that package, ie. put initramfs before yaird. # /usr/sbin/mkinitramfs --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.14 echo 1 1 I'm not sure I understand all the implications here, but I leave that all in your wise hands. I can help more if you tell me what to do. :) Thanks, a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Is this what the upgrade path from sarge will look like for etch (assuming here that etch will go up to 2.6.14, or will that not happen at all?). In general, why not simply change the depends to have the whole thing Just Work in the general case? A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
