• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  General Category / General Discussion / Writing to Samba typically crashes system: kernel dma bug? on: November 29, 2009, 11:37:46 PM
I'm running Debian Testing's Samba 3.4.3-1 on an OpenRD running 2.6.32-rc7 (compiled Nov 14th fresh from Torvalds' master).  Its not a regression, I've seen the same behavior across quite a variety of kernel versions.

Writing to Samba hard locks my system.  I can read file off samba fine, at approximately 36MB/s, and browse my samba shares.  However, almost any writing to samba crashes the system.  I've managed to copy 1K files onto the system, but as soon as I try even a 16K file, the system hard locks.  Further adding to strangeness, if I edit a file from Windows, and write 1MB text into the file, I can save the file and samba appears to be just happy.  Its only when I attempt to copy in a not-insigificant sized file that my openrd hard locks.  Eventually, I get a stream of messages to this effect on the serial console:

Code:
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
thuban:~# [1308365.157740] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
[1308365.163867] Modules linked in: raid0 raid1 md_mod cifs nfsd exportfs sco br                                                    idge stp llc bnep rfcomm l2cap bluetooth autofs4 ipt_MASQUERADE iptable_nat nf_n                                                    at nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ipv6 snd_usb                                                    _audio snd_pcm snd_page_alloc snd_usb_lib snd_seq_midi snd_seq_midi_event snd_ra                                                    wmidi snd_hwdep rtl8187 snd_seq mac80211 snd_timer snd_seq_device snd cfg80211 s                                                    oundcore rfkill eeprom_93cx6 mv_cesa
[1308365.202461]
[1308365.204128] Pid: 0, comm:              swapper
[1308365.208769] CPU: 0    Not tainted  (2.6.32-rc7-thuban #1)
[1308365.214374] PC is at feroceon_range_dma_inv_range+0x4/0x40
[1308365.220063] LR is at dma_cache_maint_page+0x88/0xc0
[1308365.225138] pc : [<c0034f24>]    lr : [<c0031d08>]    psr: 60000013
[1308365.225144] sp : c05abcb8  ip : 09dc78c0  fp : df9604b8
[1308365.237028] r10: 0000006c  r9 : c9dc7858  r8 : 0000006c
[1308365.242453] r7 : 00000f94  r6 : c0816520  r5 : c0031ac0  r4 : c068a370
[1308365.249185] r3 : c0034f20  r2 : 60000013  r1 : cb6aa000  r0 : cb6a9f94
[1308365.255918] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment ke                                                    rnel
[1308365.263434] Control: 0005317f  Table: 0151c000  DAC: 00000017

[1308430.657740] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
[1308430.663868] Modules linked in: raid0 raid1 md_mod cifs nfsd exportfs sco bridge stp llc bnep rfcomm l2cap bluetooth autofs4 ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ipv6 snd_usb_audio snd_pcm snd_page_alloc snd_usb_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hwdep rtl8187 snd_seq mac80211 snd_timer snd_seq_device snd cfg80211 soundcore rfkill eeprom_93cx6 mv_cesa
[1308430.702462]
[1308430.704129] Pid: 0, comm:              swapper
[1308430.708770] CPU: 0    Not tainted  (2.6.32-rc7-thuban #1)
[1308430.714373] PC is at dma_cache_maint_page+0x88/0xc0
[1308430.719452] LR is at dma_cache_maint_page+0x88/0xc0
[1308430.724528] pc : [<c0031d08>]    lr : [<c0031d08>]    psr: 20000013
[1308430.724534] sp : c05abcb8  ip : 09dc78c0  fp : df9604b8
[1308430.736419] r10: 0000006c  r9 : c9dc7858  r8 : 0000006c
[1308430.741844] r7 : 00000f94  r6 : c0816520  r5 : c0031ac0  r4 : c068a370
[1308430.748576] r3 : 60000093  r2 : 60000013  r1 : cb6a9fff  r0 : cb6a9f94
[1308430.755309] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[1308430.762824] Control: 0005317f  Table: 0151c000  DAC: 00000017

[1308496.147739] BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
[1308496.153867] Modules linked in: raid0 raid1 md_mod cifs nfsd exportfs sco bridge stp llc bnep rfcomm l2cap bluetooth autofs4 ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ipv6 snd_usb_audio snd_pcm snd_page_alloc snd_usb_lib snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hwdep rtl8187 snd_seq mac80211 snd_timer snd_seq_device snd cfg80211 soundcore rfkill eeprom_93cx6 mv_cesa
[1308496.192461]
[1308496.194127] Pid: 0, comm:              swapper
[1308496.198769] CPU: 0    Not tainted  (2.6.32-rc7-thuban #1)
[1308496.204375] PC is at feroceon_l2_clean_range+0x74/0x94
[1308496.209714] LR is at feroceon_l2_clean_range+0x34/0x94
[1308496.215051] pc : [<c00351f0>]    lr : [<c00351b0>]    psr: 40000013
[1308496.215057] sp : c05abca8  ip : 09dc78c0  fp : df9604b8
[1308496.226942] r10: 0000006c  r9 : c9dc7858  r8 : df9604b8
[1308496.232367] r7 : df960920  r6 : 0000006c  r5 : 09dc78e0  r4 : 09dc78e0
[1308496.239098] r3 : c9dc78c0  r2 : c9dc7840  r1 : 40000013  r0 : 09dc78e0
[1308496.245830] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[1308496.253346] Control: 0005317f  Table: 0151c000  DAC: 00000017

I havent been able to coax any good logging out of samba or the system.   I have samba setup to log verbosely to syslog (/etc/samba/smb.conf):

Code:
[global]
syslog = 9

And syslog setup to spew to ttyUSB0 (/etc/syslog.conf):

Code:
daemon,mail.*;\
        news.=crit;news.=err;news.=notice;\
        *.=debug;*.=info;\
        *.=notice;*.=warn       /dev/ttyS0

In spite of this logging, I'm not getting any samba logging to console.  I'd expect at least to see stuff like /var/log/samba/log.kato, which has basic connect info like:
Code:
[2009/11/29 23:17:54,  1] smbd/service.c:1047(make_connection_snum)
  kato (::ffff:10.50.50.8) connect to service rektide initially as user rektide (uid=1000, gid=1000) (pid 2057)

This is keeping me from having a very nice OpenRD NAS setup, and has generally confounded the hell out of me.  Aside from the stack traces that slowly trickle in, I dont really have any idea what is causing this completely neurotic behavior.  The stack traces are inside dma routines though, which is _suspicious_, very suspicious.

I've tried reading/writing from usb flash, nand ubifs root, and my esata md0/raid1 and md1/raid0 arrays.  I can read off any of them just fine.  Writing to any device causes the lockup.

Regards,
rektide
2  General Category / General Discussion / mtd-utils? on: September 04, 2009, 10:16:46 AM
First off, how do I resize the /dev/mtd* devices?  I have a 3.5 MB kernel (barely fits in the 4MB /dev/mtd1) and a nearly 2MB uInitrd (which does not fit in /dev/mtd0).  I need to expand /dev/mtd0 to fit.

Second, do I need a special mtd utils?  I'm on OpenRD and have received a page full of errors when I attempt to ubiformat my /dev/mtd2:

# ubiformat /dev/mtd2 -s 512 -f ubi.img
ubiformat: 4055 corrupted erase counters
ubiformat: bad eraseblocks: 1013
ubiformat: warning!: only 0 of 4055 eraseblocks have valid erase counter
ubiformat: note, arbitrary erase coutner value may be specified using -e option
ubiformat: continue? (yes/no) yes


Then, attemting to ubiattach:
# ubiattach /dev/ubi_ctrl -m 2
ubiattach: error!: cannot attach mtd2
           error 22 (Invalid argument)

3  Hardware and U-Boot firmware / U-Boot stuff / Re: Compiling u-boot on: August 24, 2009, 11:16:13 PM
Please do the following:
1) tar jxvf u-boot-1.1.4.tar.bz2
2) mv u-boot-1.1.4 u-boot-3.4.16
3) unzip u-boot-3.4.16 (this will overwriting existing files)
4) cd u-boot-3.4.16
5) make mrproper
6) make rd88f6281Sheevaplug_config NBOOT=1 LE=1
7) make

