Re: [Zaurus-devel] bit errors on spitz
Hi! > dmesg would not be useful, it usually hits user programs. Like... mutt > suddenly displaying , instead of - in the header. Program failing to > start because function printg is not found (it was not exactly > printf->printg, I don't remember exact symbol), ping complaining > about discarding corrupted packets, etc. > > (Or of course, kernel oopsing or not going from suspend at all. But as > even user data are being corrupted, oops is not likely to be > interesting and system is typically not in state to capture it any more.) > Well I've seen empty lines when editing file with vim (these that are starting with blue tilda) in the middle of file. And sometimes programs segfaults for no good reason. Just today I've run "apt-get update" and got: symbol lookup error: apt-get: undefined symbol: _ZN16pkgAcquireStatus4StopEv While the correct symbol seems to be _ZN16pkgAcquireStatus4. When running 'make' in kernel directory and closing the display sometimes machine dies and nothing but reset under battery cover helps. I remeber waking up in the morning, opening the device and reseting the device. And it seems to be provoked much more by active CF wifi card. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] bit errors on spitz
Hi! > - And I see display noise while CF Wi-Fi card is active. Forgotten about this one. See for yourself, notice short black vertical lines flashing randomly. http://atrey.karlin.mff.cuni.cz/~metan/outgoing/zaurus_sickness.mpg -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] bit errors on spitz
Hi! > Is this display rotated by 90 degrees? Yes it is. > If so, they're actually horizontal lines as far as the display scanning > is concerned - and that tends to suggest that there's insufficient system > bus bandwidth for all the activity taking place, and the LCD controller > is being starved of data. Well, when doing 'echo 0 > /sys/class/graphics/fbcon/rotate_all' for 2.6.33 I've got the same problem but the lines are vertical. However 2.6.24 seems to work in non rotated mode. > I've seen similar (described) effects on SA1110 systems in past years > with low clock rates. > > Some of the reports suggest that this happens with multiple kernel versions > and is not something new to the latest kernels. Please confirm when the > problem started. As far as I can test in rotated mode it happens for kernels from 2.6.24 to 2.6.33 (I haven't older kernel than 2.6.24 that boots on spitz). -- 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.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
[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] usb gadget on zaurus and kexec
Hi! > >> > Dumping out the registers of the two situations and doing a comparison > >> > then might be a quick way. > >> > >> Any debugging update on this? > > > > Yeah, there's a workaround. Cyril's working on a proper fix, but that might > > take > > some time. Simply -- UP2OCR is misconfigured. > > That's quite interesting. In the pxa27x_udc gadget driver, I seem to have a > regression on the resume from suspend to RAM path. My USB UDC is not > enumerated > anymore. > > > The might be a correlation, as UP2OCR is lost in the suspend process. I'm very > interested by your analysis of the issue you have on kexec, as that might ease > my work :) Well it seems, at least for spitz that UP2OCR is set to host at the initialization and not touched anymore (spitz.c). I guess that the OE kernel, that is flashed in my spitz, changes UP2OCR when gadget/host driver is loaded but this doesn't work in vanilla kernels for some time. That would clarify why gadgets doesn't work after kexec at least for me. > Besides, it's been some time I've been thinking that the pxa deserves a proper > encapsulation of the USB internal routing paths (ie. a proper way to switch > from > usb host handled by ohci-pxa27x to an usb client handled by pxa2x_udc), to > reflect the setup of the Pad Unit (see TRM chapter 12.4 : tables 12.2, 12.15, > 12.17, 12.18 and 12.19). > > Whatever you find on the USB Port2 configuration register would help me design > the Pad block. > Would be great. So far the GPIO for usb host/slave cable detection is not used on spitz so there is no way to switch to USB slave for gadgets to work if you don't want to play with devmem2. There is some otg code in drivers/usb/otg/ but I haven't time to look on that yet. -- 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
Re: [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? > > > > What kind of number of files (in tar archive) are we talking about in round > > figures? Does the files it affect differ in size (large fail, small > > doesnt)..? > > Its hard to say without having more data (as always). > > These mysterious failures were discussed several times before in > zaurus-devel[1][2][3][4][5][6]. We suspected PCMCIA code, RAM errors or > bad voltage. > > Typical reproducers: > > git status on kernel tree (false result) > copy files from CF to SD or USB (errors in files) > gcc while using CF WLAN or CF Bluetooth (segfault) > > It happened in all kernels at least since 2.6.26, but probably in all > 2.6 kernels. > 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. -- Cyril Hrubis ___ 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! > > 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=shortlo > > g;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? > > I use the pcmcia on a few devices and was unable to replicate it (and I use > git > and do some heavy compiling on them too). I'll do some further testing. > > Cyril, do you have the PCMCIA timing fix for PXA applied? Well git log says so: ... pxa2xx/cpufreq: Fix PCMCIA frequency scaling The MCxx values must be based off memory clock, not CPU core clock. This also fixes the bug where on some machines the LCD went crazy while using PCMCIA. ... At least it's your tree that I've been testing ;). -- Cyril Hrubis ___ 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 index? 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~0? 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
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] reboot/kexec in 2.6.38
Hi! > I think it's config issue. Never heard of this. I've just compiled and booted 2.6.38. The kernel boots without problems when flashed in. But I've had no success with kexec, the last lines I see are: Starting new kernel Bye! _ Any ides where to dig? -- 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] WARNING: at mm/page_alloc.c
Hi! > Maybe if you could post your program we could see what exactly went > wrong... Gone trought my code once again and found small typo in sizeof() in uinput_user_dev initialization. Sorry for the noise. -- 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: [] lr : [] 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] 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! > > 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. Hmm, besides cleanup by Marek Vasut there were no changes in the code. And it seems that it was just cleanup in spitz_card_pwr_ctrl(). -- 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!
> > 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
> > ...
> >
> > 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
>
> 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.
--
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] zaurus: mmcblk0: error -110
Hi! > > 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 > > That's interesting. Would you mind trying to bisect? (Knowing whether > 2.6.38 final does it, for example, would be very helpful.) It may need one or two tries on 2.6.38 but it's there too. > There aren't many -EOPNOTSUPP returns in the stack. I see: > > card/block.c: mmc_blk_issue_secdiscard_rq and mmc_blk_issue_discard_rq > card/core.c: mmc_erase > core/sd_ops.c: mmc_app_cmd > > Mind doing some instrumentation to figure out which it is? Fails in the mmc_app_cmd. -- 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! > >> > mmc0: error -95 whilst initialising SD card > >> > >> That's interesting. Would you mind trying to bisect? (Knowing whether > >> 2.6.38 final does it, for example, would be very helpful.) > > > > It may need one or two tries on 2.6.38 but it's there too. > > > >> There aren't many -EOPNOTSUPP returns in the stack. I see: > >> > >> card/block.c: mmc_blk_issue_secdiscard_rq and mmc_blk_issue_discard_rq > >> card/core.c: mmc_erase > >> core/sd_ops.c: mmc_app_cmd > >> > >> Mind doing some instrumentation to figure out which it is? > > > > Fails in the mmc_app_cmd. > > Okay. mmc_app_cmd() hasn't changed for years, so I'm afraid I don't > have any strong leads for you -- further bisection (you're pretty > sure this is a regression?) would be very useful. Well, I was using some old kernel there and updated to the 2.6.38 recently so only clue I do have is that it was working on like 2 years old kernel. And bisection is quite complicated, as number of kernel images simply doesn't boot there. :( I will look on this next week (hopefully) thanks anyway for your help so far. -- 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
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] [PATCH] MAX1111: Fix race condition causing NULL pointer exception
Hi! I've applied this patch over 2.6.39-rc3 and did couple of suspends. After about ten of them I've got attached trace (instead of the usuall NULL pointer dereference in complete()). And yes, the MMC is still broken after this change it seems that there are more bugs in zaurus SPI drivers. -- metan PM: Syncing filesystems ... done. mmc0: card 0002 removed Freezing user space processes ... (elapsed 0.03 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.07 seconds) done. Suspending console(s) (use no_console_suspend to debug) [ cut here ] WARNING: at lib/kref.c:34 kref_get+0x20/0x44() Modules linked in: ---[ end trace 435fc8b0048da5e9 ]--- sd 0:0:0:0: [sda] Stopping disk [ cut here ] WARNING: at lib/kref.c:34 kref_get+0x20/0x44() Modules linked in: ---[ end trace 435fc8b0048da5ea ]--- PM: suspend of devices complete after 81.489 msecs [ cut here ] WARNING: at lib/kref.c:34 kref_get+0x20/0x44() Modules linked in: ---[ end trace 435fc8b0048da5eb ]--- PM: late suspend of devices complete after 1.993 msecs [ cut here ] WARNING: at lib/kref.c:34 kref_get+0x20/0x44() Modules linked in: ---[ end trace 435fc8b0048da5ec ]--- PM: early resume of devices complete after 728.029 msecs [ cut here ] WARNING: at lib/kref.c:34 kref_get+0x20/0x44() Modules linked in: ---[ end trace 435fc8b0048da5ed ]--- sd 0:0:0:0: [sda] Starting disk PM: resume of devices complete after 232.192 msecs Restarting tasks ... done. mmc0: error -95 whilst initialising SD card PM: Syncing filesystems ... done. haruka-chan login: root kernel BUG at kernel/cred.c:171! Unable to handle kernel NULL pointer dereference at virtual address pgd = c399c000 [] *pgd=a39ac831, *pte=, *ppte= Internal error: Oops: 817 [#1] PREEMPT last sysfs file: /sys/devices/platform/pxa2xx-spi.2/spi2.1/backlight/corgi_bl/brightness Modules linked in: CPU: 0Tainted: GW(2.6.39-rc7-00259-g09c1ce4 #14) PC is at __bug+0x18/0x24 LR is at __bug+0x14/0x24 pc : []lr : []psr: 4013 sp : c3bc5f78 ip : fp : bef2ea2c r10: 0002 r9 : c3bc4000 r8 : fffe r7 : ff9c r6 : c38d2d80 r5 : r4 : c38d2d80 r3 : r2 : c3bc5f6c r1 : c02d6e9b r0 : 0027 Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 397f Table: a399c000 DAC: 0015 Process login (pid: 1105, stack limit = 0xc3bc4278) Stack: (0xc3bc5f78 to 0xc3bc6000) 5f60: c38d2d80 c0054c2c 5f80: c38d2d80 c009c0e0 ff9c 400e6c14 0001 0021 5fa0: c0023184 c0023000 0001 400e6c14 400f0f18 5fc0: 0001 0021 400f1000 400f1000 fdc8 bef2ea2c 5fe0: bef2e9b8 400e0ed8 400e247c 6010 400e6c14 Code: e1a01000 e59f000c eb08ff53 e3a03000 (e5833000) Unable to handle kernel NULL pointer dereference at virtual address 0002 pgd = c397c000 [0002] *pgd=a3b71831, *pte=, *ppte= Internal error: Oops: f3 [#2] PREEMPT last sysfs file: /sys/devices/platform/pxa2xx-spi.2/spi2.1/backlight/corgi_bl/brightness Modules linked in: CPU: 0Tainted: G D W(2.6.39-rc7-00259-g09c1ce4 #14) PC is at kmem_cache_alloc+0x2c/0x78 LR is at scsi_pool_alloc_command+0x38/0x60 pc : []lr : []psr: 2093 sp : c388bd88 ip : fp : ec30 r10: c38f r9 : c38bd0b8 r8 : 1000 r7 : 0002 r6 : 0020 r5 : a093 r4 : c3802100 r3 : c03c8018 r2 : r1 : 0020 r0 : c3802100 Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 397f Table: a397c000 DAC: 0017 Process sync_supers (pid: 139, stack limit = 0xc388a278) Stack: (0xc388bd88 to 0xc388c000) bd80: c0329330 c380fdc0 0020 0020 1000 c0172ed8 bda0: c38bd000 0020 c38bc800 c0172f38 c38bd000 c38bc800 c38bd0b8 c0173010 bdc0: c38bd000 c38bd0b8 c38bd0b8 c01730e4 c38f4a90 c38bd000 003f bde0: 1000 c0178834 c38f4a90 c38bd000 c393c340 c0181918 c380fd20 c38f80a4 be00: 1000 c38f9638 c393c340 0001 c38f4a90 c38f4ad8 0007 c0117d64 be20: c38f4a90 c38f4a90 c38f4a90 c393c340 c393c340 c38bd0b8 0008 be40: ec30 c01197f8 c38bd000 c38bc800 c38bd024 c388a000 c393c340 c0177e44 be60: c393c340 c393c498 00012a00 c393c340 c3b1fc00 0003 0091 c393c340 be80: 0001 0008 ec30 c0118060 c393c340 c011ad38 c393c340 c38f4a90 bea0: c3b1fc00 c388a000 c388beb8 c393c340 c0119150 c3896b00 c388a000 bec0: c388beec c0265b20 c388a000 c3854aa0 00011210 c388bef4 bee0: c3896b00 c3b1fc00 0008 0001 0001 c0322fdc bf00: c01192d8 c388bf40 c3408000 c3854a60 0091 0010 0001 bf20: c00c85fc c3b1fc00 c00c86b4 0010 000f c3408000 c3408000 bf40: c3b1fc00 0091
[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 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 Cc: Mel Gorman Cc: KOSAKI Motohiro Cc: KAMEZAWA Hiroyuki Cc: Rik van Riel Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds 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 : []lr : []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 c00f53e8 8000 c38ff840 c00a0684 c03298b0 8000 1ee0: c380f6e0 c03298b0 c38ff840 c00baa34 c03298b0 c38ff820 c38ff840 1f00: 8000 c00baab0 0020 c38ff840 8000
Re: [Zaurus-devel] 3.0-rc1: alsactl restore fails on spitz
Hi! > Something changed in ALSA land, if you use sound you may want to check. I've seen the errors on alsactl restore too. However sound seems to work for me. Probably ALSA changed some ids of the knobs for alsamixer and the saved state could not be properly restored. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
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 Works on the top of the 3.0-rc2 on my spitz. Acked-by: Cyril Hrubis -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] zaurus patches -- arm/pxa -- is Eric alive
Hi! > > There are some rather critical patches for zaurus C-3000 (spitz) > > available... with no response. What is going on? > > Eric seems alive. At least he've sent pull requests few days ago. > Maybe you can point to those patches, that you mention as critical? Perhaps the most critical one is: [PATCH] MAX: Fix race condition causing NULL pointer exception http://ns1.yosemitephotos.net/lists/arm-kernel/msg125356.html Which fixes memory corruption that caused random oops. And then there is a bunch of fixes for charging and power management from Pavel Machek: Disable CF during suspend https://lkml.org/lkml/2011/5/21/46 and spitz pm https://lkml.org/lkml/2011/5/21/72 https://lkml.org/lkml/2011/5/21/73 https://lkml.org/lkml/2011/5/21/76 -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] zaurus patches -- arm/pxa -- is Eric alive
Hi! > > > > There are some rather critical patches for zaurus C-3000 (spitz) > > > > available... with no response. What is going on? > > > > > > Eric seems alive. At least he've sent pull requests few days ago. > > > Maybe you can point to those patches, that you mention as critical? > > > > Perhaps the most critical one is: > > > > [PATCH] MAX: Fix race condition causing NULL pointer exception > > > > http://ns1.yosemitephotos.net/lists/arm-kernel/msg125356.html > > Ahem, this one was opposed to. The right one seems to be: > > http://ns1.yosemitephotos.net/lists/arm-kernel/msg125592.html > > Note that it is a hwmon-driver and neither the apropriate list nor > maintainers have been CCed. Eric cannot take this patch. Check > MAINTAINERAS (or use scripts/get_maintainer.pl) to find the right people > and this will increase chances to get your patch upstream a lot. Right, CCing patch author. -- metan ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
