[microblaze-uclinux] Re: kernel BUG at sched.c:562!

[DeviPrasad Natesan <ndprasad@xxxxxxxxx>]

Doing some single-stepping, it does fail while running _syscall3()
while trying to run run_init_process("/sbin/init");  in init/main.c.
Also sys_execve() returns success during this call.

Please let me know if i miss something that causes this error.

thanx
- deviprasad

On 10/28/05, DeviPrasad Natesan <ndprasad@xxxxxxxxx> wrote:
> Hi,
> I am getting a kernel bug right after romfs gets mounted. Please let
> me know is there anything i am missing. I have console log below. I am
> right now using ML403 target configured for microblaze.  Is there any
> obvious stuff i am missing.
>
> ************************************************************************
> Linux version 2.4.31-uc0 (mblaze@DeviPrasad) (gcc version 3.4.1 (
> Xilinx EDK 8.1 Build EDK_I.15 290805On node 0 totalpages: 8192
> zone(0): 8192 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> CPU: MICROBLAZE
> Kernel command line: .�
> Console: xmbserial on UARTLite
> Calibrating delay loop... 49.76 BogoMIPS
> Memory: 32MB = 32MB total
> Memory: 30304KB available (1064K code, 1037K data, 52K init)
> Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
> Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Microblaze UARTlite serial driver version 1.00
> ttyS0 at 0x40600000 (irq = 1) is a Microblaze UARTlite
> Starting kswapd
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> eth0: using fifo mode.
> eth0: Xilinx EMAC #0 at 0x40C00000 mapped to 0x40C00000, irq=3
> eth0: id 2.0h; block id 7, type 1
> uclinux[mtd]: RAM probe address=0x24140b1c size=0xcd000
> mtd: Giving out device 0 to RAM
> uclinux[mtd]: root filesystem index=0
> MicroBlaze auto-config flash probe(0xff800000,8388608,4): 800000 at ff800000
> cfi_cmdset_0001: Erase suspend on write enabled
> 0: offset=0x0,size=0x40000,blocks=32
> Using buffer write method
> Creating 8 MTD partitions on "Flash":
> 0x00000000-0x00004000 : "Bootloader"
> mtd: partition "Bootloader" doesn't end on an erase block -- force read-only
> mtd: Giving out device 1 to Bootloader
> 0x00004000-0x00008000 : "Bootargs"
> mtd: partition "Bootargs" doesn't start on an erase block boundary --
> force read-only
> mtd: Giving out device 2 to Bootargs
> 0x00008000-0x0000c000 : "MAC"
> mtd: partition "MAC" doesn't start on an erase block boundary -- force read-only
> mtd: Giving out device 3 to MAC
> 0x00010000-0x00020000 : "Config"
> mtd: partition "Config" doesn't start on an erase block boundary --
> force read-only
> mtd: Giving out device 4 to Config
> 0x0000c000-0x00010000 : "Spare"
> mtd: partition "Spare" doesn't start on an erase block boundary --
> force read-only
> mtd: Giving out device 5 to Spare
> 0x00100000-0x00400000 : "Image"
> mtd: Giving out device 6 to Image
> 0x00400000-0x00800000 : "JFFS2"
> mtd: Giving out device 7 to JFFS2
> 0x00000000-0x00800000 : "Flash"
> mtd: Giving out device 8 to Flash
> MicroBlaze auto-config ram probe(0x24140b1c,839680,4): cd000 at 24140b1c
> Creating 1 MTD partitions on "RAM":
> 0x00000000-0x000cd000 : "Romfs"
> mtd: Giving out device 9 to Romfs
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind 4096)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (romfs filesystem) readonly.
> Freeing init memory: 52K
> kernel BUG at sched.c:562!
>
>
> ************************************************************************
>
>
> On 10/27/05, DeviPrasad Natesan <ndprasad@xxxxxxxxx> wrote:
> > Yes, that is right. When i updated my compiler toolchain from the
> > website, this problem disappeared.
> >
> > Thanx a lot john and vasanth.
> > - Prasad
> >
> >
> > On 10/26/05, John Williams <jwilliams@xxxxxxxxxxxxxx> wrote:
> > > Hi Prasad,
> > >
> > > DeviPrasad Natesan wrote:
> > > > Hi, I am trying to get uClinux with microblaze up and running in ML403
> > > > platform (virtex-4) before our custom board (with spartan3) arrives.
> > > > When trying to bring up the kernel, I get crash in the timer bottom
> > > > half timer_bh() and if i comment out the function run_timer_list()
> > > > everything works fine and i could proceed further.
> > > > When i was browsing the archives of the mailing list i found some-one
> > > > else did get same kinda error posted few months back
> > > > (http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2005/07/msg00069.html)
> > > >
> > > > Just wondering what i missed, that causes this error. I have attached
> > > > my autoconfig.in along with this. Any help on this will be
> > > > appreciated.
> > >
> > > This crash was being caused by a compiler bug - can you please try
> > > downloading the latest version of the mb-gcc / uClinux compiler
> > > toolchain from the website?  Don't forget to "make clean" before you
> > > rebuild with the new compiler!
> > >
> > > Regards,
> > >
> > > John
> > > ___________________________
> > > microblaze-uclinux mailing list
> > > microblaze-uclinux@xxxxxxxxxxxxxx
> > > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> > > Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> > >
> > >
> >
>

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/