The output should be u-boot-rd88f6281Sheevaplug_400db_nand.bin

The final instruction to compile U-Boot is "make all", not make.  This will fix your compile errors.

edit: this ought to fix your compile errors.  it fixed my mainline u-boot compile errors, at least, which looked very very very similar to the errors you are experiencing.

edit2: my undefined reference was at a latter step, never mind.  still, the mainline uboot sequence is make board_config; make all;
4  Hardware and U-Boot firmware / U-Boot stuff / Re: USB boot fails with multiple devices connected on: August 24, 2009, 11:13:21 PM
Other posts discussing this topic:

http://plugcomputer.org/plugforum/index.php?topic=403.0
http://plugcomputer.org/plugforum/index.php?topic=626.0

Mike, your issue-- adding devices to a running system causing disk read errors-- terrifies the hell out of me.

I would like to use my OpenRD system as a car computer.  As such, adding/removing devices at specific intervals is a non starter for me.

The one thing absent from all the discussion on this topic is any kind of technical insight into the issue-- is this a hardware issue, or just buggy U-boot?  I'd assumed it was a matter of the special brand of u-boot we use being flaky, but if mike is seeing issues in linux related to having multiple devices, I'm suddenly enormously concerned.
5  Hardware and U-Boot firmware / Hardware / Re: SheevaPlug v2 - Hardware Requests on: August 24, 2009, 07:19:15 AM
In order of my own priorities:
  • esata
  • 1gb ram
  • heating
