Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

[Martin Michlmayr]

* Ross Burton [EMAIL PROTECTED] [2008-11-17 10:59]:
 Installing ifplugd and setting INTERFACES in /etc/default/ifplugd to
 auto causes the bug for me.  auto may well be the default.

It happens because of Riku's LED driver.  When I compile a kernel
without the driver, I can start ifplugd just fine.

Riku, the best way to reproduce this is to install ifplugd (but _not_
change INTERFACES in /etc/default/ifplugd to auto) and then you can
trigger it with:
  /usr/sbin/ifplugd -i eth0

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

[Riku Voipio]

On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
 It happens because of Riku's LED driver.  When I compile a kernel
 without the driver, I can start ifplugd just fine.

 Riku, the best way to reproduce this is to install ifplugd (but _not_
 change INTERFACES in /etc/default/ifplugd to auto) and then you can
 trigger it with:
   /usr/sbin/ifplugd -i eth0

I see, ifplugd tries to beep. Why when ifplugd is calling it ends up
in atomic context is unclear to me, using schedule_work should make
it more safe anyway. will convert when back at device to test..

-- 
rm -rf only sounds scary if you don't have backups


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

[Bill Gatliff]

Riku Voipio wrote:
 On Tue, Nov 18, 2008 at 01:37:11PM +0100, Martin Michlmayr wrote:
 It happens because of Riku's LED driver.  When I compile a kernel
 without the driver, I can start ifplugd just fine.
 
 Riku, the best way to reproduce this is to install ifplugd (but _not_
 change INTERFACES in /etc/default/ifplugd to auto) and then you can
 trigger it with:
   /usr/sbin/ifplugd -i eth0
 
 I see, ifplugd tries to beep. Why when ifplugd is calling it ends up
 in atomic context is unclear to me, using schedule_work should make
 it more safe anyway. will convert when back at device to test..

I haven't looked at any of the related code.

Does iop32x use gpiolib?  Maybe the GPIO pin that controls the beep is
at the end of an i2c GPIO expander.  If that's the case, then there is
at least one sleep whilst waiting for the i2c bus controller to
complete the transaction.


b.g.
-- 
Bill Gatliff
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

[Martin Michlmayr]

* Ross Burton [EMAIL PROTECTED] [2008-11-16 15:47]:
 On Sun, 2008-11-16 at 13:07 +, Ross Burton wrote:
  I'm going to try an flash an older kernel and hope that fixes it now...
 
 I discovered that ifplugd was causing this, I'm guessing a locking bug
 in r8139.ko?  I've disabled ifplugd for now and it is booting again.  Is
 this is a known issue or should I file a bug report?

I'm not sure if it's known upstream, but I didn't know about it.  Does
it also happen with 2.6.25?  Can I reproduce this simply be installing
the ifplugd or do I have to configure it in some way? (I don't know
ifplugd at all.)
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: BUG booting 2.6.26-1-iop32x on Thecus N2100

[Martin Michlmayr]

* Ross Burton [EMAIL PROTECTED] [2008-11-17 10:59]:
 Installing ifplugd and setting INTERFACES in /etc/default/ifplugd to
 auto causes the bug for me.  auto may well be the default.

OK, I can reproduce it and it's a regression from 2.6.25.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

BUG booting 2.6.26-1-iop32x on Thecus N2100

[Ross Burton]

Hi,

I finally got around to putting a serial port onto my semibricked N2100
and got a log of the boot.  Attached is the full log, the interesting
line is:

[42949526.36] BUG: scheduling while atomic: swapper/0/0x0100

