Loading ...
Sorry, an error occurred while loading the content.
 

help! what if I have a broken NSLU2?

Expand Messages
  • Nicola Bernardini
    Dear friends, I have been following this list for some time now and have tried hard to make my NSLU2 work the way I see it working for you all, but to no
    Message 1 of 6 , Apr 23, 2006
      Dear friends,

      I have been following this list for some time now and have tried hard to
      make my NSLU2 work the way I see it working for you all, but to no
      avail. I usually use anywhere else Debian, so I am not a casual Debian
      GNU/Linux user.

      I have tried all distributions (Unslug, OpenSlug, DebianSlug,
      OpenDebianSlug):

      1. Unslug and OpenSlug install, but then they crash upon transfer of
      large files (let's say > 1 MB)

      2. DebianSlug crashes during di (debian-installer)

      3. OpenDebianSlug installs, but apt-get segfaults so there's no way
      to get to the next step. I have reformatted the drive, and every
      time it crashes in a fairly terminal way during different phases
      (untarring the sarge tarball, apt-get dist-upgradeing, etc.) In
      any case, it will not go beyong apt-get dist-upgrade.

      However (and this is the bad thing) both Linksys R29 and Linksys R63
      work without problems (but do half has much of what I need) :(. This is
      bad because I hardly can go bickering to the Linksys forums if their
      firmware work.

      Another bad thing is that I can hardly collect any log on the machine
      because it fails much before being able to start syslog or something
      like it. I have succeded in getting a dmesg output into a file once that
      I tried with a memory stick, and it features a nice big fat kernel oops
      right at the end. I append this output at the end of this post.

      I heavily suspect that my NSLU2 is broken, but I would'nt know how to
      diagnose the break (RAM? Ethernet? bus?). Some months ago I saw on this
      list somebody being successeful in having it replaced by Linksys, but
      since my slug works with their firmware, I suppose this will not do for
      me.

      Can somebody help me in making some sense out of what the slug is doing?
      Or to do some form of hardware diagnostics? Does this happen only to me
      or is it a fairly diffused behaviour? I really would like to use this
      little jewel but I have been very unlucky so far.

      Thanks to all the people keeping this project alive and kicking,

      Nicola

      --
      Nicola Bernardini
      Scuola di Musica Elettronica
      Conservatorio C.Pollini Padova
      e-mail: nicb@...
      http://www.conservatoriopollini.it
      http://www.sme-ccppd.org
      http://www.nicolabernardini.info
      GPG fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910
      Neither MS-Word nor MS-PowerPoint attachments please.

      ------------------------------------------------------------------------
      Normal zone: 0 pages, LIFO batch:1
      HighMem zone: 0 pages, LIFO batch:1
      Built 1 zonelists
      Kernel command line: root=/dev/mtdblock4 rw rootfstype=jffs2 mem=32M@0x00000000 init=/linuxrc reboot=s noirqdebug console=ttyS0,115200n8
      PID hash table entries: 256 (order: 8, 4096 bytes)
      Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
      Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
      Memory: 32MB = 32MB total
      Memory: 30512KB available (1601K code, 153K data, 80K init)
      Calibrating delay loop... 131.48 BogoMIPS (lpj=657408)
      Mount-cache hash table entries: 512
      CPU: Testing write buffer coherency: ok
      NET: Registered protocol family 16
      PCI: IXP4xx is host
      PCI: IXP4xx Using indirect access for memory space
      PCI: bus0: Fast back to back transfers disabled
      dmabounce: registered device 0000:00:01.0 on pci bus
      dmabounce: registered device 0000:00:01.1 on pci bus
      dmabounce: registered device 0000:00:01.2 on pci bus
      SCSI subsystem initialized
      usbcore: registered new driver usbfs
      usbcore: registered new driver hub
      OpenN2 Misc I/O Driver Version 0.1.7
      init_jiffy=-29974
      setup_interrupts - jiffies=-29974 init_jiffy=-29974
      enable_irq(22) unbalanced from c0010cb0
      enable_irq(29) unbalanced from c0010cb8
      NetWinder Floating Point Emulator V0.97 (double precision)
      JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
      Initializing Cryptographic API
      IXP4xx Watchdog Timer: heartbeat 60 sec
      Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
      ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
      ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
      io scheduler noop registered
      io scheduler deadline registered
      RAMDISK driver initialized: 4 RAM disks of 10240K size 1024 blocksize
      IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
      IXP4XX-Flash.0: Found an alias at 0x800000 for the chip at 0x0
      Intel/Sharp Extended Query Table at 0x0031
      Using buffer write method
      cfi_cmdset_0001: Erase suspend on write enabled
      0: offset=0x0,size=0x20000,blocks=64
      Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e0000
      6 RedBoot partitions found on MTD device IXP4XX-Flash.0
      Creating 6 MTD partitions on "IXP4XX-Flash.0":
      0x00000000-0x00040000 : "RedBoot"
      0x00040000-0x00060000 : "SysConf"
      0x00060000-0x00160000 : "Kernel"
      0x00160000-0x00180000 : "Ramdisk"
      0x00180000-0x007e0000 : "Flashdisk"
      0x007e0000-0x00800000 : "FIS directory"
      PCI: enabling device 0000:00:01.2 (0140 -> 0142)
      ehci_hcd 0000:00:01.2: EHCI Host Controller
      ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
      ehci_hcd 0000:00:01.2: irq 26, io mem 0x48002000
      ehci_hcd 0000:00:01.2: park 0
      ehci_hcd 0000:00:01.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
      hub 1-0:1.0: USB hub found
      hub 1-0:1.0: 5 ports detected
      ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
      PCI: enabling device 0000:00:01.0 (0140 -> 0142)
      ohci_hcd 0000:00:01.0: OHCI Host Controller
      ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
      ohci_hcd 0000:00:01.0: irq 28, io mem 0x48000000
      hub 2-0:1.0: USB hub found
      hub 2-0:1.0: 3 ports detected
      PCI: enabling device 0000:00:01.1 (0140 -> 0142)
      ohci_hcd 0000:00:01.1: OHCI Host Controller
      ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
      ohci_hcd 0000:00:01.1: irq 27, io mem 0x48001000
      hub 3-0:1.0: USB hub found
      hub 3-0:1.0: 2 ports detected
      Initializing USB Mass Storage driver...
      usbcore: registered new driver usb-storage
      USB Mass Storage support registered.
      i2c /dev entries driver
      LOADED Xicor x1205 RTC Dvr v0.9.3.3NPW
      Xicor x1205 RTC Dvr v0.9.3.3NPW attached on adapter
      NET: Registered protocol family 2
      IP: routing cache hash table of 512 buckets, 4Kbytes
      TCP established hash table entries: 2048 (order: 2, 16384 bytes)
      TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
      TCP: Hash tables configured (established 2048 bind 2048)
      NET: Registered protocol family 1
      VFS: Mounted root (jffs2 filesystem).
      Freeing init memory: 80K
      ixp400: module license 'unspecified' taints kernel.
      Module init.
      ixp425_eth:
      Initializing IXP425 NPE Ethernet driver software v. 1.1A
      ixp425_eth: CPU clock speed (approx) = 0 MHz
      [error] ixEthMiiPhyScan : unexpected Mii PHY ID 00008201
      ixp425_eth: npe0 is using the PHY at address 0
      ixp425_eth: npe1 is using the PHY at address 1
      ixp425_eth: ixEthMiiLinkStatus failed on PHY0.
      Can't determine
      the auto negotiated parameters. Using default values.
      usb 1-2: new high speed USB device using ehci_hcd and address 2
      scsi0 : SCSI emulation for USB Mass Storage devices
      usb-storage: device found at 2
      usb-storage: waiting for device to settle before scanning
      Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04
      Type: Direct-Access ANSI SCSI revision: 00
      SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
      sda: Write Protect is off
      sda: Mode Sense: 23 00 00 00
      sda: assuming drive cache: write through
      SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
      sda: Write Protect is off
      sda: Mode Sense: 23 00 00 00
      sda: assuming drive cache: write through
      sda: sda1 sda2
      Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
      usb-storage: device scan complete
      kjournald starting. Commit interval 5 seconds
      EXT3 FS on sda1, internal journal
      EXT3-fs: mounted filesystem with ordered data mode.
      Unable to handle kernel paging request at virtual address 00200000
      pgd = c0004000
      [00200000] *pgd=00000000
      Internal error: Oops: f5 [#1]
      Modules linked in: ixp425_eth ixp400 ext3 jbd mbcache
      CPU: 0
      pc : [<bf006e7c>] lr : [<bf004bac>] Tainted: P
      sp : c02d1e20 ip : 00200000 fp : c02d1e34
      r10: c0586328 r9 : c02d1e84 r8 : c05ab4ac
      r7 : c05d79f0 r6 : 00000000 r5 : c01e1ba0 r4 : c05d7a50
      r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : c05ab4ac
      Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment kernel
      Control: 39FF Table: 01AE0000 DAC: 00000017
      Process kswapd0 (pid: 56, stack limit = 0xc02d0194)
      Stack: (0xc02d1e20 to 0xc02d2000)
      1e20: c05d7a50 c01e1ba0 c02d1e5c c02d1e38 bf004bac bf006e64 0000001d c01e1ba0
      1e40: 0000001f 00000002 0000001e ffffffff c02d1e6c c02d1e60 c006f050 bf004ad0
      1e60: c02d1e80 c02d1e70 c0058570 c006f00c c01e1ba0 c02d1eec c02d1e84 c005898c
      1e80: c0058548 0000000e 00000000 c01e1260 c01e1900 c01e1ba0 c01e1bc0 c01e1960
      1ea0: c01e1c80 c01e1aa0 c01e1a80 c01e18e0 c01e18c0 c01e1600 c01e1640 c01e0a40
      1ec0: c01e1b80 c0586288 c0586290 c01b43b4 00000028 c01b43a4 c02d1ef8 0000001a
      1ee0: c02d1f28 c02d1ef0 c0085728 c00588e4 0000001a 00000080 c0586448 c1ad57b8
      1f00: 00000082 00000000 00000040 00000082 c023fb40 000000d0 c01b3890 c02d1f5c
      1f20: c02d1f2c c0058dec c0085630 00001736 00000020 00000001 c01b3224 00000000
      1f40: c01b3224 00000000 00000000 0000000a c02d1ff4 c02d1f60 c005a35c c0058d24
      1f60: 00000000 00000000 00001736 c02d1f7c 00000000 00000000 00000000 00000000
      1f80: 00000020 00000000 00000000 000002dc 00000020 0000000a 000000d0 00000000
      1fa0: 00000020 00000000 c02b7560 c0047998 c02d1fc4 c02d1fc4 00000000 c02b7560
      1fc0: c0047998 c02d1fc4 c02d1fc4 00000000 00000000 00000000 00000000 00000000
      1fe0: 00000000 00000000 00000000 c02d1ff8 c00354f8 c005a0ac 95a6d24d 4a592db0
      Backtrace:
      Function entered at [<bf006e58>] from [<bf004bac>]
      r5 = C01E1BA0 r4 = C05D7A50
      Function entered at [<bf004ac4>] from [<c006f050>]
      r8 = FFFFFFFF r7 = 0000001E r6 = 00000002 r5 = 0000001F
      r4 = C01E1BA0
      Function entered at [<c006f000>] from [<c0058570>]
      Function entered at [<c005853c>] from [<c005898c>]
      r4 = C01E1BA0
      Function entered at [<c00588d8>] from [<c0085728>]
      Function entered at [<c0085624>] from [<c0058dec>]
      Function entered at [<c0058d18>] from [<c005a35c>]
      Function entered at [<c005a0a0>] from [<c00354f8>]
      Code: e15c0001 0a00001c e590202c e5903030 (e59c4000)

      ----- End forwarded message -----
    • Bob Cox
      In article , ... Nicola - you say it works ok using the Linksys firmware. Have you tried very large, intensive file
      Message 2 of 6 , Apr 25, 2006
        In article <20060424063558.GH31372@...-ft.org>,
        Nicola Bernardini <nic.bern@...> wrote:

        > I have been following this list for some time now and have tried hard to
        > make my NSLU2 work the way I see it working for you all, but to no
        > avail. I usually use anywhere else Debian, so I am not a casual Debian
        > GNU/Linux user.
        >
        > I have tried all distributions (Unslug, OpenSlug, DebianSlug,
        > OpenDebianSlug):
        >
        > 1. Unslug and OpenSlug install, but then they crash upon transfer of
        > large files (let's say > 1 MB)
        >
        > 2. DebianSlug crashes during di (debian-installer)
        >
        > 3. OpenDebianSlug installs, but apt-get segfaults so there's no way
        > to get to the next step. I have reformatted the drive, and every
        > time it crashes in a fairly terminal way during different phases
        > (untarring the sarge tarball, apt-get dist-upgradeing, etc.) In
        > any case, it will not go beyong apt-get dist-upgrade.
        >
        > However (and this is the bad thing) both Linksys R29 and Linksys R63
        > work without problems (but do half has much of what I need) :(. This is
        > bad because I hardly can go bickering to the Linksys forums if their
        > firmware work.

        Nicola - you say it works ok using the Linksys firmware. Have you tried
        very large, intensive file transfers to your USB harddrive when using
        Linksys? What I am trying to get at is whether the problem is really
        the USB interface and/or the harddrive itself failing under heavy load
        (for example transferring large files, installing an OS or running
        apt-get as mentioned above). This *might* be the harddrive overheating?

        Just a thought - admittedly unlikely!

        Good luck.

        --
        Bob Cox. Stoke Gifford, near Bristol, UK.
        OpenDebianSlug on NSLU2: http://slug.bobcox.com/
      • thekitehunter
        I reflashed my working NSLU2 to the Unslung 6.8 beta, adding a new disk at the same time. It is unslung to USB2 and USB1 has a NTFS formatted disk (both Lacie
        Message 3 of 6 , Apr 25, 2006
          I reflashed my working NSLU2 to the Unslung 6.8 beta, adding a new
          disk at the same time. It is unslung to USB2 and USB1 has a NTFS
          formatted disk (both Lacie 250mb disks). It sort-of works ok, but I
          have the same problem - the unit is hanging on large file transfers.
          It is not locking up as the various lights flash intermittently
          showing that it is doing something, but whatever it is, it is not
          doing it over the network and I have to unplug the power to get it
          working again. I have been looking to see if anyone else is
          experiencing this and this is the first hint. I have nothing running
          now, except the Unslung firmware.
          Are there any others with this problem?

          John

          --- In nslu2-general@yahoogroups.com, Bob Cox <bobcox1955@...> wrote:
          >
          > In article <20060424063558.GH31372@...>,
          > Nicola Bernardini <nic.bern@...> wrote:
          >
          > > I have been following this list for some time now and have
          > > tried hard to make my NSLU2 work the way I see it working for
          > > you all, but to no avail. I usually use anywhere else Debian,
          > > so I am not a casual DebianGNU/Linux user.
          > >
          > > I have tried all distributions (Unslug, OpenSlug,
          > > DebianSlug, OpenDebianSlug):
          > >
          > > 1. Unslug and OpenSlug install, but then they crash upon
          > > transfer of large files (let's say > 1 MB)
          > >
          > > 2. DebianSlug crashes during di (debian-installer)
          > >
          > > 3. OpenDebianSlug installs, but apt-get segfaults so there's
          > > no way to get to the next step. I have reformatted the
          > > drive, and every time it crashes in a fairly terminal way
          > > during different phases (untarring the sarge tarball,
          > > apt-get dist-upgradeing, etc.) In any case, it will not go
          > > beyong apt-get dist-upgrade.
          > > However (and this is the bad thing) both Linksys R29 and
          > > Linksys R63 work without problems (but do half has much of what I
          > > need) :(. This isbad because I hardly can go bickering to the
          > > Linksys forums if theirfirmware work.
          >
          > Nicola - you say it works ok using the Linksys firmware.
          > Have you tried very large, intensive file transfers to your USB
          > harddrive when using Linksys? What I am trying to get at is
          > whether the problem is really the USB interface and/or the
          > harddrive itself failing under heavy load(for example transferring
          > large files, installing an OS or running apt-get as mentioned
          > above). This *might* be the harddrive overheating?
          > Just a thought - admittedly unlikely!
          >
          > Good luck.
          >
          > --
          > Bob Cox. Stoke Gifford, near Bristol, UK.
          > OpenDebianSlug on NSLU2: http://slug.bobcox.com/
          >
        • Nicola Bernardini
          Dear Bob, thank you very much for your reply! I was starting to feel somewhat alone :) ... I must say that I did not do many tests with Linksys firmware for
          Message 4 of 6 , Apr 25, 2006
            Dear Bob,

            thank you very much for your reply! I was starting to feel somewhat alone :)

            On Tue, Apr 25, 2006 at 09:21:18AM +0100, Bob Cox wrote:
            > In article <20060424063558.GH31372@...-ft.org>,
            > Nicola Bernardini <nic.bern@...> wrote:
            >
            > > I have been following this list for some time now and have tried hard to
            > > make my NSLU2 work the way I see it working for you all, but to no
            > > avail. I usually use anywhere else Debian, so I am not a casual Debian
            > > GNU/Linux user.
            > >
            > > I have tried all distributions (Unslug, OpenSlug, DebianSlug,
            > > OpenDebianSlug):
            > >
            > > 1. Unslug and OpenSlug install, but then they crash upon transfer of
            > > large files (let's say > 1 MB)
            > >
            > > 2. DebianSlug crashes during di (debian-installer)
            > >
            > > 3. OpenDebianSlug installs, but apt-get segfaults so there's no way
            > > to get to the next step. I have reformatted the drive, and every
            > > time it crashes in a fairly terminal way during different phases
            > > (untarring the sarge tarball, apt-get dist-upgradeing, etc.) In
            > > any case, it will not go beyong apt-get dist-upgrade.
            > >
            > > However (and this is the bad thing) both Linksys R29 and Linksys R63
            > > work without problems (but do half has much of what I need) :(. This is
            > > bad because I hardly can go bickering to the Linksys forums if their
            > > firmware work.
            >
            > Nicola - you say it works ok using the Linksys firmware. Have you tried
            > very large, intensive file transfers to your USB harddrive when using
            > Linksys? What I am trying to get at is whether the problem is really
            > the USB interface and/or the harddrive itself failing under heavy load
            > (for example transferring large files, installing an OS or running
            > apt-get as mentioned above). This *might* be the harddrive overheating?
            >
            > Just a thought - admittedly unlikely!

            I must say that I did not do many tests with Linksys firmware for three
            reasons:

            1) I don't need a simple file server as the Linksys is set to be; I need
            a full-featured server as the OpenDebianSlug promises to be (and I
            know very well it can be), so when I bought the NSLU2 almost a year
            ago I flashed unslug then openslug and started having problems with
            these

            2) In addition to that, IIRC I initially did some tests with the Linksys
            firmware and the large file test was killing the samba serving on me.
            At the time, I though it was samba having problems (it happens to me
            also on other servers).

            3) To *really* revert back to the Linksys firmware would mean to
            completely reformat my 200 GByte Maxtor One Touch drive which is now
            half full of things which I would not know where to put, so I did my
            tests with a 512 Mbytes memory stick.

            Which made me think that you might be right! I should try the
            OpenDebianSlug installation on the 512 Mbytes memory stick.

            However, I must tell you that I considered the overheating problems some
            months ago (I have very little time to devote to non-fully working
            appliances, so it takes me months before I can come back to them :() and
            I made some tests opening the case, adding fans to the disk etc. and
            that was not the problem. The disk was perfectly cold and the NSLU2
            keeps on oopsing and dying.

            Also: the OpenDebianSlug installation segfaults abruptly in the middle
            of the very first apt-get dist-upgrade (step 12 of the documentation),
            at around 70% of the building of the dependency tree. That is not really
            where the disk-intensive part is, is'nt it? Another test I did yesterday
            was to run a quick-and-dirty perl script which basically eats up all the
            memory available and dies (thus basically releasing most of the RAM),
            and *then* the apt-get dist-upgrade went to the end, started installing
            but then died in the middle of the installation of coreutils. I attach
            the perl script just for documentation.

            So: I will try again the installation and get back to the list as soon
            as I have done the test (this won't be before Friday evening I'm afraid
            :(). In the meantime, I just wonder if there is anywhere to be found a
            diagnostic software that just does the diagnostics on the NSLU2...

            Thanks again Bob for your suggestions and for devoting some time to the
            problem! I also looked at your slug page and envy your setup very much!
            (that's exactly what I wanted to do, but I'm having bad luck)

            Nicola

            --
            Nicola Bernardini
            e-mail: nic.bern@...
            http://www.nicolabernardini.info
            GPG fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910
            Neither MS-Word nor MS-PowerPoint attachments please.

            ----------

            #! /usr/bin/perl
            #
            # cleanram,v 0.1 2002/06/30 19:52:53 nicb Exp
            #
            # this script eats memory until it explodes. In doing this it asks all
            # the resources of the system available and then suddendly releases them.
            # It is some form of stupid garbage collection, is'nt it? :) (but it works
            # well when your netscape browser or your X server have been running for
            # weeks...)
            #

            #
            # main
            #
            @ressources = ();

            while()
            {
            push(@ressources, eat());
            }
            #
            # end of main
            #
            BEGIN {
            print "Starting ram cleansing (ver. \0.1). Please wait and don't do anything...\n";
            }

            END {
            print "Done. Your memory is back! :-)\n";
            }

            sub eat()
            {
            local @chunk = ( 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0);

            return \@chunk;
            }
            #
            # cleanram,v
            # Revision 0.1 2002/06/30 19:52:53 nicb
            # corrected small printout bug
            #
            # Revision 0.0 1999/01/13 07:12:14 nicb
            # Initial Revision
            #


            [Non-text portions of this message have been removed]
          • Marcel Nijenhof
            ... I have tried to reproduce it but i didn t succeed. I created a file of 1 GB over smbfs on the slug with the command: # dd if=/dev/zero of=t bs=64k
            Message 5 of 6 , Apr 25, 2006
              On Tue, 2006-04-25 at 11:32 +0000, thekitehunter wrote:

              > I reflashed my working NSLU2 to the Unslung 6.8 beta, adding a new
              > disk at the same time. It is unslung to USB2 and USB1 has a NTFS
              > formatted disk (both Lacie 250mb disks). It sort-of works ok, but I
              > have the same problem - the unit is hanging on large file transfers.
              > It is not locking up as the various lights flash intermittently
              > showing that it is doing something, but whatever it is, it is not
              > doing it over the network and I have to unplug the power to get it
              > working again. I have been looking to see if anyone else is
              > experiencing this and this is the first hint. I have nothing running
              > now, except the Unslung firmware.
              > Are there any others with this problem?
              >

              I have tried to reproduce it but i didn't succeed.

              I created a file of 1 GB over smbfs on the slug with the command:
              # dd if=/dev/zero of=t bs=64k count=16000
              16000+0 records in
              16000+0 records out
              1048576000 bytes (1.0 GB) copied, 279.465 seconds, 3.8 MB/s

              I have some questions:
              1) Do you have the problem with both disks?
              2) How do you copy the files?
              3) How do you know that the system hangs?

              --
              Marceln
            • Nicola Bernardini
              Dear list, I tried, as I said a week ago, to run OpenDebianSlug on a 512 MByte stick to see whether it was my disk (Maxtor OneTouch 200 GBytes)
              Message 6 of 6 , May 1, 2006
                Dear list,

                I tried, as I said a week ago, to run OpenDebianSlug on a 512 MByte
                stick to see whether it was my disk (Maxtor OneTouch 200 GBytes)
                overheating or else.

                The trials went even worse :( I can't get to untar the Debian tarball
                (step 5) of the OpenDebianSlug distribution that I start see kernel
                oopses galore and the processes get completely locked (they do not hang
                the machine though). I was able to save the dmesg output of two
                different attempts, and I attach them here in the hope that somebody can
                see something going wrong there (not me). During the first attempt, the
                stick got mounted as ext2 though it was an ext3. Thinking that that
                might be the problem, I did another attempt making sure it was mounted
                as an ext3, but no joy just the same.

                I am getting really frustrated. I will now try to reflash the old
                Linksys firmware and really hard test the device with huge files,
                perhaps multiple uploads/dowloads at once until it crashes, and then
                I'll talk to Linksys to have a replacement. I don't know what else to
                do.

                Thanks to everybody for all the help, I'll keep the list posted

                Nicola

                --
                Nicola Bernardini
                e-mail: nic.bern@...
                http://www.nicolabernardini.info
                GPG fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910
                Neither MS-Word nor MS-PowerPoint attachments please.

                On Tue, Apr 25, 2006 at 04:44:21PM +0200, Nicola Bernardini wrote:
                > Dear Bob,
                >
                > thank you very much for your reply! I was starting to feel somewhat alone :)
                >
                > On Tue, Apr 25, 2006 at 09:21:18AM +0100, Bob Cox wrote:
                > > In article <20060424063558.GH31372@...-ft.org>,
                > > Nicola Bernardini <nic.bern@...> wrote:
                > >
                > > > I have been following this list for some time now and have tried hard to
                > > > make my NSLU2 work the way I see it working for you all, but to no
                > > > avail. I usually use anywhere else Debian, so I am not a casual Debian
                > > > GNU/Linux user.
                > > >
                > > > I have tried all distributions (Unslug, OpenSlug, DebianSlug,
                > > > OpenDebianSlug):
                > > >
                > > > 1. Unslug and OpenSlug install, but then they crash upon transfer of
                > > > large files (let's say > 1 MB)
                > > >
                > > > 2. DebianSlug crashes during di (debian-installer)
                > > >
                > > > 3. OpenDebianSlug installs, but apt-get segfaults so there's no way
                > > > to get to the next step. I have reformatted the drive, and every
                > > > time it crashes in a fairly terminal way during different phases
                > > > (untarring the sarge tarball, apt-get dist-upgradeing, etc.) In
                > > > any case, it will not go beyong apt-get dist-upgrade.
                > > >
                > > > However (and this is the bad thing) both Linksys R29 and Linksys R63
                > > > work without problems (but do half has much of what I need) :(. This is
                > > > bad because I hardly can go bickering to the Linksys forums if their
                > > > firmware work.
                > >
                > > Nicola - you say it works ok using the Linksys firmware. Have you tried
                > > very large, intensive file transfers to your USB harddrive when using
                > > Linksys? What I am trying to get at is whether the problem is really
                > > the USB interface and/or the harddrive itself failing under heavy load
                > > (for example transferring large files, installing an OS or running
                > > apt-get as mentioned above). This *might* be the harddrive overheating?
                > >
                > > Just a thought - admittedly unlikely!
                >
                > I must say that I did not do many tests with Linksys firmware for three
                > reasons:
                >
                > 1) I don't need a simple file server as the Linksys is set to be; I need
                > a full-featured server as the OpenDebianSlug promises to be (and I
                > know very well it can be), so when I bought the NSLU2 almost a year
                > ago I flashed unslug then openslug and started having problems with
                > these
                >
                > 2) In addition to that, IIRC I initially did some tests with the Linksys
                > firmware and the large file test was killing the samba serving on me.
                > At the time, I though it was samba having problems (it happens to me
                > also on other servers).
                >
                > 3) To *really* revert back to the Linksys firmware would mean to
                > completely reformat my 200 GByte Maxtor One Touch drive which is now
                > half full of things which I would not know where to put, so I did my
                > tests with a 512 Mbytes memory stick.
                >
                > Which made me think that you might be right! I should try the
                > OpenDebianSlug installation on the 512 Mbytes memory stick.
                >
                > However, I must tell you that I considered the overheating problems some
                > months ago (I have very little time to devote to non-fully working
                > appliances, so it takes me months before I can come back to them :() and
                > I made some tests opening the case, adding fans to the disk etc. and
                > that was not the problem. The disk was perfectly cold and the NSLU2
                > keeps on oopsing and dying.
                >
                > Also: the OpenDebianSlug installation segfaults abruptly in the middle
                > of the very first apt-get dist-upgrade (step 12 of the documentation),
                > at around 70% of the building of the dependency tree. That is not really
                > where the disk-intensive part is, is'nt it? Another test I did yesterday
                > was to run a quick-and-dirty perl script which basically eats up all the
                > memory available and dies (thus basically releasing most of the RAM),
                > and *then* the apt-get dist-upgrade went to the end, started installing
                > but then died in the middle of the installation of coreutils. I attach
                > the perl script just for documentation.
                >
                > So: I will try again the installation and get back to the list as soon
                > as I have done the test (this won't be before Friday evening I'm afraid
                > :(). In the meantime, I just wonder if there is anywhere to be found a
                > diagnostic software that just does the diagnostics on the NSLU2...
                >
                > Thanks again Bob for your suggestions and for devoting some time to the
                > problem! I also looked at your slug page and envy your setup very much!
                > (that's exactly what I wanted to do, but I'm having bad luck)
                >
                > Nicola
                >
                > --
                > Nicola Bernardini
                > e-mail: nic.bern@...
                > http://www.nicolabernardini.info
                > GPG fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910
                > Neither MS-Word nor MS-PowerPoint attachments please.
                >

                ----------

                tered protocol family 2
                IP: routing cache hash table of 512 buckets, 4Kbytes
                TCP established hash table entries: 2048 (order: 2, 16384 bytes)
                TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
                TCP: Hash tables configured (established 2048 bind 2048)
                NET: Registered protocol family 1
                Vendor: Kingston Model: DataTraveler 2.0 Rev: 1.04
                Type: Direct-Access ANSI SCSI revision: 00
                SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                sda: Write Protect is off
                sda: Mode Sense: 23 00 00 00
                sda: assuming drive cache: write through
                SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                sda: Write Protect is off
                sda: Mode Sense: 23 00 00 00
                sda: assuming drive cache: write through
                sda: sda1
                Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
                usb-storage: device scan complete
                VFS: Mounted root (jffs2 filesystem).
                Freeing init memory: 80K
                VFS: Can't find ext3 filesystem on dev sda1.
                ixp400: module license 'unspecified' taints kernel.
                Module init.
                ixp425_eth:
                Initializing IXP425 NPE Ethernet driver software v. 1.1A
                ixp425_eth: CPU clock speed (approx) = 0 MHz
                [error] ixEthMiiPhyScan : unexpected Mii PHY ID 00008201
                ixp425_eth: npe0 is using the PHY at address 0
                ixp425_eth: npe1 is using the PHY at address 1
                ixp425_eth: ixEthMiiLinkStatus failed on PHY0.
                Can't determine
                the auto negotiated parameters. Using default values.
                FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
                SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                sda: Write Protect is off
                sda: Mode Sense: 23 00 00 00
                sda: assuming drive cache: write through
                sda: sda1 sda2
                SCSI device sda: 1003520 512-byte hdwr sectors (514 MB)
                sda: Write Protect is off
                sda: Mode Sense: 23 00 00 00
                sda: assuming drive cache: write through
                sda: sda1 sda2
                Adding 101112k swap on /dev/sda2. Priority:-1 extents:1
                FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
                FAT: bogus number of reserved sectors
                VFS: Can't find a valid FAT filesystem on dev sda1.
                EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2

                Unable to handle kernel NULL pointer dereference at virtual address 00000000
                pgd = c0004000
                [00000000] *pgd=00000000
                Internal error: Oops: 817 [#1]
                Modules linked in: nls_utf8 nls_cp437 ext2 vfat fat nls_base ixp425_eth ixp400 ext3 jbd mbcache
                CPU: 0
                pc : [<c00b7714>] lr : [<00000036>] Tainted: P
                sp : c02cbd60 ip : 00000000 fp : c02cbda0
                r10: 0000000e r9 : 00000001 r8 : 00000000
                r7 : 00000000 r6 : 00000000 r5 : c05f53cc r4 : ffffffff
                r3 : 00000000 r2 : 00000015 r1 : c05f54a0 r0 : 00000036
                Flags: nZCv IRQs off FIQs on Mode SVC_32 Segment kernel
                Control: 39FF Table: 00564000 DAC: 00000017
                Process pdflush (pid: 55, stack limit = 0xc02ca194)
                Stack: (0xc02cbd60 to 0xc02cc000)
                bd60: 0000000e c02cbe10 0000003f c02cbe10 c05c8508 00000040 c02cbe10 c02cbdfc
                bd80: ffffffff c1d6c800 c05c8504 c05c8504 c02cbf50 c02cbdbc c02cbda4 c004ea60
                bda0: c00b75dc 00000000 c02cbe08 c02cbf64 c02cbdd4 c02cbdc0 c0058438 c004ea30
                bdc0: c02cbe10 00000000 c02cbe70 c02cbdd8 c008f938 c0058414 0000000e c006ddd4
                bde0: 00000080 00000000 00000000 00000000 00000000 c032c6e4 bf0d67f8 00000000
                be00: 00000000 00000000 00000000 00000000 c01f64e0 bf0d7290 c0070c24 c01e1be0
                be20: c103b7e0 00000006 00000000 c05c8608 00000000 c05c86a8 c1d6c800 c02cbe80
                be40: c02cbe4c bf0d7d40 00000007 c05c8464 c05c8464 c1d6c800 c05c8504 00000000
                be60: c02cbf50 c02cbe80 c02cbe74 c00547dc c008f5e0 c02cbee4 c02cbe84 c008dfa8
                be80: c00547b4 00011314 c02cbed4 c02cbe98 c01805cc c003babc 00100100 00200200
                bea0: 00011314 c02cbec4 c02cbeb4 bf0d64ec c02cbed0 c02cbec0 bf0d64ec c1d6c800
                bec0: c05c8464 c032c6e4 c02ca000 c02cbf50 c1d6c884 00000000 c02cbf14 c02cbee8
                bee0: c008e658 c008de5c 00011f17 c1d6c800 c1d6c840 c01b3d9c c02cbf50 c01b12c0
                bf00: 00000000 00000000 c02cbf34 c02cbf18 c008e888 c008e474 00000000 c02cbf50
                bf20: c02cbf90 c02ca000 c02cbf8c c02cbf38 c0054444 c008e820 00000ccc 00000333
                bf40: 00000344 00000000 0000025d 00000000 00000000 00000000 00000000 000003c3
                bf60: 00000000 00000000 00000000 00000000 00000000 80000000 00000001 c01b3700
                bf80: c02cbfc8 c02cbf90 c0055098 c00543b8 c02b77e0 c00543ac 00000000 c02cbf9c
                bfa0: c02cbf9c 00011d95 00000000 c02ca000 c0241f6c c0054f70 fffffffc c02cbff4
                bfc0: c02cbfcc c0047508 c0054f7c ffffffff ffffffff 00000000 00000000 00000000
                bfe0: 00000000 00000000 00000000 c02cbff8 c00354f8 c0047430 95a6d24d 4a592d90
                Backtrace:
                Function entered at [<c00b75d0>] from [<c004ea60>]
                Function entered at [<c004ea24>] from [<c0058438>]
                r5 = C02CBF64 r4 = C02CBE08
                Function entered at [<c0058408>] from [<c008f938>]
                r4 = 00000000
                Function entered at [<c008f5d4>] from [<c00547dc>]
                Function entered at [<c00547a8>] from [<c008dfa8>]
                Function entered at [<c008de50>] from [<c008e658>]
                Function entered at [<c008e468>] from [<c008e888>]
                Function entered at [<c008e814>] from [<c0054444>]
                r7 = C02CA000 r6 = C02CBF90 r5 = C02CBF50 r4 = 00000000
                Function entered at [<c00543ac>] from [<c0055098>]
                r5 = C01B3700 r4 = 00000001
                Function entered at [<c0054f70>] from [<c0047508>]
                r8 = FFFFFFFC r7 = C0054F70 r6 = C0241F6C r5 = C02CA000
                r4 = 00000000
                Function entered at [<c0047424>] from [<c00354f8>]
                r8 = 00000000 r7 = 00000000 r6 = 00000000 r5 = 00000000
                r4 = 00000000
                Code: e3130001 0a000009 e5913004 e3530000 (05833000)
                <1>Unable to handle kernel paging request at virtual address 00200004
                pgd = c0b48000
                [00200004] *pgd=00000000
                Internal error: Oops: f5 [#2]
                Modules linked in: nls_utf8 nls_cp437 ext2 vfat fat nls_base ixp425_eth ixp400 ext3 jbd mbcache
                CPU: 0
                pc : [<c004e9fc>] lr : [<00000000>] Tainted: P
                sp : c1a55e70 ip : 00000001 fp : c1a55e80
                r10: 00000000 r9 : c1a55e98 r8 : c05d117c
                r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : c1a55ea0
                r3 : 80000093 r2 : 00200000 r1 : 80000093 r0 : 00000002
                Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment user
                Control: 39FF Table: 00B48000 DAC: 00000015
                Process rm (pid: 1017, stack limit = 0xc1a54194)
                Stack: (0xc1a55e70 to 0xc1a56000)
                5e60: c1a55e98 c1a55e94 c1a55e84 c0058400
                5e80: c004e9b8 00000fff c1a55f00 c1a55e98 c0058730 c00583e8 00000000 00000000
                5ea0: c01e1e00 00200000 c008dce8 c05d1e9c c05d10dc c05d1dfc fffffffe c05d10dc
                5ec0: c05d1dfc 00000000 44555c75 c1a55f00 c1a55edc bf0d8bc8 c05d10dc bf0de5e0
                5ee0: c0672000 c1a55f48 c001ce44 c1a54000 401d6000 c1a55f18 c1a55f04 c0086244
                5f00: c005863c c05d10dc c1da9f6c c1a55f2c c1a55f1c c008561c c00861cc c1da9f6c
                5f20: c1a55f44 c1a55f30 c0083410 c0085594 00000000 c1da9f6c c1a55fa4 c1a55f48
                5f40: c007bf68 c0083254 c1ae3a1c c0235780 d9ae7e01 00000007 c0672014 00000010
                5f60: 00000000 00000000 c0083254 c1dfb1e0 00000000 c022a380 00000006 c1a55fa4
                5f80: c1a55f8c c006b194 00090140 00091198 00000004 00000028 00000000 c1a55fa8
                5fa0: c001ccc0 c007bea0 00090140 c0023f5c 00090140 00000000 00000000 00000000
                5fc0: 00090140 00091198 00000004 00090160 00000000 00000f0c 401d6000 0000cfd4
                5fe0: 0007f474 be962c90 0005ce9c 40175864 60000010 00090140 5ab8e016 cca8c41d
                Backtrace:
                Function entered at [<c004e9ac>] from [<c0058400>]
                r4 = C1A55E98
                Function entered at [<c00583dc>] from [<c0058730>]
                r4 = 00000FFF
                Function entered at [<c0058630>] from [<c0086244>]
                Function entered at [<c00861c0>] from [<c008561c>]
                r5 = C1DA9F6C r4 = C05D10DC
                Function entered at [<c0085588>] from [<c0083410>]
                r4 = C1DA9F6C
                Function entered at [<c0083248>] from [<c007bf68>]
                r5 = C1DA9F6C r4 = 00000000
                Function entered at [<c007be94>] from [<c001ccc0>]
                r7 = 00000028 r6 = 00000004 r5 = 00091198 r4 = 00090140
                Code: e794210c e10f1000 e3813080 e121f003 (e5923004)


                ----------

                el.
                Module init.
                ixp425_eth:
                Initializing IXP425 NPE Ethernet driver software v. 1.1A
                ixp425_eth: CPU clock speed (approx) = 0 MHz
                [error] ixEthMiiPhyScan : unexpected Mii PHY ID 00008201
                ixp425_eth: npe0 is using the PHY at address 0
                ixp425_eth: npe1 is using the PHY at address 1
                ixp425_eth: ixEthMiiLinkStatus failed on PHY0.
                Can't determine
                the auto negotiated parameters. Using default values.
                FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
                FAT: bogus number of reserved sectors
                VFS: Can't find a valid FAT filesystem on dev sda1.
                EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2

                EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
                Adding 101112k swap on /dev/sda2. Priority:-1 extents:1
                kjournald starting. Commit interval 5 seconds
                EXT3 FS on sda1, internal journal
                EXT3-fs: mounted filesystem with ordered data mode.
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 1024
                Aborting journal on device sda1.
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 2048
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 3072
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 4096
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 5120
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 6144
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 7168
                EXT3-fs error (device sda1): ext3_readdir: directory #57346 contains a hole at offset 8192
                ext3_abort called.
                EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
                Remounting filesystem read-only
                kjournald starting. Commit interval 5 seconds
                EXT3 FS on sda1, internal journal
                EXT3-fs: mounted filesystem with ordered data mode.
                Unable to handle kernel paging request at virtual address 00200004
                pgd = c0004000
                [00200004] *pgd=00000000
                Internal error: Oops: f5 [#1]
                Modules linked in: ext2 vfat fat nls_base ixp425_eth ixp400 ext3 jbd mbcache
                CPU: 0
                pc : [<c004e9fc>] lr : [<00000000>] Tainted: P
                sp : c02d1e5c ip : 00000001 fp : c02d1e6c
                r10: c0c83f50 r9 : c02d1e84 r8 : ffffffff
                r7 : 00000000 r6 : c01b43b4 r5 : 00000000 r4 : c02d1e8c
                r3 : 80000093 r2 : 00200000 r1 : 80000093 r0 : 00000002
                Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment kernel
                Control: 39FF Table: 01AE0000 DAC: 00000017
                Process kswapd0 (pid: 56, stack limit = 0xc02d0194)
                Stack: (0xc02d1e5c to 0xc02d2000)
                1e40: c02d1e84
                1e60: c02d1e80 c02d1e70 c0058400 c004e9b8 c0c83eb0 c02d1eec c02d1e84 c00589dc
                1e80: c00583e8 00000000 00000000 c01e1480 00200000 c01fbfc0 c01e1280 c01e9f40
                1ea0: c01e9f60 c01e11c0 c01e11a0 c01e12c0 c01e9740 c01e9660 c01e9600 c01e96a0
                1ec0: c05970d0 c0c83eb0 c0c83eb8 c01b43b4 00000064 c01b43a4 c02d1ef8 00000038
                1ee0: c02d1f28 c02d1ef0 c0085728 c00588e4 00000038 00000080 c05970d8 c0cf7290
                1f00: 00000082 00000000 00000040 00000082 c023fb40 000000d0 c01b3890 c02d1f5c
                1f20: c02d1f2c c0058dec c0085630 000015f9 00000020 00000001 c01b3224 00000000
                1f40: c01b3224 00000000 00000000 0000000b c02d1ff4 c02d1f60 c005a35c c0058d24
                1f60: 00000000 00000000 000015f9 c02d1f7c 00000000 00000000 00000000 00000002
                1f80: 00000020 00000000 00000000 0000027e 00000020 0000000b 000000d0 00000000
                1fa0: 00000020 00000000 c02b7560 c0047998 c02d1fc4 c02d1fc4 00000000 c02b7560
                1fc0: c0047998 c02d1fc4 c02d1fc4 00000000 00000000 00000000 00000000 00000000
                1fe0: 00000000 00000000 00000000 c02d1ff8 c00354f8 c005a0ac 95a6d24d 4a592db0
                Backtrace:
                Function entered at [<c004e9ac>] from [<c0058400>]
                r4 = C02D1E84
                Function entered at [<c00583dc>] from [<c00589dc>]
                r4 = C0C83EB0
                Function entered at [<c00588d8>] from [<c0085728>]
                Function entered at [<c0085624>] from [<c0058dec>]
                Function entered at [<c0058d18>] from [<c005a35c>]
                Function entered at [<c005a0a0>] from [<c00354f8>]
                Code: e794210c e10f1000 e3813080 e121f003 (e5923004)
                <1>Unable to handle kernel paging request at virtual address 00200000
                pgd = c05bc000
                [00200000] *pgd=00000000
                Internal error: Oops: f5 [#2]
                Modules linked in: ext2 vfat fat nls_base ixp425_eth ixp400 ext3 jbd mbcache
                CPU: 0
                pc : [<bf006e7c>] lr : [<bf004bac>] Tainted: P
                sp : c09fbc84 ip : 00200000 fp : c09fbc98
                r10: c09fbe40 r9 : c05f2698 r8 : c05e24ac
                r7 : c05f68d0 r6 : 00000000 r5 : c01e1f20 r4 : c05f68d0
                r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : c05e24ac
                Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment user
                Control: 39FF Table: 005BC000 DAC: 00000015
                Process dmesg (pid: 1032, stack limit = 0xc09fa194)
                Stack: (0xc09fbc84 to 0xc09fc000)
                bc80: c05f68d0 c01e1f20 c09fbcc0 c09fbc9c bf004bac bf006e64 00000001
                bca0: c05f2698 c01e1f20 00000001 00000001 c01b3224 c09fbcd0 c09fbcc4 c006f050
                bcc0: bf004ad0 c09fbe30 c09fbcd4 c0059ad4 c006f00c 00000017 00000000 c01b32fc
                bce0: ffffffff c01b32f4 00000007 00000003 c09fbcf0 c09fbcf0 00000021 c01fc118
                bd00: c01e1f58 00000021 c09fbd08 c09fbd08 c09fbd10 c09fbd10 c09fbd18 c09fbd18
                bd20: c008423c c00b8858 c032baa4 00000000 c09fbf34 c09fa000 c037c5a0 00000000
                bd40: c032baa4 c09fa000 00000009 00000001 c01e1d60 c01e1e60 c01e1ea0 c01e1d80
                bd60: c01e1b60 c01e1da0 c01e1ee0 c01e1f00 c01e1dc0 c01e18c0 c01e1d00 c01e1d20
                bd80: c01e1b40 c01e1d40 00000000 00000001 00000020 00000001 c02568d8 c05b1e00
                bda0: c09fbddc 00000200 00000200 c09fbe70 c020e0e0 00000000 c004f25c c02568d8
                bdc0: 00000000 ffffffff 00000000 00000001 c020a360 c020ba40 c0210f00 c020f9c0
                bde0: c020a020 c02113a0 c02113c0 c0211380 c0215200 c0215220 c020a060 c020a040
                be00: c020a7c0 c020a300 c01b35b0 c09fbe40 00000001 00000000 c09fbea0 00000000
                be20: 00000008 c09fbe8c c09fbe34 c0059fa4 c0058f88 00001699 00000000 000000d2
                be40: 00000020 00000018 00000000 00000314 00000020 00000008 000000d2 00000000
                be60: 00000020 00000000 00000000 000000d2 c01b35b0 00000000 00000000 c1f42340
                be80: c09fbecc c09fbe90 c005328c c0059e90 00000000 00000000 00000000 00000010
                bea0: 00000000 c1741a40 0000005f c12cf3e0 00090000 c1741a40 c0015480 c01c9278
                bec0: c09fbf04 c09fbed0 c005d150 c0053068 00000000 00000000 00000001 c1741a40
                bee0: 00000000 c12cf3e0 00090000 00000000 00000817 c05bc000 c09fbf4c c09fbf08
                bf00: c005d68c c005d0bc c1741a40 c05bc000 c0015480 0008e000 c05bc000 00000800
                bf20: c0015480 ffffffeb c1f42340 c12cf3e0 c0015480 c00154ac 00000817 00090054
                bf40: c09fbf88 c09fbf50 c0023d14 c005d594 c12cf3e0 0008e000 00000800 c09fbfb0
                bf60: 00000817 c09fbfec c01b1424 00090054 c09fbfb0 00000f0c 401d6000 c09fbfac
                bf80: c09fbf8c c0023f8c c0023c70 ffffffff c09fbfec 00000004 c01b101c 0000006b
                bfa0: 00000000 c09fbfb0 c001cc60 c0023f5c 0008e048 0001efb1 00002009 00000000
                bfc0: 00090050 401d88f0 00000004 00002008 0000006b 00000f0c 401d6000 0000cfd4
                bfe0: 00000000 be9bdd94 401d8c94 40134ac0 60000010 ffffffff 9b6ec3ad 6d20276d
                Backtrace:
                Function entered at [<bf006e58>] from [<bf004bac>]
                r5 = C01E1F20 r4 = C05F68D0
                Function entered at [<bf004ac4>] from [<c006f050>]
                r8 = C01B3224 r7 = 00000001 r6 = 00000001 r5 = C01E1F20
                r4 = C05F2698
                Function entered at [<c006f000>] from [<c0059ad4>]
                Function entered at [<c0058f7c>] from [<c0059fa4>]
                Function entered at [<c0059e84>] from [<c005328c>]
                Function entered at [<c005305c>] from [<c005d150>]
                Function entered at [<c005d0b0>] from [<c005d68c>]
                Function entered at [<c005d588>] from [<c0023d14>]
                Function entered at [<c0023c64>] from [<c0023f8c>]
                Function entered at [<c0023f50>] from [<c001cc60>]
                r8 = 0000006B r7 = C01B101C r6 = 00000004 r5 = C09FBFEC
                r4 = FFFFFFFF
                Code: e15c0001 0a00001c e590202c e5903030 (e59c4000)



                [Non-text portions of this message have been removed]
              Your message has been successfully submitted and would be delivered to recipients shortly.