li]sd card[/li]
[/list]

esata is by far the most significant; its the difference between an interesting toy and a fully capable PC.
6  Hardware and U-Boot firmware / U-Boot stuff / Re: mmcinit fails on: August 24, 2009, 06:57:35 AM
Hello,

I've tried with a 16GB Transcend Clas 6 and a 16GB A-Data Class 6.  I havent gone line by line, but the results seem quite similar.
7  Hardware and U-Boot firmware / U-Boot stuff / Mainline U-Boot experiment: no console. on: August 24, 2009, 06:55:51 AM
There are a number of Kirkwood & Sheevaplug commits on the U-Boot tree, so I tried compiling[1] and running it, just to see what happened, with reserved hopes that maybe it would fix either my boot from USB[2] or SD[3] issues.  When I rebooted, nothing appeared on the console what-so-ever.  Sad  I went back to my working U-Boot, but I thought it was an interesting experiment, and I'd be interested in any pointers about what may have gone wrong?

rektide

[1] http://www.openplug.org/plugwiki/index.php/User:Rektide#cross_compile_u-boot
[2] http://plugcomputer.org/plugforum/index.php?topic=653.0
[3] http://plugcomputer.org/plugforum/index.php?topic=652.0
8  Hardware and U-Boot firmware / U-Boot stuff / U-Boot Merge Window Begins Next Week! on: August 24, 2009, 05:22:35 AM
U-Boot release is planned for the end of August.  Immediately following that is a two week merge window for the release after that, which is destined to be the end of October.

Please please please; anyone who has been advancing Kirkwood support in U-Boot, take advantage of this window and _merge_!  The merge window is very short, but you'll have 6 weeks after the window to hammer out issues.

Just a heads-up-- wanted to make sure this important date is noted.

rektide
9  Hardware and U-Boot firmware / U-Boot stuff / USB boot fails with multiple devices connected on: August 23, 2009, 09:05:47 PM
I've been using USB boot from a flash stick for quite a while, but I wanted to start adding peripherials to make my system useful.  However, after adding peripherials, usb boot stops working.

This happens relatively quickly:
Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices...
      USB device not responding, giving up (status=20)
5 USB Device(s) found
       scanning bus for storage devices...


And then, ~3 minutes latter:
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 00 00 00
0 Storage Device(s) found


