Re: [Zaurus-devel] Disable CF during suspend
Hi! Disable SPITZ_SCP_CF_POWER during suspend. Otherwise it eats battery, fast. Thanks to Stanislav Brabec. Signed-off-by: Pavel Machek pa...@ucw.cz Works on the top of the 3.0-rc2 on my spitz. Acked-by: Cyril Hrubis me...@ucw.cz -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] zaurus 3.0-rc1 Oops (fail GFP_DMA allocations when ZONE_DMA is not configured)
Hi! The 3.0-rc1 no longer boots on spitz see the attached Oops. The bisecting pointed to this commit, reverting it machine boots again. commit a197b59ae6e8bee56fcef37ea2482dc08414e2ac Author: David Rientjes rient...@google.com Date: Tue May 24 17:12:35 2011 -0700 mm: fail GFP_DMA allocations when ZONE_DMA is not configured The page allocator will improperly return a page from ZONE_NORMAL even when __GFP_DMA is passed if CONFIG_ZONE_DMA is disabled. The caller expects DMA memory, perhaps for ISA devices with 16-bit address registers, and may get higher memory resulting in undefined behavior. This patch causes the page allocator to return NULL in such circumstances with a warning emitted to the kernel log on the first occurrence. Signed-off-by: David Rientjes rient...@google.com Cc: Mel Gorman m...@csn.ul.ie Cc: KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com Cc: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com Cc: Rik van Riel r...@redhat.com Signed-off-by: Andrew Morton a...@linux-foundation.org Signed-off-by: Linus Torvalds torva...@linux-foundation.org diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 01e6b61..10a8c6d 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -2247,6 +2247,10 @@ __alloc_pages_nodemask(gfp_t gfp_mask, unsigned int order, if (should_fail_alloc_page(gfp_mask, order)) return NULL; +#ifndef CONFIG_ZONE_DMA + if (WARN_ON_ONCE(gfp_mask __GFP_DMA)) + return NULL; +#endif /* * Check the zones suitable for the gfp_mask contain at least one -- metan pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 pcmcia 1.0: pcmcia: registering new device pcmcia1.0 (IRQ: 202) mmc0: new SD card at address 0002 scsi0 : pata_pcmcia ata1: PATA max PIO0 cmd 0xc484 ctl 0xc484000e irq 202 mmcblk0: mmc0:0002 0 1.90 GiB mmcblk0: p1 ata1.00: CFA: LEXAR ATA FLASH, 20051220, max MWDMA4 ata1.00: 16128000 sectors, multi 0: LBA ata1.00: configured for PIO0 scsi 0:0:0:0: Direct-Access ATA LEXAR ATA FLASH 2005 PQ: 0 ANSI: 5 [ cut here ] WARNING: at mm/page_alloc.c:2251 __alloc_pages_nodemask+0x90/0x5a0() Modules linked in: ---[ end trace a76f77d0364258f5 ]--- sd 0:0:0:0: [sda] READ CAPACITY(16) failed sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x04 sd 0:0:0:0: [sda] Sense not available. sd 0:0:0:0: [sda] READ CAPACITY failed sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x04 sd 0:0:0:0: [sda] Sense not available. sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Asking for cache data failed sd 0:0:0:0: [sda] Assuming drive cache: write through wm8750-codec 0-001b: asoc: failed to add kcontrol Differential Mux sd 0:0:0:0: [sda] READ CAPACITY(16) failed sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x04 wm8750-codec 0-001b: asoc: failed to add kcontrol Out3 Mux sd 0:0:0:0: [sda] Sense not available. wm8750-codec 0-001b: asoc: failed to add kcontrol Right Line Mux sd 0:0:0:0: [sda] READ CAPACITY failed sd 0:0:0:0: [sda] wm8750-codec 0-001b: asoc: failed to add kcontrol Left Line Mux Result: hostbyte=0x00 driverbyte=0x04 sd 0:0:0:0: [sda] Sense not available. wm8750-codec 0-001b: asoc: failed to add kcontrol Right PGA Mux sd 0:0:0:0: [sda] Asking for cache data failed wm8750-codec 0-001b: asoc: failed to add kcontrol Left PGA Mux sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Attached SCSI removable disk asoc: wm8750-hifi - pxa2xx-i2s mapping ok ALSA device list: #0: Spitz TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 XScale iWMMXt coprocessor detected. pxa-rtc pxa-rtc: setting system clock to 2011-06-01 10:31:14 UTC (1306924274) Waiting 1sec before mounting root device... Unable to handle kernel NULL pointer dereference at virtual address 01d4 pgd = c0004000 [01d4] *pgd= Internal error: Oops: f5 [#1] PREEMPT Modules linked in: CPU: 0Tainted: GW(3.0.0-rc1 #16) PC is at blkdev_get+0x31c/0x3bc LR is at blkdev_get+0x2f4/0x3bc pc : [c00ccdac]lr : [c00ccd84]psr: 6013 sp : c3831e30 ip : 9e370001 fp : c3831e44 r10: c34041b0 r9 : r8 : 0083 r7 : c03298b0 r6 : fffa r5 : c34041a0 r4 : c3404340 r3 : r2 : r1 : c3404364 r0 : c03ca188 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 397f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc3830278) Stack: (0xc3831e30 to 0xc3832000) 1e20: c34041a0 c3404364 c3831e44 1e40: c3831ecc 0081 0001 c3831e68 c34041a0 0083 c03298b0 1e60: 8000 c03298b0 c38ff820 c00ccf2c c380f6e0 0083 1e80: 8000 c00a1aac ff9c c38147b8 c0341da8 c034246c 000a 1ea0: c38ff840 00d0 c380f750 c380f6e0 c03298b0 c03298b0 8000 1ec0: c00f4414
Re: [Zaurus-devel] Zaurus CF tests -- ok
Hi! Backtrace from QEMU ... I think this is what Cyril observed. But heck, it happens in QEMU too ;-) Yes, that is pretty much it. It happens randomly, eg. adding printk() line into kernel code (somewhere in mmc stack). Or sometimes crashes in the pccard initalization when two cards are inserted at the boot time. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Zaurus CF tests -- ok
Hi! After getting _good_ power supply, I was able to untar and rm ltp tree 100 times so far. 2.6.38, ext3. (So metan no, I do not see any weird ext3 problems). Hmm, I'm using original adapter, but who knows if it's okay to use... Another strange thing is... I see lots of duplicated keystrokes -- like type pavel but machine understands paavel. But it only seems to happen when I'm _not_ trying to debug it?! That seems to be side effect of machine under load (it has gpio keyboard). ( So... just because something needs 5V does not mean you should charge it from USB. Yes, I'm talking about zaurus. I noticed that it crashed rather quickly when connected to USB power. (For example in tar/rm test). So I took multimeter, and there was 4.15..4.5V on USB :-(. With power from USB extension cable, it crashes in 5 minutes. It seems to toggle charger a lot, as voltage on the cable is only 4.2..4.5V. I guess it is software problem in the charging code. ) The zaurus actually is AFAIK unable to run from battery when connected to the external power, so weak power line may explain some of the strange behaviour. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] zaurus: mmcblk0: error -110
Hi! When I insert the mmc card to zaurus, it gets properly detected and prints some info into console. Mounting reading/writing files works fine. However when the card is removed (doesn't need to be mounted before), the removal is most likely not detected, so when I insert it again, no info is printed into console and moreover when I try to mount it zaurus goes into infinite loop printing: Buffer I/O error on device mmcblk0p1, logical block 9 mmcblk0: error -110 sending status command mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00 end_request: I/O error, dev mmcblk0, sector 257 Buffer I/O error on device mmcblk0p1, logical block 10 mmcblk0: error -110 sending status command mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00 end_request: I/O error, dev mmcblk0, sector 258 Buffer I/O error on device mmcblk0p1, logical block 11 mmcblk0: error -110 sending status command mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00 end_request: I/O error, dev mmcblk0, sector 259 Buffer I/O error on device mmcblk0p1, logical block 12 mmcblk0: error -110 sending status command mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00 ... Related part of the .config: # # OTG and related infrastructure # # CONFIG_USB_GPIO_VBUS is not set # CONFIG_USB_ULPI is not set # CONFIG_NOP_USB_XCEIV is not set CONFIG_MMC=y # CONFIG_MMC_DEBUG is not set CONFIG_MMC_UNSAFE_RESUME=y # CONFIG_MMC_CLKGATE is not set # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=y CONFIG_MMC_BLOCK_MINORS=8 CONFIG_MMC_BLOCK_BOUNCE=y # CONFIG_SDIO_UART is not set # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # CONFIG_MMC_PXA=y -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] zaurus: mmcblk0: error -110
Hi! Which model do you have? And check the corresponding board file if card detect GPIO handling is doing right. I've got spitz (SL-3200). So I suppose the board file is arch/arm/mach-pxa/spitz.c, I'll have a look. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] zaurus: mmcblk0: error -110
Hi! Your symptoms match the bug that was fixed by: bad3babace2ee4d (mmc: fix CONFIG_MMC_UNSAFE_RESUME regression) but this fix made it into 2.6.38, so if you're using 2.6.38 final then you shouldn't be seeing this. Could you confirm that you have this patch? It seems that the pxa tree I have is still based on 2.6.38-rc8. And yes, turning CONFIG_MMC_UNSAFE_RESUME off seems to fix that problem. I'll try to update the kernel tree and try again with CONFIG_MMC_UNSAFE_RESUME enabled. Okay, great. It was introduced in 2.6.38-rc1 and fixed in 2.6.38 final. Tried 2.6.39-rc3 both with and without CONFIG_MMC_UNSAFE_RESUME and the insert/remove detection works but both with and without unsafe resume, if the card is removed for more than second or two it fails to recognize the card after insertion failing with: mmc0: error -95 whilst initialising SD card -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] 2.6.39-rc2 on zaurus: does not build, does not boot
Hi! Boot stops just after mounting root filesystem; cursor stops flashing. (Any idea what goes on there?) With CF bluetooth unplugged, it gets up to userland. Once it hung in eaarly boot, once early in runlevel 2. Hmm, the cf seems to be crippled a little. I've got oops in pccard, but only when cf wifi is compiled in kernel and inserted while booting, it stopped when the driver is compiled as module. Note that zaurus has two cf slots, one for internal hd and one outside, so it may be some race in cf/pccardd initalization. Some parts of the trace: Unable to handle kernel NULL pointer dereference at virtual address pgd = c0004000 [] mpad= Internal error: Oops: f5 [#1] PREEMPT las sysfs file: CPU: 0 Not tainted (2.6.38) PC is at complete+0x30/0x90 LR is at giveback+0x134/0x150 pc: [c0032070] lr : [c019a4278] psr: a093 sp : c38a4cb0 ip : c38atc70 fp : c38a5cc4 ... Flags: NzCv IRQs off FIQs on Mode SYC_32 ISA ARM segment kernel Control: 397f Table a0004000 DAC: 0017 Process: pccardd (pid 275, stack limit = 0xc38a4278) Stack (0xc38a5cb0 to 0xc38a6000) ... Which seems like problem occured in complete() ... -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] WARNING: at mm/page_alloc.c
Hi! I'm playing with uinput on zaurus (spitz) I've a pxa-2.6 kernel flashed in the uinput is loaded as module. Right after my program called: ioctl(fd, UI_DEV_CREATE); I've got: WARNING: at mm/page_alloc.c:2012 __alloc_pages_nodemask+0148/0x5a8() and the ioctl() has failed. Anybody has an idea what went wrong? -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] reboot/kexec in 2.6.38
Hi! I got report that reboot/kexec does not work in recent kernels. I tried both kexec and reboot in 2.6.38, and it worked ok. Maybe config issue? I think it's config issue. Never heard of this. I've seen that on my zaurus a month or two ago. When kexeced to pxa-linux-2.6 then tried to kexec again. The last thing I've seen was Bye on the framebuffer console and the machine freezed. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] zaurus pata_pcmcia corrupted filesystem
Hi! These seems to be different, at least it newer occured so often to me. Now installing debian packages often fails because it cannot remove temporary files, the filesystem worked reasonably good before. The usecase is to unpack archive with a lot rather small files somewhere deeper to the filesystem tree. Eg. installing gtk2-devel failed miserably when trying to move all the header files from *.h.dpkg-new to *.h, this works rather good with old driver. Well, I remember opkg crashes while installing emacs (many small files) and file system corruption as well. Both with kernel 2.6.26. The main difference is that now it's 100% reproducible and I've never seen corruption bad enough so I could not delete files without doing fsck first. Here is pseudo output from fsck on ext3 filesystem after these problems appeared: Pass 2: Bunch of these: Invalid HTREE directory inode $NUMBER $PATH/$FILE Clear HTree indexy? and these: Problem in HTree directory inode $NUMBER: block #$NR has bad max hash Pass 3: Bunch of: Entry '$FILE in $PATH ($NUMBER) has a non-unique filename. Rename to $FILE~0y? Happily the files/directories affected was only the recently written from the kernel from marex tree. I haven't seen file content to be corrupted (that doesn't mean there weren't any corruptions) but it seems they are not so likely as directory tree corruption. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] zaurus pata_pcmcia corrupted filesystem
Hi! Marek Vasut ported deprecated zaurus pcmcia disk driver to the pata_pcmcia interface, sources are here: http://git.kernel.org/?p=linux/kernel/git/marex/pxa-linux-2.6.git;a=shortlog;h=refs/heads/zaurus-haxing Everythig seems to be fine at the first look but sometimes the filesystem gets unconsistent. Typical example is extracting tar archive with big number of files and directories (I used ltp-full archive from http://www.sf.net/projects/ltp/). After doing that, some files or directories are present in the filesystem, eg. you can see them in directory listing but open or fstat returns ENOENT. Extracting to SD card seems to work without any problems. Anybody has idea what went wrong? -- Cyril Hrubis me...@ucw.cz ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] usb gadget on zaurus and kexec
Hi! After some testing I found out that no usb gadget (g_ether, g_mass_storage, ...) is working after zaurus boots with kexec. So it seems like some missing initalization (it's working after doing reboot again) anybody has any clue, patch or ideas how to debug this? -- Cyril Hrubis ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] 2.6.34-rc3 vs zaurus spitz: mistery solved
Hi! For some reason, spitz will hang very early in boot with SLUB. With SLOB, it boots fine. Weird, just wondering for what specific reason. Pavel, could you possibly paste the failure log if possible? Investigating... So far it seems that either it was fixed in -rc4 or that slub debugging options cause the problem. rc4 is working for me, so it looks like this was fixed, or at least works again now. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
