Bug#589804: Implement missing syscalls on Alpha
On Fri, Jul 23, 2010 at 06:36:20PM +1200, Michael Cree wrote: > On 22/07/10 07:14, maximilian attems wrote: > >On Wed, 21 Jul 2010, Michael Cree wrote: > >>I have tested both these patches applied to the Debian 2.6.32-17 kernel > >>source (though I did have to disable the buildcheck.py script as the ABI > >>didn't match) and it is running successfully on an Alpha PWS600au. > > > >please send in the log of the broken ABI so that it can be ignored > >on purpose. > > Attached. > I see thanks allmost everything changes as expected, this leaves two opportunities: A) ignore the abi change, as it is a clear improvement for alpha and external module should be less of a trouble on this arch. (considering that we haven't released yet).. B) wait for an ABI bump to slide in those patches. I prefer A, but will wait a while to see if anyone voices against. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723075504.gh19...@baikonur.stro.at
Bug#589996: Insane dependency on apt causes kernel to be removed on update
Ben Hutchings writes: > On Thu, 2010-07-22 at 22:19 +0200, Goswin von Brederlow wrote: >> Package: linux-base >> Version: 2.6.32-17 >> Severity: important >> >> Hi, >> >> in the linux-image packages there is now a dependency chain from >> linux-image-2.6... -> linux-base -> libapt-pkg-perl -> >> libapt-pkg-libc6.9-6-4.8. Which is the virtual package provided by apt >> to signal the ABI of its library and binary caches. In effect the >> kernels are locked to a specific ABI version of apt. The problem is >> that the ABI changes from time to time and every time it does an >> update of apt will now remove the kernel for the duration of the >> transition. For an example try installing apt from experimental. >> >> Well, that is life you might say. That is what is called a library >> transition. >> >> But here comes the insane part. The 1637 line long perl postinst >> script of linux-base only depends on apt because of this code at the >> end: > [...] > > What's really insane is that we don't have a nice and stable library to > do this and instead I have to fork every time I want to compare two > strings. > > Ben. Yes, a nice and stable libdpkg is needed. But here it is ONE fork and the script aready forks a zillion times for other tools. So no harm done. MfG Goswin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iq46tvv4@frosties.localdomain
Bug#589996: Insane dependency on apt causes kernel to be removed on update
On 2010-07-23 01:34 +0200, Ben Hutchings wrote: > On Thu, 2010-07-22 at 22:19 +0200, Goswin von Brederlow wrote: >> Package: linux-base >> Version: 2.6.32-17 >> Severity: important >> >> Hi, >> >> in the linux-image packages there is now a dependency chain from >> linux-image-2.6... -> linux-base -> libapt-pkg-perl -> >> libapt-pkg-libc6.9-6-4.8. Which is the virtual package provided by apt >> to signal the ABI of its library and binary caches. In effect the >> kernels are locked to a specific ABI version of apt. The problem is >> that the ABI changes from time to time and every time it does an >> update of apt will now remove the kernel for the duration of the >> transition. For an example try installing apt from experimental. >> >> Well, that is life you might say. That is what is called a library >> transition. >> >> But here comes the insane part. The 1637 line long perl postinst >> script of linux-base only depends on apt because of this code at the >> end: > [...] > > What's really insane is that we don't have a nice and stable library to > do this and instead I have to fork every time I want to compare two > strings. Isn't there libdpkg-perl which provides this, see Dpkg::Version(3)? Though it might not be suitable for linux-base, because you would have to depend on libdpkg-perl | dpkg-dev (<< 1.15.6). Sven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k4ompm1r@turtle.gmx.de
Bug#590090: linux-image-2.6.35-rc5-686: HP Compaq 6715s with radeon KMS does not shutdown anymore
Package: linux-2.6 Version: 2.6.35~rc5-1~experimental.1 Severity: important Hello, since I have updated from 2.6.34 from experimental to 2.6.35-rc5, my notebook does not shutdown anymore. I am using KDE4 (and so on kdm). If I choose shutdown, kdm exits and then I can not do anything. Switching to another console etc does not work and there is no shutdown :( I am using the radeon driver with KMS (per default) enabled. -- Package-specific info: ** Version: Linux version 2.6.35-rc5-686 (Debian 2.6.35~rc5-1~experimental.1) (b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-6) ) #1 SMP Tue Jul 13 16:16:00 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc5-686 root=UUID=fc14f80e-bb68-45b3-b227-b76e7d9349c1 ro quiet ** Not tainted ** Kernel log: [9.399137] ACPI: AC Adapter [C1EB] (off-line) [9.488311] ACPI: Battery Slot [C1ED] (battery present) [9.488512] ACPI: Battery Slot [C1EC] (battery absent) [9.525607] ACPI: WMI: Mapper loaded [9.913968] k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 [9.971567] acpi device:01: registered as cooling_device6 [9.972392] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/LNXVIDEO:00/input/input4 [9.972450] ACPI: Video Device [C08D] (multi-head: yes rom: no post: no) [9.991457] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x2580b1, caps: 0xa04793/0x30/0x0 [9.991463] serio: Synaptics pass-through port at isa0060/serio4/input0 [ 10.031984] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input5 [ 10.104149] piix4_smbus :00:14.0: SMBus Host Controller at 0x8200, revision 0 [ 10.363810] cfg80211: Calling CRDA to update world regulatory domain [ 10.371204] input: HP WMI hotkeys as /devices/virtual/input/input6 [ 10.817300] b43-phy0: Broadcom 4311 WLAN found (core revision 13) [ 11.355314] phy0: Selected rate control algorithm 'minstrel' [ 11.356004] Registered led device: b43-phy0::tx [ 11.356030] Registered led device: b43-phy0::rx [ 11.356052] Registered led device: b43-phy0::radio [ 11.356122] Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] [ 11.573387] HDA Intel :00:14.2: power state changed by ACPI to D0 [ 11.573433] HDA Intel :00:14.2: power state changed by ACPI to D0 [ 11.573445] HDA Intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.632993] input: HDA Digital PCBeep as /devices/pci:00/:00:14.2/input/input7 [ 13.204665] Adding 971928k swap on /dev/sda2. Priority:-1 extents:1 across:971928k [ 13.462621] EXT3-fs (sda3): using internal journal [ 13.625575] loop: module loaded [ 14.981640] fuse init (API version 7.14) [ 16.443936] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input8 [ 18.200398] apm: BIOS not found. [ 19.676954] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology TL-56 (2 cpu cores) (version 2.20.00) [ 19.677023] powernow-k8:0 : fid 0xa (1800 MHz), vid 0x12 [ 19.677026] powernow-k8:1 : fid 0x8 (1600 MHz), vid 0x14 [ 19.677029] powernow-k8:2 : fid 0x0 (800 MHz), vid 0x1e [ 20.173039] Clocksource tsc unstable (delta = -178542988 ns) [ 22.256921] tg3 :10:00.0: irq 43 for MSI/MSI-X [ 22.287685] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 22.764068] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 22.850434] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 25.798950] pci :01:05.0: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 26.049163] [drm] Initialized drm 1.1.0 20060810 [ 26.342856] [drm] radeon kernel modesetting enabled. [ 26.351239] [drm] initializing kernel modesetting (RS690 0x1002:0x791F). [ 26.351447] [drm] register mmio base: 0xD020 [ 26.351453] [drm] register mmio size: 65536 [ 26.351800] ATOM BIOS: ATI [ 26.351861] radeon :01:05.0: VRAM: 128M 0x7800 - 0x7FFF (128M used) [ 26.351869] radeon :01:05.0: GTT: 512M 0x8000 - 0x9FFF [ 26.352058] [drm] radeon: irq initialized. [ 26.352445] [drm] Detected VRAM RAM=128M, BAR=128M [ 26.352455] [drm] RAM width 128bits DDR [ 26.353256] [TTM] Zone kernel: Available graphics memory: 443796 kiB. [ 26.353263] [TTM] Zone highmem: Available graphics memory: 972024 kiB. [ 26.353269] [TTM] Initializing pool allocator. [ 26.353320] [drm] radeon: 128M of VRAM memory ready [ 26.353326] [drm] radeon: 512M of GTT memory ready. [ 26.353376] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 26.371089] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [ 26.391224] [drm] Loading RS690/RS740 Microcode [ 26.472365] [drm] radeon: ring at 0x8000 [ 26.472395] [drm] ring test succeeded in 1 usecs [ 26.472751] [drm] radeon: ib pool ready. [ 26.472913] [drm] ib test succeeded in 0 usecs [ 26.473034] [drm] Default TV standard: NTSC [ 26.473322] [drm] Default TV standard: NTSC [ 26.473406] [drm] Radeon Displ
Bug#580901: suspend to disk break multithreading
Hi, I can confirm this on a core i7. A funny side effect is that single threaded programs run twice as fast after suspend to disk than they did before! It would be nice to have that power available before suspend too! processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz stepping: 5 cpu MHz : 1728.714 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 3458.48 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz stepping: 5 cpu MHz : 1728.714 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 11 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 3458.87 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz stepping: 5 cpu MHz : 1728.714 cache size : 8192 KB physical id : 0 siblings: 8 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 3459.81 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz stepping: 5 cpu MHz : 1728.714 cache size : 8192 KB physical id : 0 siblings: 8 core id : 1 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 11 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 3458.18 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz stepping: 5 cpu MHz : 1728.714 cache size : 8192 KB physical id : 0 siblings: 8 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 3458.45 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 5 ve
Bug#580901: suspend to disk break multithreading
See also https://bugzilla.kernel.org/show_bug.cgi?id=15559 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723.182923.760530912486605785.debian00+l...@umons.ac.be
Le virement
Btissam DERRAZ Compte bancaire : Banque populaire Agence el Harti Marrakech 145 450 2 9951152 000 1 /94 Code swift: BCPOMAMCMKH -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723162337.423a113a4...@liszt.debian.org
Bug#583689: Not yet support for loongson-2f
found 583689 2.6.34-1~experimental.2 thanks Hello Debian Kernel people, Version 2.6.34-1~experimental.2 says [ 0.764000] /build/buildd-linux-2.6_2.6.34-1~exprimental.2-mipsel-ZShPn4/linux-2.6-2.6.34/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable open rtc device (rtc0) And also [ 0.912000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [ 0.916000] ata1.00: 312581808 sectors, mult 16: LBA48 [ 0.932000] ata1.00: configured for UDMA/100 [ 0.936000] scsi 0:0:0:0 Direct-Access ATA WDC WD1600BEVT-2 11.0 PQ: 0 ANSI: 5 [ 0.94] VFS: Cannot open root device "hda1" or unknown-block(0,0) So it is too early to close bugreport 583689 Groeten Geert Stappers signature.asc Description: Digital signature
Processed: Not yet support for loongson-2f
Processing commands for cont...@bugs.debian.org: > found 583689 2.6.34-1~experimental.2 Bug #583689 [linux-2.6] please add support for longsoon 2f There is no source info for the package 'linux-2.6' at version '2.6.34-1~experimental.2' with architecture '' Unable to make a source version for version '2.6.34-1~experimental.2' Bug Marked as found in versions 2.6.34-1~experimental.2; no longer marked as fixed in versions 2.6.34-1~experimental.2. > thanks Stopping processing here. Please contact me if you need assistance. -- 583689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127990802119699.transcr...@bugs.debian.org
Bug#583689: FYI: 2.6.35-rc5-loongson-2f does see disk
For you information, on version 2.6.35-rc5-loongson-2f there is still the RTC error, but the harddisk is seen. (version 2.6.34 doesn't see a disk) dmesg output [0.732000] /usr/src/Linux/debian-svn/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.736000] Initalizing network drop monitor service [0.916000] ata1.00: ATA-8: WDC WD1600BEVT-22ZCT0, 11.01A11, max UDMA/133 [0.92] ata1.00: 312581808 sectors, multi 16: LBA48 [0.932000] ata1.00: configured for UDMA/100 [0.936000] scsi 0:0:0:0: Direct-Access ATA WDC WD1600 BEVT-2 11.0 PQ: 0 ANSI: 5 [0.94] ata2: port disabled. ignoring. [0.94] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks : (160 GB/149 GiB) [0.944000] sd 0:0:0:0: [sda] Write Protect is off [0.948000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [0.948000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [0.952000] sda: sda1 sda2 sda3 sda4 [0.968000] sd 0:0:0:0: [sda] Attached SCSI disk [0.976000] EXT3-fs: barriers not enabled [0.984000] kjournald starting. Commit interval 5 seconds [0.988000] EXT3-fs (sda1): mounted filesystem with ordered data mode [0.992000] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. hth gst -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723181040.gn11...@gpm.stappers.nl
Bug#583689: Not yet support for loongson-2f
fixed 583689 2.6.34-1~experimental.2 thanks On Fri, Jul 23, 2010 at 07:53:49PM +0200, Geert Stappers wrote: > [ 0.94] VFS: Cannot open root device "hda1" or unknown-block(0,0) You have to supply a correct initramfs. > So it is too early to close bugreport 583689 How would it provide this output if it is broken? Bastian -- No one can guarantee the actions of another. -- Spock, "Day of the Dove", stardate unknown -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723182434.ga1...@wavehammer.waldi.eu.org
Processed: Re: Bug#583689: Not yet support for loongson-2f
Processing commands for cont...@bugs.debian.org: > fixed 583689 2.6.34-1~experimental.2 Bug #583689 [linux-2.6] please add support for longsoon 2f There is no source info for the package 'linux-2.6' at version '2.6.34-1~experimental.2' with architecture '' Unable to make a source version for version '2.6.34-1~experimental.2' Bug Marked as fixed in versions 2.6.34-1~experimental.2. > thanks Stopping processing here. Please contact me if you need assistance. -- 583689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127990948732111.transcr...@bugs.debian.org
Bug#583689: Not yet support for loongson-2f
* Bastian Blank [2010-07-23 20:24]: > > [ 0.94] VFS: Cannot open root device "hda1" or unknown-block(0,0) > > You have to supply a correct initramfs. No, it should be built in (mips/mipsel don't use initramfs). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723190641.ga4...@jirafa.cyrius.com
Bug#583689: loongson-2f is missing USB Host Controller
Hello Debian Kernel People, On both 2.6.34 and 2.6.35 for the MIPSEL flavour loonson-2f is a USB Host controller missing. Missing as is in "Not compiled in the kernel, not even as a module." This is what went during build in the .config file: | # | # USB Host Controller Drivers | # | CONFIG_USB_C67X00_HCD=m | CONFIG_USB_XHCI_HCD=m | # CONFIG_USB_XHCI_HCD_DEBUGGING is not set | # CONFIG_USB_EHCI_HCD is not set | # CONFIG_USB_OXU210HP_HCD is not set | CONFIG_USB_ISP116X_HCD=m | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | # CONFIG_USB_OHCI_HCD is not set | # CONFIG_USB_UHCI_HCD is not set | CONFIG_USB_U132_HCD=m | # CONFIG_USB_SL811_HCD is not set | CONFIG_USB_R8A66597_HCD=m | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m This is what aba requested in http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=config.2.6.34-1~experimental.1;att=3;bug=583689 | # | # USB Host Controller Drivers | # | # CONFIG_USB_C67X00_HCD is not set | # CONFIG_USB_XHCI_HCD is not set | CONFIG_USB_EHCI_HCD=y | CONFIG_USB_EHCI_ROOT_HUB_TT=y | # CONFIG_USB_EHCI_TT_NEWSCHED is not set | # CONFIG_USB_OXU210HP_HCD is not set | # CONFIG_USB_ISP116X_HCD is not set | # CONFIG_USB_ISP1760_HCD is not set | # CONFIG_USB_ISP1362_HCD is not set | CONFIG_USB_OHCI_HCD=y | # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set | # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set | CONFIG_USB_OHCI_LITTLE_ENDIAN=y | CONFIG_USB_UHCI_HCD=m | # CONFIG_USB_SL811_HCD is not set | # CONFIG_USB_R8A66597_HCD is not set | CONFIG_USB_WHCI_HCD=m | CONFIG_USB_HWA_HCD=m | # CONFIG_USB_GADGET_MUSB_HDRC is not set It is at least 'CONFIG_USB_OHCI_HCD=y' that should come back in the .config file. Groeten Geert Stappers -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723194801.go11...@gpm.stappers.nl
Bug#583689: Not yet support for loongson-2f
# Op 20100723 om 20:06 schreef Martin Michlmayr: # > * Bastian Blank [2010-07-23 20:24]: # > > > [ 0.94] VFS: Cannot open root device "hda1" or unknown-block(0,0) # > > # > > You have to supply a correct initramfs. # > # > No, it should be built in (mips/mipsel don't use initramfs). # found 583689 2.6.34-1~experimental.2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723195601.gp11...@gpm.stappers.nl
Processed: Re: Bug#583689: Not yet support for loongson-2f
Processing commands for cont...@bugs.debian.org: > # Op 20100723 om 20:06 schreef Martin Michlmayr: > # > * Bastian Blank [2010-07-23 20:24]: > # > > > [ 0.94] VFS: Cannot open root device "hda1" or > unknown-block(0,0) > # > > > # > > You have to supply a correct initramfs. > # > > # > No, it should be built in (mips/mipsel don't use initramfs). > # > found 583689 2.6.34-1~experimental.2 Bug #583689 [linux-2.6] please add support for longsoon 2f There is no source info for the package 'linux-2.6' at version '2.6.34-1~experimental.2' with architecture '' Unable to make a source version for version '2.6.34-1~experimental.2' Bug No longer marked as fixed in versions 2.6.34-1~experimental.2. > End of message, stopping processing here. Please contact me if you need assistance. -- 583689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127991486519227.transcr...@bugs.debian.org
Bug#589989: [PATCH net-next-2.6] 3c59x: Fix call to mdio_sync() with the wrong argument
From: Ben Hutchings Date: Fri, 23 Jul 2010 01:18:28 +0100 > commit a095cfc40ec7ebe63e9532383c5b5c2a27b14075 > "3c59x: Specify window explicitly for access to windowed registers" > changed the first parameter to mdio_sync(), from a pointer to the > register mapping, to a pointer to the vortex_private structure, > and changed all but one of the call sites. Fix that last one. > > Reported-by: Luca Falavigna > Signed-off-by: Ben Hutchings Applied. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723.130538.229733396.da...@davemloft.net
Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
I am experiencing this problem as well. I have read through this bug report, and the most recent entry suggesting purging util-vserver does not make any sense. If you purge that package, you lose the utilities you need to start the virtual servers. If you re-install it from lenny sources, the problem persists. Just wondering if anyone has a solution for this yet, short of stopping and restarting all affected vservers after reboot. -- Scott Barker sc...@mostlylinux.ca Linux Consultant http://www.mostlylinux.ca/scott -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723203102.gm1...@mostlylinux.ca
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
I wrote: > ... I'm going to compile the kernel again without that particular > warning (and with kgdb support) and see if I can dig out anything > interesting. My attempt to compile the kernel with kgdb support failed. Something in the Debian kernel packaging thingy complained like this: ABI has changed! Refusing to continue. Added symbols: kgdb_breakpoint module: vmlinux, version: 0x01e1a8de, export: EXPORT_SYMBOL_GPL ... Changed symbols: __audit_inode_child module: vmlinux, version: 0xead6af60 -> 0xe3835d2d, export: EXPORT_SYMBOL_GPL __fatal_signal_pending module: vmlinux, version: 0xb5428735 -> 0xee8d0603, export: EXPORT_SYMBOL [lots more] I've run out of time to do more on this now. Ian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/19530.7824.326265.929...@chiark.greenend.org.uk
Processed: this is RC since it hard locks ARM machines
Processing commands for cont...@bugs.debian.org:
> severity 588164 grave
Bug #588164 {Done: Ben Hutchings } [linux-2.6]
linux-image-2.6.32-5-orion5x: kernel NULL pointer dereference while loading
module parport_pc
Bug #589678 {Done: Ben Hutchings } [linux-2.6] Installing
cups on SheevaPlug Development Kit freezes system
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
> --
Stopping processing here.
Please contact me if you need assistance.
--
588164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.127992946813448.transcr...@bugs.debian.org
Processed: tagging 534422
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 534422 + pending Bug #534422 [linux-2.6] Enabling KMS causes lots of segfaults after hibernation resume Bug #545125 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #545517 [linux-2.6] linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk Bug #571741 [linux-2.6] System freezes after pm-hibernate when kms is on Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating Ignoring request to alter tags of bug #534422 to the same tags previously set Ignoring request to alter tags of bug #545125 to the same tags previously set Ignoring request to alter tags of bug #545517 to the same tags previously set Ignoring request to alter tags of bug #571741 to the same tags previously set Ignoring request to alter tags of bug #576800 to the same tags previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 534422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127992960014144.transcr...@bugs.debian.org
Processed: tagging 589989
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 589989 + pending Bug #589989 [linux-2.6] Kernel panic after few seconds of booting Ignoring request to alter tags of bug #589989 to the same tags previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 589989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127992960114253.transcr...@bugs.debian.org
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_2.6.32-18.diff.gz linux-2.6_2.6.32-18.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:25:45, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ocsfk-0004wx...@franck.debian.org
Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
On Fri, 2010-07-23 at 23:58 +0100, Ian Jackson wrote: > I wrote: > > ... I'm going to compile the kernel again without that particular > > warning (and with kgdb support) and see if I can dig out anything > > interesting. > > My attempt to compile the kernel with kgdb support failed. Something > in the Debian kernel packaging thingy complained like this: > ABI has changed! Refusing to continue. > Added symbols: > kgdb_breakpoint module: vmlinux, > version: 0x01e1a8de, export: EXPORT_SYMBOL_GPL > ... > Changed symbols: > __audit_inode_child module: vmlinux, version: > 0xead6af60 -> 0xe3835d2d, export: EXPORT_SYMBOL_GPL > __fatal_signal_pending module: vmlinux, version: > 0xb5428735 -> 0xee8d0603, export: EXPORT_SYMBOL > [lots more] > > I've run out of time to do more on this now. If you remove the 'debian/abi' directory this check will be skipped. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processing of linux-2.6_2.6.32-18_multi.changes
linux-2.6_2.6.32-18_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-18.dsc linux-2.6_2.6.32-18.diff.gz linux-doc-2.6.32_2.6.32-18_all.deb linux-manual-2.6.32_2.6.32-18_all.deb linux-patch-debian-2.6.32_2.6.32-18_all.deb linux-source-2.6.32_2.6.32-18_all.deb linux-support-2.6.32-5_2.6.32-18_all.deb firmware-linux-free_2.6.32-18_all.deb linux-base_2.6.32-18_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oct2e-0007u1...@franck.debian.org
linux-2.6_2.6.32-18_multi.changes ACCEPTED
Accepted: firmware-linux-free_2.6.32-18_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-18_all.deb linux-2.6_2.6.32-18.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-18.diff.gz linux-2.6_2.6.32-18.dsc to main/l/linux-2.6/linux-2.6_2.6.32-18.dsc linux-base_2.6.32-18_all.deb to main/l/linux-2.6/linux-base_2.6.32-18_all.deb linux-doc-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-18_all.deb linux-manual-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-18_all.deb linux-patch-debian-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-18_all.deb linux-source-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-18_all.deb linux-support-2.6.32-5_2.6.32-18_all.deb to main/l/linux-2.6/linux-support-2.6.32-5_2.6.32-18_all.deb Override entries for your package: firmware-linux-free_2.6.32-18_all.deb - optional kernel linux-2.6_2.6.32-18.dsc - source devel linux-base_2.6.32-18_all.deb - optional kernel linux-doc-2.6.32_2.6.32-18_all.deb - optional doc linux-manual-2.6.32_2.6.32-18_all.deb - optional doc linux-patch-debian-2.6.32_2.6.32-18_all.deb - optional kernel linux-source-2.6.32_2.6.32-18_all.deb - optional kernel linux-support-2.6.32-5_2.6.32-18_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 534422 574766 580124 588426 588863 589989 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oct9f-00019o...@franck.debian.org
Bug#576800: marked as done (libc6: Cannot create new processes after hibernating)
Your message dated Sat, 24 Jul 2010 01:03:29 + with message-id and subject line Bug#534422: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #534422, regarding libc6: Cannot create new processes after hibernating to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.10.2-6 Severity: critical Justification: breaks the whole system After resuming my EeePC from hibernation, I can no longer start new processes. This goes so far as preventing shutdown since init itself cannot be forked so that the only solution is a hard reset. Hence the 'breaks the whole system' justification. Also, although this only happens after hibernating, I feel this is a pretty unavoidable activity on a laptop. Since no new process can be started (including gdb, strace, etc), this is quite hard to debug. I do get some traces in /var/log/syslog though: Apr 7 11:58:47 malte kernel: [ 122.856385] sh[2687]: segfault at b773f11f ip b772f001 sp bffb8300 error 7 in ld-2.10.2.so[b7725000+1c000] Apr 7 11:58:47 malte kernel: [ 122.961515] date[2690]: segfault at b781f11f ip b780f001 sp bfaaed00 error 7 in ld-2.10.2.so[b7805000+1c000] Apr 7 11:58:47 malte kernel: [ 122.963258] sort[2693]: segfault at b78e311f ip b78d3001 sp bfa10ad0 error 7 in ld-2.10.2.so[b78c9000+1c000] Apr 7 11:58:47 malte kernel: [ 122.963836] uniq[2694]: segfault at b787c11f ip b786c001 sp bfa5fdc0 error 7 in ld-2.10.2.so[b7862000+1c000] Apr 7 11:58:47 malte kernel: [ 122.966155] rm[2696]: segfault at b770711f ip b76f7001 sp bff05d20 error 7 in ld-2.10.2.so[b76ed000+1c000] I am reporting this bug against libc6 because if I understand the above traces correctly, they indicate that the crash occurs in ld-2.10.2.so which belongs to libc6. But I acknowledge that the bug may instead be in the Linux kernel. In my case: ii linux-image-2.6-6862.6.32+25 Linux 2.6 for modern PCs ii linux-image-2.6.32-3-686 2.6.32-9 Linux 2.6.32 for modern PCs -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libc-bin 2.10.2-6 Embedded GNU C Library: Binaries ii libgcc1 1:4.4.2-9 GCC support library Versions of packages libc6 recommends: ii libc6-i6862.10.2-6 GNU C Library: Shared libraries [i Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.30 Debian configuration management sy pn glibc-doc (no description available) ii locales 2.10.2-6 Embedded GNU C Library: National L -- debconf information: * glibc/upgrade: true glibc/disable-screensaver: glibc/restart-failed: * glibc/restart-services: rsync openbsd-inetd exim4 cups cron atd --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.32-18 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-18_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-18_all.deb linux-2.6_2.6.32-18.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-18.diff.gz linux-2.6_2.6.32-18.dsc to main/l/linux-2.6/linux-2.6_2.6.32-18.dsc linux-base_2.6.32-18_all.deb to main/l/linux-2.6/linux-base_2.6.32-18_all.deb linux-doc-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-18_all.deb linux-manual-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-18_all.deb linux-patch-debian-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-18_all.deb linux-source-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-18_all.deb linux-support-2.6.32-5_2.6.32-18_all.deb to main/l/linux-2.6/linux-support-2.6.32-5_2.6.32-18_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 534...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier o
Bug#545517: marked as done (linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk)
Your message dated Sat, 24 Jul 2010 01:03:29 + with message-id and subject line Bug#534422: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #534422, regarding linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.31~rc6-1~experimental.1~snapshot.14160 Severity: normal Hi, I've tried KMS since about 2.6.30. I've seen support improved for each new kernel version (each new rc for 2.6.31), however suspend-to-disk has always problems. With older kernel version, KMS and suspend-to-disk did not work at all. With more recent kernel (as 2.6.31-rc6), KMS and suspend-to-disk seems to work sometimes. However, it happens sometimes to freeze at restart (just after reloading the kernel state, ie after the "... reloading ... 100%"). The laptop is then completly frozen, the graphical screen is not correctly restored and I do not see anything in the /var/log/syslog after next reboot. When the laptop is so frozen, the only solution is to hard-reboot it. After several such freeze, some ext3 corruptions have been found on my disks (both / and /home). I do not know if they are due to the bug itself or to the fact that I had to hard-reboot the machine. Nevertheless, I removed KMS in my configuration and now I can use suspend-to-disk without any problems. Summer break being ended, I need to be able to suspend-to-disk and not to have on-disk corruption. So I do not know when I will be able to test KMS again. If other users experiment the same problem, this bug can be use to track the progress on it. For info, my graphic card is (from lspci): 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) Regards, Vincent PS: to enable KMS, I only added intel_agp drm i915 modeset=1 in /etc/initramfs-tools/modules and recreated the initrd -- Package-specific info: ** Version: Linux version 2.6.31-rc6-amd64 (Debian 2.6.31~rc6-1~experimental.1~snapshot.14160) (wa...@debian.org) (gcc version 4.3.3 (GCC) ) #1 SMP Sat Aug 22 01:15:15 UTC 2009 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.31-rc6-amd64 root=/dev/mapper/eyak-root ro quiet ** Tainted: G W (512) ** Kernel log: [236124.392058] CPU1 attaching sched-domain: [236124.392061] domain 0: span 0-1 level MC [236124.392064] groups: 1 0 [236124.392704] CPU1 is up [236124.392708] ACPI: Waking up from system sleep state S4 [236124.404729] pci :00:02.0: restoring config space at offset 0x1 (was 0x97, writing 0x900403) [236124.404851] ehci_hcd :00:1a.7: PME# disabled [236124.404889] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100102) [236124.405222] ehci_hcd :00:1d.7: PME# disabled [236124.405244] pci :00:1e.0: restoring config space at offset 0x6 (was 0x20040300, writing 0x20070300) [236124.405367] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407) [236124.405516] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100506) [236124.405620] tg3 :09:00.0: restoring config space at offset 0xc (was 0x0, writing 0x2020) [236124.405685] yenta_cardbus :03:01.0: restoring config space at offset 0xf (was 0x14001ff, writing 0x5c001ff) [236124.405698] yenta_cardbus :03:01.0: restoring config space at offset 0xa (was 0x0, writing 0xf43ff000) [236124.405704] yenta_cardbus :03:01.0: restoring config space at offset 0x9 (was 0x0, writing 0xf400) [236124.405718] yenta_cardbus :03:01.0: restoring config space at offset 0x3 (was 0x824000, writing 0x82a800) [236124.405725] yenta_cardbus :03:01.0: restoring config space at offset 0x1 (was 0x417, writing 0x4100087) [236124.405769] firewire_ohci :03:01.4: restoring config space at offset 0x1 (was 0x2100117, writing 0x2180117) [236124.446617] pci :00:02.0: PME# disabled [236124.446624] pci :00:02.0: setting latency timer to 64 [236124.446628] pci :00:02.1: PME# disabled [236124.446634] uhci_hcd :00:1a.0: setting latency timer to 64 [236124.446674] usb usb2: root hub lost power or was reset [236124.446713] uhci_hcd :00:1a.1: setting latency timer to 64 [236124.446752] usb usb4: root hub lost power or was reset [236124.446772] ehci_hcd :00:1a.7: PME# disabled [236124.446776] ehci_hcd :00:1a.7: setting latency timer
Bug#545125: marked as done (linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk)
Your message dated Sat, 24 Jul 2010 01:03:29 + with message-id and subject line Bug#534422: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #534422, regarding linux-image-2.6.31-rc6-amd64: freeze and on-disk corruption with KMS and suspend-to-disk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.31-rc6-amd64 Version: 2.6.31~rc6-1~experimental.1~snapshot.14160 Severity: normal Hi, I've tried KMS since about 2.6.30. I've seen support improved for each new kernel version (each new rc for 2.6.31), however suspend-to-disk has always problems. With older kernel version, KMS and suspend-to-disk did not work at all. With more recent kernel (as 2.6.31-rc6), KMS and suspend-to-disk seems to work sometimes. However, it happens sometimes to freeze at restart (just after reloading the kernel state, ie after the "... reloading ... 100%"). The laptop is then completly frozen, the graphical screen is not correctly restored and I do not see anything in the /var/log/syslog after next reboot. When the laptop is so frozen, the only solution is to hard-reboot it. After several such freeze, some ext3 corruptions have been found on my disks (both / and /home). I do not know if they are due to the bug itself or to the fact that I had to hard-reboot the machine. Nevertheless, I removed KMS in my configuration and now I can use suspend-to-disk without any problems. Summer break being ended, I need to be able to suspend-to-disk and not to have on-disk corruption. So I do not know when I will be able to test KMS again. If other users experiment the same problem, this bug can be use to track the progress on it. For info, my graphic card is (from lspci): 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) Regards, Vincent PS: to enable KMS, I only added intel_agp drm i915 modeset=1 in /etc/initramfs-tools/modules and recreated the initrd -- Package-specific info: ** Version: Linux version 2.6.31-rc6-amd64 (Debian 2.6.31~rc6-1~experimental.1~snapshot.14160) (wa...@debian.org) (gcc version 4.3.3 (GCC) ) #1 SMP Sat Aug 22 01:15:15 UTC 2009 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.31-rc6-amd64 root=/dev/mapper/eyak-root ro quiet ** Tainted: G W (512) ** Kernel log: [236124.392058] CPU1 attaching sched-domain: [236124.392061] domain 0: span 0-1 level MC [236124.392064] groups: 1 0 [236124.392704] CPU1 is up [236124.392708] ACPI: Waking up from system sleep state S4 [236124.404729] pci :00:02.0: restoring config space at offset 0x1 (was 0x97, writing 0x900403) [236124.404851] ehci_hcd :00:1a.7: PME# disabled [236124.404889] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100102) [236124.405222] ehci_hcd :00:1d.7: PME# disabled [236124.405244] pci :00:1e.0: restoring config space at offset 0x6 (was 0x20040300, writing 0x20070300) [236124.405367] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407) [236124.405516] iwlagn :0c:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100506) [236124.405620] tg3 :09:00.0: restoring config space at offset 0xc (was 0x0, writing 0x2020) [236124.405685] yenta_cardbus :03:01.0: restoring config space at offset 0xf (was 0x14001ff, writing 0x5c001ff) [236124.405698] yenta_cardbus :03:01.0: restoring config space at offset 0xa (was 0x0, writing 0xf43ff000) [236124.405704] yenta_cardbus :03:01.0: restoring config space at offset 0x9 (was 0x0, writing 0xf400) [236124.405718] yenta_cardbus :03:01.0: restoring config space at offset 0x3 (was 0x824000, writing 0x82a800) [236124.405725] yenta_cardbus :03:01.0: restoring config space at offset 0x1 (was 0x417, writing 0x4100087) [236124.405769] firewire_ohci :03:01.4: restoring config space at offset 0x1 (was 0x2100117, writing 0x2180117) [236124.446617] pci :00:02.0: PME# disabled [236124.446624] pci :00:02.0: setting latency timer to 64 [236124.446628] pci :00:02.1: PME# disabled [236124.446634] uhci_hcd :00:1a.0: setting latency timer to 64 [236124.446674] usb usb2: root hub lost power or was reset [236124.446713] uhci_hcd :00:1a.1: setting latency timer to 64 [236124.446752] usb usb4: root hub lost power or was reset [236124.446772] ehci_hcd :00:1a.7: PME# disabled [236124.446776] ehci_hcd :00:1a.7: set
Bug#574766: marked as done (2.6.32-3-686: No WPA with Ralink rt2860 (works with upstream driver, though))
Your message dated Sat, 24 Jul 2010 01:03:29 + with message-id and subject line Bug#574766: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #574766, regarding 2.6.32-3-686: No WPA with Ralink rt2860 (works with upstream driver, though) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 574766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-9 Severity: normal I cannot get a WPA-encrypted WLAN connection to work with the included rt2860 driver (staging). Attached is a syslog snippet of a failing connection attempt. Unencrypted connections work fine. As a workaround, I took the rt2860-source package from unstable and upgraded the included upstream driver from 1.8.0.0 to the latest version provided by Ralink (2.3.0.0). There were only minor adjustments of the Debian-patches necessary. I compiled the updated package with module-assistant, removed the rt2860 module from the linux-image package and installed the replacement. After loading the new kernel module everything was fine: WPA and unencrypted connections are working. I tried to look at the diff between the upstream driver and the one in the kernel sources. Unfortunately, there is no one-to-one correspondance between source files. However, were comparison was possible the kernel driver looks older and the diff is substantial. I'm not an expert in WPA issue debugging, but please let me know if I can be of help fixing this issue. Thanks, Michael PS: Note that the system information below is collected with the working rt2860 loaded. Moreover, I removed the kernel log, as it had only firewall messages. -- Syslog excerpt -- Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 20 09:22:24 morkel NetworkManager: (wlan0): device state change: 6 -> 4 (reason 0) Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 20 09:22:24 morkel NetworkManager: (wlan0): device state change: 4 -> 5 (reason 0) Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0/wireless): connection 'Auto Selma' has security, and secrets exist. No new secrets needed. Mar 20 09:22:24 morkel NetworkManager: Config: added 'ssid' value 'Selma' Mar 20 09:22:24 morkel NetworkManager: Config: added 'scan_ssid' value '1' Mar 20 09:22:24 morkel NetworkManager: Config: added 'key_mgmt' value 'WPA-PSK' Mar 20 09:22:24 morkel NetworkManager: Config: added 'psk' value '' Mar 20 09:22:24 morkel NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 20 09:22:24 morkel NetworkManager: Config: set interface ap_scan to 1 Mar 20 09:22:24 morkel NetworkManager: (wlan0): supplicant connection state: disconnected -> scanning Mar 20 09:22:29 morkel wpa_supplicant[2083]: Trying to associate with 00:15:e9:d6:7a:d0 (SSID='Selma' freq=2437 MHz) Mar 20 09:22:29 morkel NetworkManager: (wlan0): supplicant connection state: scanning -> associating Mar 20 09:22:29 morkel kernel: [ 3897.684288] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 286 Mar 20 09:22:29 morkel kernel: [ 3897.684849] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=6) Mar 20 09:22:39 morkel wpa_supplicant[2083]: Authentication with 00:15:e9:d6:7a:d0 timed out. Mar 20 09:22:39 morkel NetworkManager: (wlan0): supplicant connection state: associating -> disconnected Mar 20 09:22:39 morkel NetworkManager: (wlan0): supplicant connection state: disconnected -> scanning Mar 20 09:22:44 morkel kernel: [ 3912.709580] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 113 Mar 20 09:22:50 morkel NetworkManager: Activation (wlan0/wireless): association took too long. Mar 20 09:22:50 morkel NetworkManager: (wlan0): device state change: 5 -> 6 (reason 0) Mar 20 09:22:50 morkel NetworkManager: Activation (wlan0/wireless): asking for new secrets Mar 20 09:22:50 morkel NetworkManager: (wlan0): supplicant connection state: scanning -> disconnected Mar 20 09:22:51 morkel NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 20 09:22:51 morkel NetworkManager: Activation (wla
Bug#589178: marked as done (linux-image-2.6.32-5-amd64: regression: kernel does not boot in kvm after update)
Your message dated Sat, 24 Jul 2010 01:03:30 + with message-id and subject line Bug#588426: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #588426, regarding linux-image-2.6.32-5-amd64: regression: kernel does not boot in kvm after update to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 588426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-17 Severity: normal after updating linux-image-2.6.32-5-amd64 from 2.6.32-15 to 2.6.32-17 the kernel doesn't boot in a lenny kvm anymore. the attached info is gathered from the working version! -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010 ** Command line: console=ttyS0,115200n8 root=/dev/sda ro verbose debug ** Not tainted ** Kernel log: [0.900948] TCP cubic registered [0.901555] NET: Registered protocol family 10 [0.912884] lo: Disabled Privacy Extensions [0.913630] Mobile IPv6 [0.914055] NET: Registered protocol family 17 [0.924810] PM: Resume from disk failed. [0.925328] registered taskstats version 1 [0.926221] rtc_cmos 00:01: setting system clock to 2010-07-15 14:45:19 UTC (1279205119) [0.937395] Initalizing network drop monitor service [0.948249] Freeing unused kernel memory: 584k freed [0.949063] Write protecting the kernel read-only data: 4208k [0.976066] udev: starting version 158 [0.997972] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [1.051407] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [1.056672] SCSI subsystem initialized [1.063379] 8139cp :00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 [1.074153] libata version 3.00 loaded. [1.076610] FDC 0 is a S82078B [1.081377] eth0: RTL-8139C+ at 0xc95be000, 52:54:00:12:34:56, IRQ 11 [1.092704] 8139cp :00:03.0: setting latency timer to 64 [1.103751] ata_piix :00:01.1: version 2.13 [1.104942] ata_piix :00:01.1: setting latency timer to 64 [1.106323] 8139too Fast Ethernet driver 0.9.28 [1.117807] scsi0 : ata_piix [1.118708] scsi1 : ata_piix [1.129787] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [1.131560] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 [1.296707] ata1.00: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.307723] ata1.00: 20971520 sectors, multi 16: LBA48 [1.308623] ata1.01: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.309440] ata2.00: ATA-7: QEMU HARDDISK, 0.9.1, max UDMA/100 [1.309443] ata2.00: 20971520 sectors, multi 16: LBA48 [1.310065] ata2.00: configured for MWDMA2 [1.332566] ata1.01: 20971520 sectors, multi 16: LBA48 [1.344415] ata1.00: configured for MWDMA2 [1.345691] ata1.01: configured for MWDMA2 [1.346584] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.358465] scsi 0:0:1:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.370542] scsi 1:0:0:0: Direct-Access ATA QEMU HARDDISK0.9. PQ: 0 ANSI: 5 [1.392779] sd 0:0:0:0: [sda] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.396259] sd 0:0:1:0: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.396304] sd 0:0:1:0: [sdb] Write Protect is off [1.396306] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [1.396325] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.396437] sdb: sdb1 sdb2 < [1.397368] sd 1:0:0:0: [sdc] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [1.397410] sd 1:0:0:0: [sdc] Write Protect is off [1.397412] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [1.397429] sd 1:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.397534] sdc: sdb5 > [1.466413] sdc1 [1.466598] sd 0:0:0:0: [sda] Write Protect is off [1.466600] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.466623] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [1.489937] sdc2 < [1.500510] sda: [1.501850] sd 0:0:0:0: [sda] Attached SCSI disk [1.503037] sd 0:0:1:0: [sdb] Attached SCSI disk [1.520403] sdc5 > [1.521726] sd 1:0:0:0: [sdc] Attached SCSI disk [2.069791] kjournald starting. Commit interval 5 seconds [2.069821] EXT3-fs: mounted filesystem with ordered data mode. [
Bug#589989: marked as done (Kernel panic after few seconds of booting)
Your message dated Sat, 24 Jul 2010 01:03:30 +
with message-id
and subject line Bug#589989: fixed in linux-2.6 2.6.32-18
has caused the Debian Bug report #589989,
regarding Kernel panic after few seconds of booting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
589989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-15
Severity: grave
Starting from version 2.6.32-16, linux-image-2.6.32-5-{4,6}86 produce a kernel
panic a couple of
seconds after I select an image to load. That didn't happen with 2.6.32-15.
See the attached file for kernel OOPS.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc
version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=10d31aeb-3d40-44ee-900c-
9465eee6cb17 ro quiet
** Not tainted
** Kernel log:
[2.707213] usbcore: registered new interface driver usbhid
[2.707542] usbhid: v2.6:USB HID core driver
[3.911735] PM: Starting manual resume from disk
[3.911751] PM: Resume from partition 8:3
[3.911756] PM: Checking hibernation image.
[3.912202] PM: Error -22 checking image file
[3.912209] PM: Resume from disk failed.
[4.015328] EXT4-fs (sda2): mounted filesystem with ordered data mode
[6.165815] udev: starting version 160
[7.016297] input: PC Speaker as /devices/platform/pcspkr/input/input0
[7.123606] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[7.190351] ACPI: I/O resource via686a [0xc00-0xc7f] conflicts with ACPI
region TSN1 [0xc20-0xc20]
[7.190430] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[7.208377] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[7.208407] ACPI: Power Button [PWRB]
[7.212203] input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[7.212245] ACPI: Sleep Button [SLPB]
[7.212807] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[7.212820] ACPI: Power Button [PWRF]
[7.277583] processor LNXCPU:00: registered as cooling_device0
[7.433435] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[7.454012] parport_pc: VIA 686A/8231 detected
[7.454021] parport_pc: probing current configuration
[7.454048] parport_pc: Current parallel port base: 0x378
[7.454150] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[7.541561] parport_pc: VIA parallel port: io=0x378, irq=7
[7.589075] input: Logitech USB Receiver as
/devices/pci:00/:00:07.2/usb1/1-2/1-2:1.0/input/input4
[7.589785] logitech 0003:046D:C517.0001: input,hidraw0: USB HID v1.10
Keyboard [Logitech USB Receiver] on usb-:00:07.2-2/input0
[7.617529] logitech 0003:046D:C517.0002: fixing up Logitech keyboard report
descriptor
[7.645608] input: Logitech USB Receiver as
/devices/pci:00/:00:07.2/usb1/1-2/1-2:1.1/input/input5
[7.653071] logitech 0003:046D:C517.0002: input,hiddev0,hidraw1: USB HID
v1.10 Mouse [Logitech USB Receiver] on usb-:00:07.2-2/input1
[8.073373] [drm] Initialized drm 1.1.0 20060810
[8.684266] nouveau :01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level,
low) -> IRQ 11
[8.704974] [drm] nouveau :01:00.0: Detected an NV20 generation card
(0x02a5)
[8.705358] [drm] nouveau :01:00.0: Attempting to load BIOS image from
PROM
[8.831794] [drm] nouveau :01:00.0: ... appears to be valid
[8.832387] [drm] nouveau :01:00.0: BMP BIOS found
[8.832395] [drm] nouveau :01:00.0: BMP version 5.20
[8.832405] [drm] nouveau :01:00.0: Bios version 03.20.00.10
[8.832416] [drm] nouveau :01:00.0: Found Display Configuration Block
version 1.4
[8.832425] [drm] nouveau :01:00.0: No useful information in BIOS output
table; adding all possible outputs
[8.832435] [drm] nouveau :01:00.0: Probing TV encoders on I2C bus: 1
[8.872577] [drm] nouveau :01:00.0: No TV encoders found.
[8.873225] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset
0xA486
[8.873251] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset
0xAAD7
[8.873267] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset
0xA4A1
[8.873297] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset
0xAA7E
[8.873314] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset
Bug#588863: marked as done (linux-image-2.6-686: rt3090sta module requires /etc/Wireless/RT2860STA/RT2860STA.dat)
Your message dated Sat, 24 Jul 2010 01:03:30 + with message-id and subject line Bug#588863: fixed in linux-2.6 2.6.32-18 has caused the Debian Bug report #588863, regarding linux-image-2.6-686: rt3090sta module requires /etc/Wireless/RT2860STA/RT2860STA.dat to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 588863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6-686 Version: 2.6.32+27 Severity: normal The rt3090sta module loads but does not function if the file /etc/Wireless/RT2860STA/RT2860STA.dat is not present, thus breaking wifi for devices using this module. This file corresponds to the wrong kernel module name and is not distributed in any debian package. Note that the driver functions correctly if the file is present but empty. The file is reported as being optional for RT2860 but appears manditory for rt3090. Comparing rt2860/rt_profile.c and rt3090/rt_profile.c shows some differences in the implementation of RTMPReadParametersHook which is the function which reads the file. rt2860 has a retval value which does not appear to be used. The function only returns failure if it cannot allocate a buffer to read the ini file and its parameters. If it doesn't open the file the meat of the function is skipped and the function returns NDIS_STATUS_SUCCESS anyway. rt3090 initializes retval to NDIS_STATUS_FAILURE. This is unchanged if there is an error opening the file and is returned at the end of the function. This propogates through to abort the module. Output from dmesg when the file is not present: [ 26.470395] RX DESC f6496000 size = 2048 [ 26.471058] <-- RTMPAllocTxRxRingMemory, Status=0 [ 26.475292] RtmpOSFileOpen(): Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 26.475305] Open file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed! [ 26.475314] 1. Phy Mode = 0 [ 26.475319] ERROR!!! NICReadRegParameters failed, Status[=0x0001] [ 26.480576] !!! rt28xx Initialized fail !!! Output from dmesg when the file is present and empty: [ 557.889591] <-- RTMPAllocTxRxRingMemory, Status=0 [ 557.894120] Read file "/etc/Wireless/RT2860STA/RT2860STA.dat" failed(errCode=0)! [ 557.894147] 1. Phy Mode = 0 [ 557.894154] 2. Phy Mode = 0 [ 557.894162] NVM is Efuse and its size =2d[2d0-2fc] [ 557.896031] 3. Phy Mode = 0 [ 557.920012] MCS Set = 00 00 00 00 00 [ 558.116167] RTMPFilterCalibration - can't find a valid value, loopcnt=102 stop calibrating< rt28xx_init, Status=0 [ 558.117827] 0x1300 = 00073200 [ 558.117875] AUX_CTRL = 0x c02 [ 558.117884] Read AUX_CTRL = 0xc02 [ 558.117891] Write AUX_CTRL = 0x1c02 [ 558.117898] OSC_CTRL = 0x3ff11 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.32-5-686 2.6.32-15 Linux 2.6.32 for modern PCs linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.32-18 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-18_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-18_all.deb linux-2.6_2.6.32-18.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-18.diff.gz linux-2.6_2.6.32-18.dsc to main/l/linux-2.6/linux-2.6_2.6.32-18.dsc linux-base_2.6.32-18_all.deb to main/l/linux-2.6/linux-base_2.6.32-18_all.deb linux-doc-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-18_all.deb linux-manual-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-18_all.deb linux-patch-debian-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-18_all.deb linux-source-2.6.32_2.6.32-18_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-18_all.deb linux-support-2.6.32-5_2.6.32-18_all.deb to main/l/linux-2.6/linux-support-2.6.32-5_2.6.32-18_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 588...@bugs.debian.org, and the maintainer will reopen the bug