I've tried four hubs, and an army of peripherials.  Of the seven devices sitting next to me, the only time I've gotten OpenRD to boot was with either just the hub, or the hub and an Alfa wifi unit plugged in.  The other six devices all cause the above error.  The behavior has been consistent across both the originally installed u-boot and the u-boot from Alpha6.

Any suggestions, thoughts, advice?
rektide
10  Hardware and U-Boot firmware / U-Boot stuff / mmcinit fails on: August 23, 2009, 08:49:20 PM
Hello all,

I'm on OpenRD, and when I try to use mmcinit via the SheevaPlug Alpha6's U-Boot, I get the following:

Code:
Hit any key to stop autoboot:  0
Marvell>> mmcinit
Error! cmd : 8, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 55, err : 0201
Error! cmd : 41, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
Error! cmd : 1, err : 0201
No MMC card found
Marvell>>

Anyone seen this error?  Have any idea what it is?  Or any suggestions for how to fix this?  I've tried three different SD cards, always the same. Sad

Thanks
rektide
11  Hardware and U-Boot firmware / U-Boot stuff / Reference material: my USB oriented uboot. on: August 21, 2009, 04:10:55 PM
I've been booting from USB with a variety of kernels, and wanted to share my configuration.  Its on my preferences page.
12  Linux Stuff / Kernel / rtc-mv: internal RTC not ticking | my only Marvell Git roadblock on: August 21, 2009, 02:34:57 PM
I'm attempting to use Marvell's git tree with the OpenRD-Base board, which is arcNumber 2325.  When I boot the kernel, it seems to go fairly well, however I get a message in the kernel log; "rtc-mv rtc-mv: internal RTC not ticking". 

The affect is that I dont get a RTC device, so my board continues booting with from unix epoch 0; January 1, 1970.  This in turn causes my Ext3 to fail to mount:
/dev/sda1: Superblock last mount time is in the future.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.


I'd be interested to know if anyone is running Marvell git, and whether their RTC device works.  I'm on OpenRD, but I'd love to hear Sheeva users' status as well.

This is the only thing keeping my car computer from going online, so.... please, if you can help, do.
13  Linux Stuff / Kernel / .config for Marvell git on: August 17, 2009, 04:35:38 AM
Anyone willing to share the .config file they're using to build against Marvell git?  I'm on OpenRD-Base; I've attached mine.  It doesnt quite work; the lack of RTC has me dead in the water.  I'm hoping if I see a couple more examples, I might have better luck.
14  Hardware and U-Boot firmware / Hardware / Rtc device? on: August 17, 2009, 04:09:30 AM
Hello.  I built a kernel out of Marvell's git repo.  It does have CONFIG_RTC_DRV_MV configured.  But I'm not sure what device I need to configure for it; what mknod I need to issue.

Hrm this may also be a problem:  rtc-mv rtc-mv: internal RTC not ticking

hwclock is relying on finding /dev/rtc0 to set up my system time, and without system time, ext3 throws me into maintence mode because *gasp* its last mount time is in the future (sometime after jan 1 1970).

Any suggestions on how to get RTC running?  Any other places to ask?
15  General Category / General Discussion / Re: Order from global scale on: August 16, 2009, 11:25:28 PM
I ordered with two day shipping July 16.  July 22nd I asked what the status of my order was.  They said it was back-ordered and should be filled July 30.  August 3 I asked how fulfillment was going; they said "Your order has been processed; you will receive Tracking number by email" ... which I got on its actual ship date, August 6th.  Took forever, and I'm convinced it would've taken longer without nagging.  The one thing I'd note, the thing that kept my unpleasantness from turning to anger, was that Globalscale's turned around my emails very very quickly; in spite of feeling like my order was being ignored, it was impossible to entertain the notion that I was being ignored.

Marvell's creating a new market segment, but the supply chain, all the way down the line, doesnt seem setup for these small orders.  Good luck to all companies involves; its wonderful finally having top of the line SoC readily accessible to enthusiasts, but it seems apparent there are growing pains making this new market accessible, particularly to the "click button / buy product / on demand" expectations of buyers like myself.
Pages: [1] 2