:(

I'm going to try an flash an older kernel and hope that fixes it now...

Cheers,
Ross
-- 
Ross Burton mail: [EMAIL PROTECTED]
  jabber: [EMAIL PROTECTED]
   www: http://burtonini.com
+RST=No
Transfer to factory test Mode : No
Reset default set:Normal
Thecus: Found PCI device Vendor ID=0x10EC
Vendor0x10ec
Device0x8169
 Allocate cyg_pci_io_base=0x9100
 Allocate cyg_pci_memory_base=0x4100
Thecus: Found PCI device Vendor ID=0x10EC
Vendor0x10ec
Device0x8169
 Allocate cyg_pci_io_base=0x9200
 Allocate cyg_pci_memory_base=0x4200
Thecus: Found PCI device Vendor ID=0x1095
Vendor0x1095
Device0x3512
 Allocate cyg_pci_io_base=0x9208
 Allocate cyg_pci_io_base=0x920c
 Allocate cyg_pci_io_base=0x9218
 Allocate cyg_pci_io_base=0x921c
 Allocate cyg_pci_io_base=0x9230
 Allocate cyg_pci_memory_base=0x4400
Thecus: Found PCI device Vendor ID=0x1106
Thecus: Found PCI device Vendor ID=0x1106
Thecus: Found PCI device Vendor ID=0x1106
Vendor0x1106
Device0x3104
 Allocate cyg_pci_memory_base=0x4500
Thecus: Found PCI device Vendor ID=0x1814
Vendor0x1814
Device0x0302
 Allocate cyg_pci_memory_base=0x4001
PCI: device already configured
rtl-eth0: RTL8169s/8110s Gigabit Ethernet driver 2.2 at 0xb000, 
00:14:fd:10:1c:ac
rtl-eth0: Auto-negotiation Enabled.
PCI: device already configured
eth1 found: bus[0] dev[2] base[b100]
rtl-eth1: RTL8169s/8110s Gigabit Ethernet driver 2.2 at 0xb100, 
00:14:fd:10:1c:ad
Ethernet rtl-eth0: MAC address 00:14:fd:10:1c:ac
IP: 192.168.1.100/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0, DNS server IP: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROM]
Red Hat certified release, version 1.93 - built 17:25:00, Feb  6 2007

Platform: THECUS N2100 (IOP80219) 
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x-0x2000, 0x0004b890-0x1ffd1000 available, total: 512 MB
FLASH: 0xf000 - 0xf100, 128 blocks of 0x0002 bytes each.
== Executing boot script in 3.000 seconds - enter ^C to abort
RedBoot thecus_setip
RedBoot fis load ramdisk
RedBoot fis load kernel
RedBoot exec -c console=ttyS0,115200 root=/dev/ram0 initrd=0xa080,42M 
[EMAIL PROTECTED]
Build ATAG
ATAG_MEM: Overwrite ram_end with real_region_top=0x2000, memsize=512 M
[EMAIL PROTECTED], MACH_TYPE=1101
Using base address 0x0020 and length 0x0016
Uncompressing 
Linux
 done, booting the kernel.
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.26-1-iop32x (Debian 2.6.26-8) ([EMAIL 
PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 Fri 
Oct 10 02:17:51 UTC 2008
[0.00] CPU: XScale-80219 [69052e30] revision 0 (ARMv5TE), cr=397f
[0.00] Machine: Thecus N2100
[0.00] Memory policy: ECC disabled, Data cache writeback
[0.00] CPU0: D VIVT undefined 5 cache
[0.00] CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 
sets
[0.00] CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 
sets
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 130048
[0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram0 
initrd=0xa080,42M [EMAIL PROTECTED]
[0.00] PID hash table entries: 2048 (order: 11, 8192 bytes)
[42949372.96] Console: colour dummy device 80x30
[42949372.96] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[42949372.96] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[42949373.01] Memory: 512MB = 512MB total
[42949373.01] Memory: 473600KB available (2604K code, 286K data, 112K init)
[42949373.24] Security Framework initialized
[42949373.24] SELinux:  Disabled at boot.
[42949373.24] Capability LSM initialized
[42949373.24] Mount-cache hash table entries: 512
[42949373.24] Initializing cgroup subsys ns
[42949373.24] Initializing cgroup subsys cpuacct
[42949373.24] Initializing cgroup subsys devices
[42949373.24] CPU: Testing write buffer coherency: ok
[42949373.24] net_namespace: 652 bytes
[42949373.24] NET: Registered protocol family 16
[42949373.25] PCI: bus0: Fast back to back transfers disabled
[42949373.29] NET: Registered protocol family 2
[42949373.38] IP route cache hash table entries: 16384 (order: 4, 65536 
bytes)
[42949373.38] TCP established hash table entries: 65536 (order: 7, 524288 
bytes)
[42949373.38] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)