Bug#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.
Still failing with latest 3.10-1 linux image... -- 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/calurrgcoyk5enb7h3l3xgyvuvraxqts-8gv-wmg-upndnmd...@mail.gmail.com
Bug#711585: [linux-image-3.9-1-loongson-2f] linux 3.9.4-1 for loongson-2f doesn't halt/reboot/suspend-disk.
Package: linux-image-3.9-1-loongson-2f Version: 3.9.4-1 Severity: Important When rebooting, halting or suspending to disk on a mini-pc with loongson-2f, it just hangs, printing a weird trace. Fortunately dmessage kept such trace: Jun 7 23:34:30 mini-1 kernel: [2.18] EXT4-fs (sda6): write access will be enabled during recovery Jun 7 23:34:30 mini-1 kernel: [2.908000] EXT4-fs (sda6): orphan cleanup on readonly fs Jun 7 23:34:30 mini-1 kernel: [2.908000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 888392 Jun 7 23:34:30 mini-1 kernel: [2.924000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 889643 Jun 7 23:34:30 mini-1 kernel: [2.924000] EXT4-fs (sda6): ext4_orphan_cleanup: deleting unreferenced inode 904421 Jun 7 23:34:30 mini-1 kernel: [2.936000] EXT4-fs (sda6): 3 orphan inodes deleted Jun 7 23:34:30 mini-1 kernel: [2.94] EXT4-fs (sda6): recovery complete Jun 7 23:34:30 mini-1 kernel: [3.072000] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Jun 7 23:34:30 mini-1 kernel: [3.076000] VFS: Mounted root (ext4 filesystem) readonly on device 8:6. Jun 7 23:34:30 mini-1 kernel: [3.076000] Freeing unused kernel memory: 320k freed Jun 7 23:34:30 mini-1 kernel: [6.764000] cpufreq: Loongson-2F CPU frequency driver. Jun 7 23:34:30 mini-1 kernel: [6.812000] CPU 0 Unable to handle kernel paging request at virtual address c00106c8, epc == 8051f1c4, ra == 8051d36c Jun 7 23:34:30 mini-1 kernel: [6.816000] Oops[#1]: Jun 7 23:34:30 mini-1 kernel: [6.816000] Cpu 0 Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 0 : cfff c00106c8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 4 : 9800be421000 807b Jun 7 23:34:30 mini-1 kernel: [6.816000] $ 8 : 98000136e798 Jun 7 23:34:30 mini-1 kernel: [6.816000] $12 : 8047d688 803192e8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $16 : 9800be421000 8081cc40 8081cc30 806f90b8 Jun 7 23:34:30 mini-1 kernel: [6.816000] $20 : 9800be764000 9800be6afe70 771b8000 4000 Jun 7 23:34:30 mini-1 kernel: [6.816000] $24 : 770c7ce4 Jun 7 23:34:30 mini-1 kernel: [6.816000] $28 : 9800be6ac000 9800be6afd50 00afc978 8051d36c Jun 7 23:34:30 mini-1 kernel: [6.816000] Hi: e147d0b6 Jun 7 23:34:30 mini-1 kernel: [6.816000] Lo: 748f7125 Jun 7 23:34:30 mini-1 kernel: [6.816000] epc : 8051f1c4 dev_uevent+0xe0/0x1a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] Not tainted Jun 7 23:34:30 mini-1 kernel: [6.816000] ra: 8051d36c show_uevent+0xdc/0x178 Jun 7 23:34:30 mini-1 kernel: [6.816000] Status: 100044e3 KX SX UX KERNEL EXL IE Jun 7 23:34:30 mini-1 kernel: [6.816000] Cause : 10008008 Jun 7 23:34:30 mini-1 kernel: [6.816000] BadVA : c00106c8 Jun 7 23:34:30 mini-1 kernel: [6.816000] PrId : 6303 (ICT Loongson-2) Jun 7 23:34:30 mini-1 kernel: [6.816000] Modules linked in: usb_common Jun 7 23:34:30 mini-1 kernel: [6.816000] Process udevd (pid: 246, threadinfo=9800be6ac000, task=9800be67a6b8, tls=771fc2c0) Jun 7 23:34:30 mini-1 kernel: [6.816000] Stack : 8081cc40 806f90b8 9800be421000 Jun 7 23:34:30 mini-1 kernel: [6.816000] 8081cc40 8051d36c 9800be342980 80867818 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be0f5550 8081cc40 806f90b8 9800be3429a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be6afe70 8051dac0 00afc978 802c6778 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be342980 80387a04 9800be6afe70 Jun 7 23:34:30 mini-1 kernel: [6.816000] 770785e0 4000 9800be75cec0 771b8000 Jun 7 23:34:30 mini-1 kernel: [6.816000] 9800be6afe70 770785e0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 7f8e97d8 803190c0 0003 9800be75cec0 Jun 7 23:34:30 mini-1 kernel: [6.816000] 771b8000 000a 80319338 Jun 7 23:34:30 mini-1 kernel: [6.816000] 4000 000a Jun 7 23:34:30 mini-1 kernel: [6.816000] ... Jun 7 23:34:30 mini-1 kernel: [6.816000] Call Trace: Jun 7 23:34:30 mini-1 kernel: [6.816000] [] dev_uevent+0xe0/0x1a0 Jun 7 23:34:30 mini-1 kernel: [6.816000] [] show_uevent+0xdc/0x178 Jun 7 23:34:30 mini-1 kernel: [6.816000] [] dev_attr_show+0x30
Bug#710852: [linux-image-3.8-2-loongson-2f] usb ethernet adapter MosChip MCS7830 hangs after working fine for a while
Additional info... The beginnign of the kernel log, not reported before, shows: Jun 2 09:00:20 mini-0 kernel: [55560.272000] UDP: bad checksum. From 213.157.218.54:0 to 186.176.90.47:0 ulen 1430 Jun 2 09:55:57 mini-0 kernel: [58896.588000] UDP: bad checksum. From 218.95.142.2:0 to 186.176.90.47:0 ulen 1430 Jun 2 11:22:06 mini-0 kernel: [64065.68] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:44352 ulen 170 Jun 2 14:16:34 mini-0 kernel: [74533.544000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:49396 ulen 136 Jun 2 14:16:40 mini-0 kernel: [74539.976000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:47340 ulen 187 Jun 2 14:17:02 mini-0 kernel: [74561.496000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:52383 ulen 154 Jun 2 14:34:16 mini-0 kernel: [75596.068000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:33701 ulen 126 Jun 2 16:26:34 mini-0 kernel: [82334.04] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:54904 ulen 125 Jun 2 16:43:35 mini-0 kernel: [83355.312000] UDP: bad checksum. From 186.32.0.99:53 to 186.176.90.47:52201 ulen 282 Jun 2 16:57:04 mini-0 kernel: [84163.824000] [ cut here ] Jun 2 16:57:04 mini-0 kernel: [84163.824000] WARNING: at /build/buildd-linux_3.8.13-1-mipsel-XrCEF3/linux-3.8.13/net/sched/sch_generic.c:254 dev_watchdog+0x180/0x2b0() Jun 2 16:57:04 mini-0 kernel: [84163.824000] NETDEV WATCHDOG: eth1 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out Jun 2 16:57:04 mini-0 kernel: [84163.828000] Modules linked in: cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave nfsd auth_rpcgss nfs_acl nfs lockd dns_resolver fscache sunrpc ipt_MASQUERADE ipt_REJECT xt_tcpudp xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables x_tables autofs4 loop fuse snd_cs5535audio snd_ac97_codec snd_pcm_oss snd_mixer_oss mcs7830 usbnet snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq r8169 rtc_cmos snd_seq_device mii ehci_pci snd_timer ohci_hcd ehci_hcd snd loongson2_cpufreq usbcore soundcore usb_common ac97_bus Jun 2 16:57:04 mini-0 kernel: [84163.84] Call Trace: Jun 2 16:57:04 mini-0 kernel: [84163.84] [] dump_stack+0x8/0x40 Jun 2 16:57:04 mini-0 kernel: [84163.84] [] warn_slowpath_common+0x78/0xa4 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [] warn_slowpath_fmt+0x38/0x50 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [] dev_watchdog+0x180/0x2b0 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [] call_timer_fn+0x84/0x164 Jun 2 16:57:04 mini-0 kernel: [84163.844000] [] run_timer_softirq+0x20c/0x2a4 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [] __do_softirq+0x124/0x288 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [] do_softirq+0x44/0x68 Jun 2 16:57:04 mini-0 kernel: [84163.848000] [] irq_exit+0x4c/0xcc Jun 2 16:57:04 mini-0 kernel: [84163.852000] [] ret_from_irq+0x0/0x4 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [] arch_local_irq_save+0x0/0x28 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [] rcu_idle_exit+0x1c/0xb4 Jun 2 16:57:04 mini-0 kernel: [84163.852000] [] cpu_idle+0x68/0x80 Jun 2 16:57:04 mini-0 kernel: [84163.856000] [] start_kernel+0x470/0x49c Jun 2 16:57:04 mini-0 kernel: [84163.856000] Jun 2 16:57:04 mini-0 kernel: [84163.856000] ---[ end trace 18e9d7175962fe44 ]--- Jun 2 17:28:23 mini-0 kernel: [0.00] Initializing cgroup subsys cpuset Jun 2 17:28:23 mini-0 kernel: [0.00] Initializing cgroup subsys cpu Jun 2 17:28:23 mini-0 kernel: [0.00] Linux version 3.8-2-loongson-2f (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-3) ) #1 Debian 3.8.13-1 Perhaps the important part is the netdev watchdog. I performed several pings to external URLs to see if I had external connection, but none of the pings was responded back, all packets were reported lost. That's how I realized the network device was hanging, or no longer working... -- Javier. -- 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/CALUrRGfo7WEYM2pR0qoQ55aKKoDc8W0gZU1Uz=89ngl7jw7...@mail.gmail.com
Bug#710852: [linux-image-3.8-2-loongson-2f] usb ethernet adapter MosChip MCS7830 hangs after working fine for a while
Package: src:linux Version: 3.8.13-1 Severity: important Tags: upstream On loongson-2f mini-pc running under unstable, I upgraded the linux image from old linux-image-3.2.0-4-loongson-2f to newer linux-image-3.8-2-loongson-2f. I use this mini-pc as a gateway 24/7, so it is to be up all the time. However after the upgrade, the MosChip MCS7830 ethernet usb adaptor starts working great after booting, but after a while (haven't identified how much), it stops working, with no message about it. I can do ifdown, but I can't complete ifup successfully given the DHCP process doesn't get response from the DHCP server (provider), given the usb device is hanging. Attempting to modprobe -r usbnet, doesn't work, the module is reported busy, even fails to remove with "-f". The only work around is to reboot. As I need the gateway up at all times, I'm going back to old 3.2.0-4 version. However the idea is to keep the machine running with more up to date kernels... -- Package-specific info: ** Version: Linux version 3.8-2-loongson-2f (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-3) ) #1 Debian 3.8.13-1 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 ro video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Kernel log: [1.964000] ata1.00: 312581808 sectors, multi 16: LBA48 [1.976000] ata1.00: configured for UDMA/100 [1.976000] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM160HI HH10 PQ: 0 ANSI: 5 [1.98] ata2: port disabled--ignoring [1.98] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) [1.984000] sd 0:0:0:0: [sda] Write Protect is off [1.984000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.984000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.148000] sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 > [2.152000] sd 0:0:0:0: [sda] Attached SCSI disk [2.152000] PM: Hibernation image partition 8:5 present [2.152000] PM: Looking for hibernation image. [2.152000] PM: Image not found (code -22) [2.152000] PM: Hibernation image not present or could not be loaded. [2.152000] registered taskstats version 1 [2.156000] /build/buildd-linux_3.8.13-1-mipsel-XrCEF3/linux-3.8.13/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [2.176000] EXT4-fs (sda6): couldn't mount as ext3 due to feature incompatibilities [2.176000] EXT4-fs (sda6): couldn't mount as ext2 due to feature incompatibilities [2.208000] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [2.208000] VFS: Mounted root (ext4 filesystem) readonly on device 8:6. [2.212000] Freeing unused kernel memory: 288k freed [5.332000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [5.364000] rtc0: alarms up to one day, 114 bytes nvram [5.412000] cpufreq: Loongson-2F CPU frequency driver. [5.56] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [5.576000] r8169 :00:06.0 (unregistered net_device): not PCI Express [5.60] usbcore: registered new interface driver usbfs [5.608000] r8169 :00:06.0 eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:04:b6, XID 1800 IRQ 36 [5.612000] r8169 :00:06.0 eth0: jumbo features [frames: 7152 bytes, tx checksumming: ok] [5.624000] usbcore: registered new interface driver hub [5.652000] usbcore: registered new device driver usb [5.684000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [5.70] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.704000] ohci_hcd :00:0e.4: setting latency timer to 64 [5.704000] ohci_hcd :00:0e.4: OHCI Host Controller [5.712000] ehci-pci: EHCI PCI platform driver [5.724000] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 1 [5.74] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [5.836000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [5.84] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.844000] usb usb1: Product: OHCI Host Controller [5.848000] usb usb1: Manufacturer: Linux 3.8-2-loongson-2f ohci_hcd [5.852000] usb usb1: SerialNumber: :00:0e.4 [5.864000] hub 1-0:1.0: USB hub found [5.868000] hub 1-0:1.0: 4 ports detected [5.872000] ehci-pci :00:0e.5: setting latency timer to 64 [5.876000] ehci-pci :00:0e.5: EHCI Host Controller [5.912000] ehci-pci :00:0e.5: new USB bus registered, assigned bus number 2 [5.92] ehci-pci :00:0e.5: irq 11, io mem 0x50071000 [5.944000] ehci-pci :00:0e.5: USB 0.0 started, EHCI 1.00 [5.96] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [5.964000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.968000] usb usb2: Product: EHCI Host Controller [5.972
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
On 5/19/12, Jonathan Nieder wrote: > Hi again, > > Jonathan Nieder wrote: >> Javier Vasquez wrote: > >>> MemTotal: 514432 kB >>> SwapTotal: 2096408 kB > [...] >>> [ 92.796017] PM: Need to copy 66237 pages >>> [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: >>> 64647 >>> [ 92.796017] PM: Not enough free memory >>> [ 92.796017] PM: Error -12 creating hibernation image >> >> Yeah, that looks broken. > > Ping. Do you still have access to a system reproducing this bug? Are > you still interested in pursuing it? > > If not, that's fine, but please do let us know so we can plan > accordingly. > > Thanks, > Jonathan > I don't have access to the laptop. I hoped I could set my hands on it, but I haven't... So, if later on I face the same problems, and you close this one, I'll file a different one, :-) BTW, if I recall correctly setting to 0 /sys/power/image_size helped prevent the issue... Thanks, Javier. -- Javier. -- 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/CALUrRGfS7rm6FUud-Y=-NLROoXRvCk6Hj+AjYnxxGvj=hx3...@mail.gmail.com
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
After a couple of upgrades (two have ahppened) on linux-image (without version change), now I'm getting the connections I was missing. As I said the linux-image package has been upgrade twice, but still keeping same version, so I couldn't notice what change unfortunately, so if you look at packages versions, they're still the same: % aptitude search '~i' | 'grep' inux-image i linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) Thanks, -- Javier. -- 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/CALUrRGfEwqofx+PVg7HNJPqv=y1iqgzwrfujcqb064ipahz...@mail.gmail.com
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
One clarification on the msn connection issue. I can connect on the gateway. I can not connect on the boxes connected to the gateway, :-) So this to re-enforce the idea it's something in the forwarding, or filtering provided by iptables which seems broken... Just in case this was not clear... -- 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/CALUrRGep14DVFCMDsQyucO1Np_-R8Sk=ams+3eu4esqs5nx...@mail.gmail.com
Bug#636417: linux-image-3.0.0-1-loongson-2f: loongson-2f linux kernel in stock compiled with ipv6 as module, which conflicts with procps
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Tags: ipv6 *** Please type your report below this line *** The loongson-2f stock kernel on debian comes with ipv6 compiled as a module. However that's not expected by procps. See: /usr/share/doc/procps/README.Debian ... ipv6 sysctl keys Modern Debian kernel packages have the IPv6 module compiled in by default. This means that the /proc/sys/net/ipv6 directory exists when the procps startup script runs. However if you make your own kernel then you may make ipv6 a module and get a race condition between the netbase and procps startup scripts. This is because netbase, by default, causes ipv6 module to be loaded but they don't (and cannot) depend on each-other. The solution is to either: - Not put ipv6 keys into /etc/sysctl.d/* or /etc/sysctl.conf - Compile the ipv6 module into the kernel - Load the module early by putting ipv6 into /etc/modules - Make a init script dependency by adding netbase to the Required-Start line in /etc/init.d/procps ... Tha clearly states the debian stock kernels should have no problem given that they come with ipv6 built inside. However loongson-2f stock kernels don't comply with this. This causes failures like: error: "net.ipv6.bindv6only" is an unknown key Work around is really simple, just to add ipv6 into /etc/modules, however that shouldn't be the case for stock kernels according to procps documentation, and also a bug filed for that purpose last year (closed already): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507788 Any ways, just the loongson-2f kernel not being compliant with procps suppositions, :-) Thanks, Javier. -- Package-specific info: ** Version: Linux version 3.0.0-1-loongson-2f (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 Mon Jul 25 21:17:28 UTC 2011 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [2.088000] PM: Hibernation image partition 8:5 present [2.088000] PM: Looking for hibernation image. [2.092000] PM: Image not found (code -22) [2.092000] PM: Hibernation image not present or could not be loaded. [2.092000] registered taskstats version 1 [2.092000] /build/buildd-linux-2.6_3.0.0-1-mipsel-TFQf1R/linux-2.6-3.0.0/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [2.096000] Initializing network drop monitor service [2.12] EXT3-fs: barriers not enabled [2.128000] kjournald starting. Commit interval 5 seconds [2.128000] EXT3-fs (sda6): mounted filesystem with ordered data mode [2.128000] VFS: Mounted root (ext3 filesystem) readonly on device 8:6. [2.132000] Freeing unused kernel memory: 240k freed [4.312000] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [4.312000] r8169 :00:06.0: (unregistered net_device): no PCI Express capability [4.312000] r8169 :00:06.0: eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:0f:62, XID 1800 IRQ 36 [4.48] cpufreq: Loongson-2F CPU frequency driver. [4.54] usbcore: registered new interface driver usbfs [4.556000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [4.604000] usbcore: registered new interface driver hub [4.612000] rtc0: alarms up to one day, 114 bytes nvram [4.644000] usbcore: registered new device driver usb [4.688000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [4.744000] PCI: Setting latency timer of device :00:0e.5 to 64 [4.744000] ehci_hcd :00:0e.5: EHCI Host Controller [4.776000] ehci_hcd :00:0e.5: new USB bus registered, assigned bus number 1 [4.828000] ehci_hcd :00:0e.5: irq 11, io mem 0x50071000 [4.848000] ehci_hcd :00:0e.5: USB 0.0 started, EHCI 1.00 [4.888000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [4.892000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.896000] usb usb1: Product: EHCI Host Controller [4.90] usb usb1: Manufacturer: Linux 3.0.0-1-loongson-2f ehci_hcd [4.904000] usb usb1: SerialNumber: :00:0e.5 [4.924000] hub 1-0:1.0: USB hub found [4.944000] hub 1-0:1.0: 4 ports detected [4.996000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.004000] PCI: Enabling device :00:0e.4 ( -> 0002) [5.036000] PCI: Setting latency timer of device :00:0e.4 to 64 [5.036000] ohci_hcd :00:0e.4: OHCI Host Controller [5.044000] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 2 [5.064000] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [5.156000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.16] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.164000] usb usb2: Product: OHCI Host Controller [
Bug#636170: Fwd: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
Just an upgrade. When trying to install the prior 2.6.39-2 kernel I tried a kernel package that was not necessary. After fixing that, the look fro kernel packages installed look this way: % aptitude search '~i' | 'grep' linux-image i linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) This doesn't affect at all, what has been exposed. Actually with that little mess my 2.6.39-2 kernel was working correctly... Thanks, -- Javier -- 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/calurrgdy1mcuuhoef+bw6+nfydz7z-tydl3xotoyh8c3tsu...@mail.gmail.com
Bug#636170: linux-image-3.0.0-1-loongson-2f doesn't allow some connections through iptables
Package: linux-2.6 Version: 3.0.0-1 Severity: important *** Please type your report below this line *** I'm using a lemote mini-pc as my gateway through simple iptables configuration. I use debian unstable. With yesterday upgrade which updated linux kernel to 3.0.0-1 and iptables as well, my gateway broke. % cat /var/log/aptitude ... [UPGRADE] iptables 1.4.11.1-3 -> 1.4.12-1 ... [UPGRADE] linux-image-loongson-2f 2.6.39+35.1 -> 3.0.0+39 ... What got broken is some connection from internal boxes connected to the gateway to some outside places external to the gateway. For example, trying to upgrade again Today from the gateway had no problem at all. However trying to upgrade from an internal box was hard, both in the sense that getting the headers took way longer than in the gateway, and that when the time came for safe-upgrade and after downloading the packages, apt-listbugs just failed indicating it couldn't connect to extract the bug information. To get to upgrade on the internal boxes, the apt-listbugs part of the process was canceled. I also connect to a msn account through pidgin. But since the upgrade until I installed back 2.6.39-2 linux kernel, I could NOT connect at all to msn. To get msn workign back, I just had to install old prior working kernel 2.6.39-2. The prior confirms to me that actually the problem was not with iptables, since I didn't have to even try downgrading it. Just by installing 2.6.39-2 linux kernel version for loongson-2f worked out great. Notice that there are several changes in the kernel config files (under boot) between 2.6.39-2 and 3.0.0-1, however I couldn't appreciate any significant variation that could have affected the iptables behavior. My iptables script that is under: /etc/network/if-up.d/00_gateway It's pretty simple: ++ # delete all existing rules and clean up. iptables -P INPUT ACCEPT iptables -P FORWARD ACCEPT iptables -P OUTPUT ACCEPT iptables -F iptables -t nat -F iptables -t mangle -F iptables -X # Always accept loopback traffic iptables -A INPUT -i lo -j ACCEPT # Allow established connections, and those not coming from the outside iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -m state --state NEW ! -i ppp0 -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -i ppp0 -o eth0 -j ACCEPT # Allow outgoing connections from the LAN side. iptables -A FORWARD -i eth0 -o ppp0 -j ACCEPT # Masquerade. iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE # Don't forward from the outside to the inside. iptables -A FORWARD -i ppp0 -o ppp0 -j REJECT ++ That's it, pretty simple as well... Also I'm using an usb NIC to connect outside the gateway through ppp: /etc/network/interfaces ++ auto lo iface lo inet loopback # The internal LAN on embedded NIC auto eth0 iface eth0 inet static pre-up /sbin/ethtool -K eth0 rx off post-up /sbin/ethtool -K eth0 rx off address 192.168.2.1 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 # The external LAN USB NIC auto eth1 iface eth1 inet manual ## The dsl-provider through PPPoE auto dsl-provider iface dsl-provider inet ppp pre-up /sbin/ifconfig eth1 up # line maintained by pppoeconf provider dsl-provider post-down /sbin/ifconfig eth1 down ++ I didn't have the post-up command before for the built-in NIC, but one of my initial thoughs was that perhaps one of the changes was related to that, but in reality it was not the issue. One needs to disable hardware crc sum calculation on the realtek built-in card otherwise the NIC transports wrong packages... Again this seems not to be the issue though, since the setting (/sbin/ethtool -K eth0 rx off) is working out in the prior kernel, and has no observed effect in the current one. So I can't really use at this moment linux kernel 3.0.0-1 on my gateway. My work around was to use prior one 2.6.39-2 still present on testing, and with the work around the problems go away, :-) Not sure what changes in the linux kernel for loongson-2f cause the new misbehavior, but it's sure the kernel is the one preventing my connections from internal boxes connected to my gateway... % aptitude search '~i' | 'grep' linux-image u linux-image-2.6-loongson-2f - Linux for Loongson 2F (dummy package) i linux-image-2.6.39-2-loongson-2 - Linux 2.6.39 for Loongson 2F i A linux-image-3.0.0-1-loongson-2f - Linux 3.0.0 for Loongson 2F i linux-image-loongson-2f - Linux for Loongson 2F (meta-package) Any help to get the kernel work properly with iptables for a gateway will be most appreciated... Thanks, Javier. -- Package-specific info: ** Model information system type : lemote-fuloong-2f-box cpu model : ICT Loongson-2 V0.3 FPU V0.1 ** PCI devices: 00:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) Subsystem:
Bug#636095: linux-image-3.0.0-1-loongson-2f: loongson-2f should have ext4 built-in support and not as a module
Package: linux-2.6 Version: 3.0.0-1 Severity: normal *** Please type your report below this line *** I have 2 lemote mini-pcs, and for both I have separate partitions for boot and root. boot needs to be ext3, given that's what pmon boot loader supports. However root can be whatever filesystem linux supports. Now problem is the lonngson-2f kernel comes without initrd, and the one generated by initramfs-tools doesn't work. So whatever FS is used needs to be built inside the kernel itself and not compiled as a module. ext3 is built inside the kernel, however ext4 is not: % 'grep' -i ext3 /boot/config-3.0.0-1-loongson-2f CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y % 'grep' -i ext4 /boot/config-3.0.0-1-loongson-2f CONFIG_EXT4_FS=m CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set I've used ext4 as the FS for root en several systems, including x86-64 and x86-32. Moreover I also tried using archloong (arch linux side attempt for loongson), which had ext4 built inside the kernel, and I had no problems whatsoever with it. So current configuration inhibits ext4 FS to be used as the root one, and I really see no reason not to have it built in. Please reconsider having ext4 built inside the kernel at least for loongson-2f one. Thanks, Javier. -- Package-specific info: ** Version: Linux version 3.0.0-1-loongson-2f (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-3) ) #1 Mon Jul 25 21:17:28 UTC 2011 ** Command line: console=tty machtype=lemote-fuloong-2f-box root=/dev/sda6 video=sisfb:1280x1024-24@60 resume=/dev/sda5 PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [ 2.10] PM: Hibernation image partition 8:5 present [ 2.10] PM: Looking for hibernation image. [ 2.104000] PM: Image not found (code -22) [ 2.104000] PM: Hibernation image not present or could not be loaded. [ 2.104000] registered taskstats version 1 [ 2.104000] /build/buildd-linux-2.6_3.0.0-1-mipsel-TFQf1R/linux-2.6-3.0.0/debian/build/source_mipsel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 2.108000] Initializing network drop monitor service [ 2.132000] EXT3-fs: barriers not enabled [ 2.14] kjournald starting. Commit interval 5 seconds [ 2.14] EXT3-fs (sda6): mounted filesystem with ordered data mode [ 2.14] VFS: Mounted root (ext3 filesystem) readonly on device 8:6. [ 2.144000] Freeing unused kernel memory: 240k freed [ 4.292000] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 4.30] r8169 :00:06.0: (unregistered net_device): no PCI Express capability [ 4.308000] r8169 :00:06.0: eth0: RTL8169sc/8110sc at 0x900050072000, 00:23:9e:00:0f:62, XID 1800 IRQ 36 [ 4.492000] cpufreq: Loongson-2F CPU frequency driver. [ 4.508000] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 4.528000] rtc0: alarms up to one day, 114 bytes nvram [ 4.584000] usbcore: registered new interface driver usbfs [ 4.676000] usbcore: registered new interface driver hub [ 4.72] usbcore: registered new device driver usb [ 4.744000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 4.824000] PCI: Setting latency timer of device :00:0e.5 to 64 [ 4.824000] ehci_hcd :00:0e.5: EHCI Host Controller [ 4.828000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 4.852000] ehci_hcd :00:0e.5: new USB bus registered, assigned bus number 1 [ 4.90] ehci_hcd :00:0e.5: irq 11, io mem 0x50071000 [ 4.92] ehci_hcd :00:0e.5: USB 0.0 started, EHCI 1.00 [ 4.932000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 4.936000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 4.94] usb usb1: Product: EHCI Host Controller [ 4.944000] usb usb1: Manufacturer: Linux 3.0.0-1-loongson-2f ehci_hcd [ 4.948000] usb usb1: SerialNumber: :00:0e.5 [ 4.96] hub 1-0:1.0: USB hub found [ 4.976000] hub 1-0:1.0: 4 ports detected [ 4.988000] PCI: Enabling device :00:0e.4 ( -> 0002) [ 5.004000] PCI: Setting latency timer of device :00:0e.4 to 64 [ 5.004000] ohci_hcd :00:0e.4: OHCI Host Controller [ 5.02] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 2 [ 5.028000] ohci_hcd :00:0e.4: irq 11, io mem 0x5007 [ 5.12] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 5.124000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 5.128000] usb usb2: Product: OHCI Host Controller [ 5.132000] usb usb2: Manufacturer: Linux 3.0.0-1-loongson-2f ohci_hcd [ 5.136000] usb usb2: SerialNumber: :00:0e.4 [ 5.144000] hub 2-0:1.0: USB hub found [ 5.148000] hub 2-0:1.0: 4 ports detected [ 5.40] PCI: Setting latency timer of device
Bug#615609: [loongson-dev] Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
> 1) try this NIC with another machine (non-Loongson); Done, it works well on x86_32 and x86_64 (both intel). I've also tried: acpi=noirq usbcore.autosuspend=-1 Which in the past have been able to solve other serial usb issues, but none worked out... > 2) try another kind of NIC on this machine (e.g. there are MosChip mcs7830 > based USB NICs which also support true USB 2.0 speeds, or if USB 1.1 with 12 > mbit is enough, then Davicom dm9601 can be an option). I'll look for them. I acquired another one to try, but at the end it was based upon the same chipset, so also the same driver, so it didn't help. I'll look in the web... > > As for trying different module parameters you mentioned earlier, usbnet and > asix do not have any tunables, but ehci_hcd does have some, you can check > them out with "sudo modinfo ehci_hcd". Thanks a lot Roman, I'll investigate as soon as possible. I'd like a work around before going to buy something else, so this will be my first step, :-) So far no luck, but I'll keep trying, and if anyone gets to find something, please let me know... Javier. -- 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/BANLkTi=5sw+YGJmaKPpnvNiH1AYJE=g...@mail.gmail.com
Bug#615609: [loongson-dev] Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
On Sun, Mar 27, 2011 at 7:42 PM, wu zhangjin wrote: > Hi, Javier > > Thanks very much for your report. > > I don't have such a USB to reproduce the problem, hope the folks from > Lemote can work on it. thanks! > > Regards, > Wu Zhangjin Any sugestions on how to try debugging this? -- Javier. -- 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/BANLkTi=ssWMM_vG-=gve8qmfg8zmmj3...@mail.gmail.com
Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
Just to let you know the problem is still present under 2.6.37-2 debian kernel and 2.6.38-1 debian kernel... -- Javier. -- 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/AANLkTim+t0mdXEFQYA_UOdpoM-UZEv3gPN--=d3sx...@mail.gmail.com
Bug#615609: linux-image-2.6.37-1-loongson-2: Lemote mini-pc with linux-image-2.6.37-1-loongson-2 doesn't support external usb NIC (TU2-ET100)
Package: linux-2.6 Version: 2.6.37-1 File: linux-image-2.6.37-1-loongson-2 Severity: important Tags: upstream *** Please type your report below this line *** I have a lemote mini-pc loongson-2f, and when hooking an external usb NIC, the trendenet TU2-ET100, after disabling the inner NIC (realtek), then the device starts working nice for a while and then all of a sudden it just halts, and doing ifdown/ifup combination several times doesn't seem to be able to bring it up. I believe this problem is not exclusive to debian given that I've tried the gnew-sense 2.6.37 kernel, and another one from anheng, and none seems to work for this. Perhaps it exposes a HW problem, such the one for the inner NIC which can't handle checksums, and the CPU needs to deal with them (/sbin/ethtool -K eth0 rx off), but if it's a HW problem there might be a way to work around it (such as some usb-net or asix modules parameters). I'm not aware of any known problem related to this, so the first suspect is a kernel problem associated to the usb-net or the asix modules, which are the ones loaded for this external USB device. Perhaps for lemote HW there are some specific compile options required, and maybe missing, :-) Please notice the kernel was loaded with "debug" boot parameter, and even by doing so, the kernel log only shows the following associated to this problem: [ 68.076000] usb 1-1: new high speed USB device using ehci_hcd and address 4 [ 68.22] usb 1-1: New USB device found, idVendor=0b95, idProduct=7720 [ 68.22] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 68.22] usb 1-1: Product: AX88772 [ 68.22] usb 1-1: Manufacturer: ASIX Elec. Corp. [ 68.22] usb 1-1: SerialNumber: 01 [ 69.164000] asix 1-1:1.0: eth1: register 'asix' at usb-:00:0e.5-1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:08:1c:5f [ 69.164000] usbcore: registered new interface driver asix [ 173.484000] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 173.62] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 184.12] eth1: no IPv6 routers present [ 593.268000] ehci_hcd :00:0e.5: force halt; handshake 900050071014 4000 -> -145 [ 593.268000] ehci_hcd :00:0e.5: can't reschedule qh 9800bc2d5200, err -145 [ 593.268000] ehci_hcd :00:0e.5: force halt; handshake 900050071014 4000 4000 -> -145 [ 593.268000] ehci_hcd :00:0e.5: HC died; cleaning up [ 593.272000] usb 1-1: USB disconnect, address 4 [ 593.28] asix 1-1:1.0: eth1: unregister 'asix' usb-:00:0e.5-1, ASIX AX88772 USB 2.0 Ethernet While this is still a problem, the mini-pc is of not much usage to me, given that its aimed to work as a two NICs gateway (and light server for couple of light services). The ineer NIC is working now after the work around for the checksum (inner NIC can handle the checks), but I'm still missing the external usb NIC to work... Below is additional information... -- Package-specific info: ** Version: Linux version 2.6.37-1-loongson-2f (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-2) ) #1 Wed Feb 16 17:37:56 UTC 2011 ** Command line: console=tty no_auto_cmd root=/dev/sda6 resume=/dev/sda5 debug PMON_VER=LM6004-1.3.6 EC_VER=undefined machtype=lemote-fuloong-2f-box ** Not tainted ** Kernel log: [5.288000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.292000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.296000] usb usb2: Product: OHCI Host Controller [5.30] usb usb2: Manufacturer: Linux 2.6.37-1-loongson-2f ohci_hcd [5.304000] usb usb2: SerialNumber: :00:0e.4 [5.312000] hub 2-0:1.0: USB hub found [5.316000] hub 2-0:1.0: 4 ports detected [5.596000] PCI: Setting latency timer of device :00:0e.3 to 64 [5.68] usbcore: registered new interface driver usbserial [5.688000] USB Serial support registered for generic [5.716000] usb 2-3: new low speed USB device using ohci_hcd and address 2 [5.944000] usb 2-3: New USB device found, idVendor=04d9, idProduct=1702 [5.952000] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.956000] usb 2-3: Product: USB Keyboard [5.96] usb 2-3: Manufacturer: [6.272000] usb 2-4: new low speed USB device using ohci_hcd and address 3 [6.496000] usb 2-4: New USB device found, idVendor=0458, idProduct=003a [6.50] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.504000] usb 2-4: Product: Optical Mouse [6.508000] usb 2-4: Manufacturer: Genius [6.612000] input: USB Keyboard as /devices/pci:00/:00:0e.4/usb2/2-3/2-3:1.0/input/input0 [6.628000] generic-usb 0003:04D9:1702.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-:00:0e.4-3/input0 [6.652000] usbcore: registered new interface driver usbserial_generic [6.656000] usbserial: USB Serial Driver core [6.684000] input: USB Keyboa
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
An additional detail is that apparently: echo 0 > /sys/power/image_size Makes things work... I haven't tested enough to confirm though, neither I would know what exahustive kind of test would be required, but from couple of trials, it seems to work. Thanks to Ben Livengood who e-mailed me to try this... I still don't understand why the issue given that /sys/power/image_size controls the image size to be restored (best effort to try to keep it as small as indicated, though if not possible it'll be bigger). By default it's set to 500 MB... What is not clear to me if this setting helps as it seems, is why if the size is limited to 500 MB or a bit more, that would represent a problem given the swap space available? Now if the logic to apply is different, like as the RAM is 512 MB, perhaps it doesn't fit into 500 MB limit, which might be the case, but the documentation indicates it's best effort, meaning it can get bigger if it's not possible to make it fit, and even if a bit bigger, then there's plenty of swap in comparison. Any ways, with those questions at hand, then even if 500 MB is the default value for linux, why not making it 0 the default for debian? As I see it 0 doesn't hurt, and it's the more secure value, since it will always tend to minimize the image sizze to be restored, which in turns might also accelerate resume time... Thanks, -- Javier. -- 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/aanlkti=acth9g2mbwsjjawnjavjbvxzz3dn8fjcjj...@mail.gmail.com
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
Package: linux-image-2.6.32-5-686 Version: 2.6.32-17 Severity: important I have debian unstable installed on a laptop Dell Inspiron 600m, with pentium M processor at 1.6 GHz: % cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 9 model name : Intel(R) Pentium(R) M processor 1600MHz stepping: 5 cpu MHz : 1600.000 cache size : 1024 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2 bogomips: 3189.09 clflush size: 64 cache_alignment : 64 address sizes : 32 bits physical, 32 bits virtual power management: The laptop includes 512 MB of RAM, and a partition with 2 GB of swap: % cat /proc/meminfo MemTotal: 514432 kB MemFree: 100192 kB Buffers: 21396 kB Cached: 152088 kB SwapCached:0 kB Active: 240888 kB Inactive: 141424 kB Active(anon): 162184 kB Inactive(anon):47256 kB Active(file): 78704 kB Inactive(file):94168 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 514432 kB LowFree: 100192 kB SwapTotal: 2096408 kB SwapFree:2096396 kB Dirty: 4 kB Writeback: 0 kB AnonPages:208828 kB Mapped:40536 kB Shmem: 612 kB Slab: 10976 kB SReclaimable: 4584 kB SUnreclaim: 6392 kB KernelStack: 984 kB PageTables: 1464 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 2353624 kB Committed_AS: 362324 kB VmallocTotal: 504128 kB VmallocUsed: 18188 kB VmallocChunk: 473956 kB HardwareCorrupted: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 4096 kB DirectMap4k: 290488 kB DirectMap4M: 233472 kB A brief from the meminfo: MemTotal: 514432 kB SwapTotal: 2096408 kB Most of the time when trying to perform a kernel suspend to disk, whether by using "acpitool -S", which is my preferred method, or by directly writing "disk" into "/sys/power/state", the suspend is attempted, but it fails and the machine returns to state priot to attempt... When looking at dmesg: [ 90.737713] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 90.752182] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 90.766427] PM: Preallocating image memory... done (allocated 61556 pages) [ 90.817030] PM: Allocated 246224 kbytes in 0.03 seconds (8207.46 MB/s) [ 90.831363] Suspending console(s) (use no_console_suspend to debug) [ 90.847537] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 90.849254] parport_pc 00:0c: disabled [ 90.850417] serial 00:0b: disabled [ 90.972175] ipw2100 :02:03.0: PCI INT A disabled [ 92.656557] tg3 :02:00.0: PME# enabled [ 92.656568] pci :00:1e.0: wake-up capability enabled by ACPI [ 92.779840] Intel ICH Modem :00:1f.6: PCI INT B disabled [ 92.792231] Intel ICH :00:1f.5: PCI INT B disabled [ 92.792380] ata_piix :00:1f.1: PCI INT A disabled [ 92.795306] ACPI: Preparing to enter system sleep state S4 [ 92.795583] PM: Saving platform NVS memory [ 92.795672] Disabling non-boot CPUs ... [ 92.795783] PM: Creating hibernation image: [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image [ 92.796716] ACPI: Waking up from system sleep state S4 The important part of the dmesg section above is: [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image According to the kernel, there's a need of 67261 pages, when there are available only 64647. This is pretty weird, given that RAM size is only 512 MB, while swap partition is 2 GB, 4 times bigger, so there should be no issue. This kernel suspend to disk has always worked for me on this laptop, under debian unstable, and under other distros, like arch gnu/linux. I stopped using debian for a while and then recently installed debian unstable again, which came with linux-image-2.6.32-5-686, and since then it hasn't worked. There's an exception... Prior to current version (2.6.32-17) there was one which after which current one came after upgrade, which seemde to have fixed the issue, but as soon as I performed an upgrade and got current one, the issue cam back again. So there was a particu
About bug# 484779
Hi all, Bug# 484779 is affecting me, since I don NOT use desktop environment (neither KDE nor GNome). There are several tools I use for power management (laptop Compaq 8510w), between them a couple of tools I use: acpitool cpufreqd Both look for /proc/acpi/battery contents, on to report battery information (-B) and the other to decide how to regulate the processors frequency. The case of cpufreq is really fatal to me under kernel image 2.6.25-2-amd64 (# CONFIG_ACPI_PROCFS_POWER is not set), since as there's no battery info under /proc/acpi/battery, cpufreq no longer has criteria to decide, and thus stops deciding forcing slowest frequency (for me the rank of frequencies goes from 800MHz to 2.2GHz, so cpufreq forces this 2.2GHz on AC power @ 800MHz, how sad can that be?), see: Jul 21 11:07:34 jevv-ofic cpufreqd: acpi_battery_init: error, acpi_battery module not compiled or inserted (/proc/acpi/battery/: No such file or directory)? Jul 21 11:07:34 jevv-ofic cpufreqd: acpi_battery_init: exiting. The result of the mentioned bug is to merge it to a KDE one, which doesn't have anything to do with acpitool neither cpufreqd. I order to get my laptop working I had to recompile the kernel: % diff /boot/config-2.6.25 /boot/config-2.6.25-2-amd64 4c4 < # Mon Jul 21 12:49:21 2008 --- > # Mon Jul 14 10:38:33 2008 308c308 < CONFIG_ACPI_PROCFS_POWER=y --- > # CONFIG_ACPI_PROCFS_POWER is not set And now I can work @ 2.2GHz as I expected... Can the bug be reopened considering this is NOT kde related? BTW I do not use gnome either, so my set of tools include acpi, acpid, acpitool, cpufreqd, cpufrequtils, acpi-support-base, acpi-support, laptop-mode-tools. All this tools are still support under unstable, so I see no reason why the latest unstable linux-image wouldn't support them... If not, then the users get forced to recompile the kernel to get things working, :(. Can you please confirm? Thanks, -- Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux kernel image 2.6.23-1 + sound card yamaha YMF-754
On Dec 29, 2007 11:31 AM, Javier Vasquez <[EMAIL PROTECTED]> wrote: > > Happy holidays ! > > I have a toshiba satellite 2800-S202, with a yamaha sound card > YMF-754. From the lspci output I see: > > ... > > This output is from kernel 2.6.23, see "uname -a" output: > > Linux ojvn 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 GNU/Linux > > ... > From dmesg: > > ACPI: PCI Interrupt :00:0c.0[A] -> Link [LNKB] -> GSI 11 (level, > low) -> IRQ 11 > firmware request failed: -2 > ACPI: PCI interrupt for device :00:0c.0 disabled > Yamaha DS-1 PCI: probe of :00:0c.0 failed with error -2 > > ... > > Maybe the problem is not with the hardware itself, but with some > firmware issue, as indicated by dmesg (firmware request failed). > > I'm attaching the dmesg output, the lspci -v output, the alsaconf output... > > Did something particularly special changed with kernel 2.6.23-1, which > might be 2.6.23-2 instead according to aptitude (reading from aptitude > linux-image-2.6.23-1-686, version 2.6.23-2)? > > By the way, I'm using unstable, which I have been for some time now... > > Thanks, > > > -- > Javier Thanks to the Debian-User mailing list, it was uncovered that the firmware generation from the kernel was removed through patching by Debian. Any reason for that? What's the expectation from the users? Are they supposed to download the firmware sources from the alsa web, and compile it and install it themselves? Or are they supposed to compile the kernel "unpatching" the Debian removal of the firmware generation under kernel compilation? My supposition is that the attempt is for the user to go download the firmware and place it in this case under /lib/firmware/yamaha, since that's way simpler than "unpatching"... However I'd like to know what do you guys expect from the users, :)... BTW, downloading and installing the firmware actually worked out, as I reported in the debian-user mailing list... Thanks, -- Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Linux kernel image 2.6.23-1 + sound card yamaha YMF-754
Happy holidays ! I have a toshiba satellite 2800-S202, with a yamaha sound card YMF-754. From the lspci output I see: 00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-754 [DS-1E Audio Controller] Subsystem: Toshiba America Info Systems Unknown device 0001 Flags: medium devsel, IRQ 11 Memory at efdf (32-bit, non-prefetchable) [size=32K] I/O ports at fec0 [size=64] I/O ports at febc [size=4] Capabilities: This output is from kernel 2.6.23, see "uname -a" output: Linux ojvn 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 GNU/Linux Under linux kernel image 2.6.22-3 and mostly all previous kernels for quiet a while, I haven't had problems using this card, but for some reason now on 2.6.23-1 the card request for interrupt is failing. >From dmesg: ACPI: PCI Interrupt :00:0c.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 firmware request failed: -2 ACPI: PCI interrupt for device :00:0c.0 disabled Yamaha DS-1 PCI: probe of :00:0c.0 failed with error -2 Which kind of gets confirmed when trying to select the card from alsaconf: amixer: Mixer attach default error: No such device Or when trying to use alsamixer: alsamixer: function snd_ctl_open failed for default: No such device Weird thing is that the corresponding module actually got intalled: # lsmod | grep ymfpci snd_ymfpci 34720 0 gameport 15112 1 snd_ymfpci snd_ac97_codec 92388 1 snd_ymfpci snd_pcm72132 3 snd_ymfpci,snd_ac97_codec,snd_pcm_oss snd_opl3_lib9952 1 snd_ymfpci snd_page_alloc 10088 2 snd_ymfpci,snd_pcm snd_mpu401_uart 8128 1 snd_ymfpci snd_timer 21156 4 snd_ymfpci,snd_pcm,snd_opl3_lib,snd_seq snd48356 13 snd_ymfpci,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device firmware_class 9472 2 snd_ymfpci,pcmcia Maybe the problem is not with the hardware itself, but with some firmware issue, as indicated by dmesg (firmware request failed). I'm attaching the dmesg output, the lspci -v output, the alsaconf output... Did something particularly special changed with kernel 2.6.23-1, which might be 2.6.23-2 instead according to aptitude (reading from aptitude linux-image-2.6.23-1-686, version 2.6.23-2)? By the way, I'm using unstable, which I have been for some time now... Thanks, -- Javier lspci_v.log Description: Binary data dmessg.log Description: Binary data alsaconf.log Description: Binary data
