[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/505375 Title: (lucid) iwlagn doesn't work if much RAM is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
Seeing this with 2.6.34-5-generic #14~lucid1-Ubuntu SMP x86_64 GNU/Linux kernel, when RAM was used up by Disk Usage Analyzer Aug 22 20:23:25 hprem-lnx kernel: [694542.574056] swapper: page allocation failure. order:1, mode:0x4020 Aug 22 20:23:25 hprem-lnx kernel: [694542.574067] Pid: 0, comm: swapper Tainted: P 2.6.34-5-generic #14~lucid1-Ubuntu Aug 22 20:23:25 hprem-lnx kernel: [694542.574074] Call Trace: Aug 22 20:23:25 hprem-lnx kernel: [694542.574079] IRQ [810fa4e3] __alloc_pages_slowpath+0x583/0x590 Aug 22 20:23:25 hprem-lnx kernel: [694542.574105] [810fa64e] __alloc_pages_nodemask+0x15e/0x1a0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574117] [8112d837] alloc_pages_current+0x87/0xd0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574164] [a01aa76a] iwl_rx_allocate+0x12a/0x290 [iwlcore] Aug 22 20:23:25 hprem-lnx kernel: [694542.574189] [a01acbfb] iwl_rx_replenish_now+0x1b/0x30 [iwlcore] Aug 22 20:23:25 hprem-lnx kernel: [694542.574208] [a0205ec0] iwl_rx_handle+0x360/0x400 [iwlagn] Aug 22 20:23:25 hprem-lnx kernel: [694542.574224] [a0207caf] iwl_irq_tasklet_legacy+0x20f/0x5c0 [iwlagn] Aug 22 20:23:25 hprem-lnx kernel: [694542.574234] [81063705] tasklet_action+0xd5/0xe0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574242] [810648c9] __do_softirq+0xb9/0x1f0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574252] [810be660] ? handle_IRQ_event+0x60/0x170 Aug 22 20:23:25 hprem-lnx kernel: [694542.574263] [8100b01c] call_softirq+0x1c/0x30 Aug 22 20:23:25 hprem-lnx kernel: [694542.574271] [8100cc95] do_softirq+0x65/0xa0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574278] [81064785] irq_exit+0x85/0x90 Aug 22 20:23:25 hprem-lnx kernel: [694542.574289] [8156d605] do_IRQ+0x75/0xf0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574311] [81567713] ret_from_intr+0x0/0x11 Aug 22 20:23:25 hprem-lnx kernel: [694542.574316] EOI [81310176] ? acpi_idle_enter_simple+0x117/0x14b Aug 22 20:23:25 hprem-lnx kernel: [694542.574335] [8131016f] ? acpi_idle_enter_simple+0x110/0x14b Aug 22 20:23:25 hprem-lnx kernel: [694542.574347] [81455a27] cpuidle_idle_call+0xa7/0x140 Aug 22 20:23:25 hprem-lnx kernel: [694542.574356] [81008da3] cpu_idle+0xb3/0x110 Aug 22 20:23:25 hprem-lnx kernel: [694542.574365] [8154f24e] rest_init+0x7e/0x90 Aug 22 20:23:25 hprem-lnx kernel: [694542.574376] [81b06e5f] start_kernel+0x37b/0x384 Aug 22 20:23:25 hprem-lnx kernel: [694542.574385] [81b06341] x86_64_start_reservations+0x12c/0x130 Aug 22 20:23:25 hprem-lnx kernel: [694542.574394] [81b0643f] x86_64_start_kernel+0xfa/0x109 Aug 22 20:23:25 hprem-lnx kernel: [694542.574399] Mem-Info: Aug 22 20:23:25 hprem-lnx kernel: [694542.574403] Node 0 DMA per-cpu: Aug 22 20:23:25 hprem-lnx kernel: [694542.574410] CPU0: hi:0, btch: 1 usd: 0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574416] CPU1: hi:0, btch: 1 usd: 0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574421] Node 0 DMA32 per-cpu: Aug 22 20:23:25 hprem-lnx kernel: [694542.574428] CPU0: hi: 186, btch: 31 usd: 175 Aug 22 20:23:25 hprem-lnx kernel: [694542.574434] CPU1: hi: 186, btch: 31 usd: 136 Aug 22 20:23:25 hprem-lnx kernel: [694542.574447] active_anon:282957 inactive_anon:95010 isolated_anon:185 Aug 22 20:23:25 hprem-lnx kernel: [694542.574450] active_file:9 inactive_file:19437 isolated_file:23 Aug 22 20:23:25 hprem-lnx kernel: [694542.574453] unevictable:28 dirty:0 writeback:175 unstable:0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574455] free:3180 slab_reclaimable:40760 slab_unreclaimable:8507 Aug 22 20:23:25 hprem-lnx kernel: [694542.574458] mapped:18711 shmem:4827 pagetables:8594 bounce:0 Aug 22 20:23:25 hprem-lnx kernel: [694542.574473] Node 0 DMA free:7896kB min:44kB low:52kB high:64kB active_anon:80kB inactive_anon:2740kB active_file:620kB inactive_file:180kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15700kB mlocked:0kB dirty:0kB writeback:0kB mapped:600kB shmem:24kB slab_reclaimable:3256kB slab_unreclaimable:76kB kernel_stack:0kB pagetables:4kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Aug 22 20:23:25 hprem-lnx kernel: [694542.574498] lowmem_reserve[]: 0 1971 1971 1971 Aug 22 20:23:25 hprem-lnx kernel: [694542.574509] Node 0 DMA32 free:4824kB min:5656kB low:7068kB high:8484kB active_anon:1131748kB inactive_anon:377300kB active_file:88296kB inactive_file:77568kB unevictable:112kB isolated(anon):740kB isolated(file):92kB present:2018672kB mlocked:112kB dirty:0kB writeback:700kB mapped:74244kB shmem:19284kB slab_reclaimable:159784kB slab_unreclaimable:33952kB kernel_stack:2776kB pagetables:34372kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Aug 22 20:23:25 hprem-lnx kernel: [694542.574536] lowmem_reserve[]: 0 0 0 0 Aug 22
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
There's no possible workaround or anything for this? To somehow let the driver reserve a huge chunk of RAM or whatever. It's driving me beyond crazy :( -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
I've the same problem. When copying large files from an external usb hdd the system hangs. -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
And it's still here in 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux and keeps on killing the wifi when doing something like copying files to an external hdd... -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
Yep... this affects me too. It's incredibly annoying. Do some disk intensive things like unpack archives and RAM cache will fill up, crashing the driver. -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
Confirmed - still occurs in Lucid. # uname -a Linux encahl 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
Still present in 2.6.32-21-generic -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
Still an issue with the new kernel: mue...@xbox:~$ uname -a Linux xbox 2.6.32-10-generic #14-Ubuntu SMP Thu Jan 7 17:38:08 UTC 2010 x86_64 GNU/Linux mue...@xbox:~$ some dmsg: [154159.921362] PM: Entering mem sleep [154159.921377] Suspending console(s) (use no_console_suspend to debug) [154160.000115] sd 0:0:0:0: [sda] Synchronizing SCSI cache [154160.130153] sd 0:0:0:0: [sda] Stopping disk [154161.303395] ACPI handle has no context! [154161.303404] sdhci-pci :05:00.2: PCI INT C disabled [154161.303412] ACPI handle has no context! [154161.325171] ACPI handle has no context! [154161.420223] ata5: port disabled. ignoring. [154161.420324] ata_piix :00:1f.1: PCI INT C disabled [154161.420341] ehci_hcd :00:1d.7: PCI INT D disabled [154161.420356] uhci_hcd :00:1d.1: PCI INT B disabled [154161.420370] uhci_hcd :00:1d.0: PCI INT A disabled [154161.420374] pciehp :00:1c.1:pcie04: pciehp_suspend ENTRY [154161.420378] pciehp :00:1c.0:pcie04: pciehp_suspend ENTRY [154161.530597] HDA Intel :00:1b.0: PCI INT B disabled [154161.550123] ehci_hcd :00:1a.7: PCI INT C disabled [154161.550139] uhci_hcd :00:1a.1: PCI INT B disabled [154161.550160] uhci_hcd :00:1a.0: PCI INT A disabled [154161.552792] e1000e :00:19.0: PCI INT A disabled [154161.552803] e1000e :00:19.0: PME# enabled [154161.552810] e1000e :00:19.0: wake-up capability enabled by ACPI [154161.600200] i915 :00:02.0: power state changed by ACPI to D3 [154161.600259] PM: suspend devices took 1.680 seconds [154161.640096] ehci_hcd :00:1d.7: power state changed by ACPI to D3 [154161.660085] uhci_hcd :00:1d.0: power state changed by ACPI to D3 [154161.700085] ehci_hcd :00:1a.7: power state changed by ACPI to D3 [154161.770074] uhci_hcd :00:1a.1: power state changed by ACPI to D3 [154161.870077] ACPI: Preparing to enter system sleep state S3 [154162.240020] Disabling non-boot CPUs ... [154162.240045] CPU0 attaching NULL sched-domain. [154162.240049] CPU1 attaching NULL sched-domain. [154162.320027] CPU0 attaching NULL sched-domain. [154162.430037] CPU 1 is now offline [154162.430041] SMP alternatives: switching to UP code [154162.439564] CPU1 is down [154162.439617] Extended CMOS year: 2000 [154162.439617] Back to C! [154162.439617] CPU0: Thermal monitoring enabled (TM2) [154162.439617] Extended CMOS year: 2000 [154162.439617] Enabling non-boot CPUs ... [154162.440135] SMP alternatives: switching to SMP code [154162.448157] Booting processor 1 APIC 0x1 ip 0x6000 [154162.439179] Initializing CPU#1 [154162.439179] Calibrating delay using timer specific routine.. 3192.14 BogoMIPS (lpj=15960712) [154162.439179] CPU: L1 I cache: 32K, L1 D cache: 32K [154162.439179] CPU: L2 cache: 4096K [154162.439179] CPU 1/0x1 - Node 0 [154162.439179] CPU: Physical Processor ID: 0 [154162.439179] CPU: Processor Core ID: 1 [154162.439179] CPU1: Thermal monitoring enabled (TM2) [154162.600139] CPU1: Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz stepping 0b [154162.600211] CPU0 attaching NULL sched-domain. [154162.630047] CPU0 attaching sched-domain: [154162.630050] domain 0: span 0-1 level MC [154162.630053] groups: 0 1 [154162.630058] CPU1 attaching sched-domain: [154162.630060] domain 0: span 0-1 level MC [154162.630063] groups: 1 0 [154162.630657] CPU1 is up [154162.631381] ACPI: Waking up from system sleep state S3 [154163.460178] i915 :00:02.0: restoring config space at offset 0x1 (was 0x97, writing 0x900407) [154163.460209] pci :00:02.1: restoring config space at offset 0x1 (was 0x90, writing 0x97) [154163.460388] uhci_hcd :00:1a.0: restoring config space at offset 0x1 (was 0x285, writing 0x281) [154163.630075] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [154163.630139] uhci_hcd :00:1a.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [154163.630230] ehci_hcd :00:1a.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [154163.630353] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100102) [154163.630486] pcieport :00:1c.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100507) [154163.630659] pcieport :00:1c.1: restoring config space at offset 0x1 (was 0x100107, writing 0x100507) [154163.650086] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [154163.650150] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x285, writing 0x281) [154163.650227] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [154163.650327] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [154163.650433] pci :00:1e.0: restoring config space at offset 0x1 (was 0x15, writing 0x17) [154163.650711] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [154163.650967] iwlagn :03:00.0:
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
** Tags added: karmic -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Triaged -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505375] Re: (lucid) iwlagn doesn't work if much RAM is used
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/37667764/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/37667766/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/37667771/BootDmesg.txt ** Attachment added: CRDA.txt http://launchpadlibrarian.net/37667775/CRDA.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/37667776/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/3766/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/37667778/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37667779/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/37667780/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/37667781/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/37667782/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/37667783/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/37667785/ProcCpuinfo.txt ** Attachment added: ProcEnviron.txt http://launchpadlibrarian.net/37667786/ProcEnviron.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/37667787/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/37667788/ProcModules.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/37667789/RfKill.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/37667790/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/37667791/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/37667792/WifiSyslog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37667793/XsessionErrors.txt -- (lucid) iwlagn doesn't work if much RAM is used https://bugs.launchpad.net/bugs/505375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
