2008-02-18 09:40:50     Error while booting: kobject_add failed for physmap-flash.0

Document created by Aaronwu Employee on Aug 5, 2013
Version 1Show Document
  • View in full screen mode

2008-02-18 09:40:50     Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51200    Hi all

 

I downloaded recently the SVN trunk and compiled it for the EZ-kit 548 board (I've done that previously as well without any problems, so its not the first time). The reason I downloaded a recent trunk is to compile it with the flags "-O3 -ffast-math -fmath-fp"

 

Compiling goes fine without errors, image is built. When I download the image and boot ucLinux with u-boot then the following happens... any ideas?

 

 

Thanks in advance

Piggebu

 

 

bfin> bootm

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.22.16-ADI-2008R2-pre-s

   Created:      2008-02-15  21:21:23 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    8764172 Bytes =  8.4 MB

   Load Address: 00001000

   Entry Point:  00001000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 1000

Linux version 2.6.22.16-ADI-2008R2-pre-svn4195 (devel@uCLinuxHost) (gcc version 4.1.2 (ADI svn)) #22 Fri Feb 158

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00001000-0x001cc4d0

  rodata    = 0x001cc4d0-0x0025c8b4

  bss       = 0x0025c8c0-0x00278238

  data      = 0x00278238-0x0029e000

    stack   = 0x0029c000-0x0029e000

  init      = 0x0029e000-0x009b9000

  available = 0x009b9000-0x03dff000

  DMA Zone  = 0x03e00000-0x04000000

Hardware Trace Active and Enabled

Blackfin support (C) 2004-2008 Analog Devices, Inc.

Compiled for ADSP-BF549 Rev 0.0

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists.  Total pages: 15748

Kernel command line: root=/dev/mtdblock0 rw console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

Console: colour dummy device 80x25

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 52944k/65536k RAM, (7276k init code, 1837k kernel code, 839k data, 2048k dma, 588k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Data A SRAM: 16 KB (15 KB free)

Blackfin Data B SRAM: 16 KB (16 KB free)

Blackfin Instruction SRAM: 48 KB (42 KB free)

Security Framework v1.0.0 initialized

Capability LSM initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_init(): registering device resources

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

musb_hdrc: version 6.0, ?dma?, host, debug=0

musb_hdrc: kernel must blacklist external hubs

musb_hdrc: USB Host mode controller at ffc03c00 using PIO, IRQ 82

musb_hdrc musb_hdrc.0: MUSB HDRC host driver

musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: Product: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.22.16-ADI-2008R2-pre-svn4195 musb-hcd

usb usb1: SerialNumber: musb_hdrc.0

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

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)

TCP reno registered

yaffs Feb 15 2008 21:19:37 Installing.

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bf54x-lq043: FrameBuffer initializing...

dma_alloc_init: dma_page @ 0x03531000 - 512 pages at 0x03e00000

Console: switching to colour frame buffer device 60x34

bfin-otp: initialized

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 48) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

smsc911x: Driver version 2007-07-13.

Linux video capture interface: v2.00

usbcore: registered new interface driver dabusb

drivers/media/video/dabusb.c: v1.54:DAB-USB Interface Driver for Linux (c)1999

SCSI Media Changer driver v0.25

register bfin atapi driver

scsi0 : pata-bf54x

ata1: PATA max UDMA/66 cmd 0x00000000 ctl 0xffc03800 bmdma 0x00000000 irq 68

ata1.00: ATA-6: TOSHIBA MK4032GAX, AD101A, max UDMA/100

ata1.00: 78140160 sectors, multi 16: LBA48

ata1.00: configured for UDMA/66

blk_queue_max_hw_segments: set to minimum 1

scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MK4032GA AD10 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

sda: sda1

sd 0:0:0:0: [sda] Attached SCSI disk

sd 0:0:0:0: Attached scsi generic sg0 type 0

physmap platform flash device: 01000000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

Intel/Sharp Extended Query Table at 0x010A

  Unknown Intel/Sharp Extended Query version 1.5.

gen_probe: No supported Vendor Command Set found

physmap-flash physmap-flash.0: map_probe failed

kobject_add failed for physmap-flash.0 with -EEXIST, don't try to register things with the same name in the sam.

Hardware Trace:

   0 Target : <0x000046f0> { _dump_stack + 0x0 }

     Source : <0x000ca444> { _kobject_shadow_add + 0xd4 }

   1 Target : <0x000ca444> { _kobject_shadow_add + 0xd4 }

     Source : <0x000ca488> { _kobject_shadow_add + 0x118 }

   2 Target : <0x000ca488> { _kobject_shadow_add + 0x118 }

     Source : <0x0000cdea> { _printk + 0x16 }

   3 Target : <0x0000cde6> { _printk + 0x12 }

     Source : <0x0000cc9c> { _vprintk + 0x1b8 }

   4 Target : <0x0000cc90> { _vprintk + 0x1ac }

     Source : <0xffa00c82> { __common_int_entry + 0xca }

   5 Target : <0xffa00c20> { __common_int_entry + 0x68 }

     Source : <0xffa00a60> { _return_from_int + 0x58 }

   6 Target : <0xffa00a60> { _return_from_int + 0x58 }

     Source : <0xffa00a36> { _return_from_int + 0x2e }

   7 Target : <0xffa00a08> { _return_from_int + 0x0 }

     Source : <0xffa00c1c> { __common_int_entry + 0x64 }

   8 Target : <0xffa00c1a> { __common_int_entry + 0x62 }

     Source : <0xffa003a0> { _asm_do_IRQ + 0x68 }

   9 Target : <0xffa00398> { _asm_do_IRQ + 0x60 }

     Source : <0x00010eaa> { __local_bh_enable + 0x3e }

  10 Target : <0x00010e6c> { __local_bh_enable + 0x0 }

     Source : <0x00010fb4> { ___do_softirq + 0x94 }

  11 Target : <0x00010fac> { ___do_softirq + 0x8c }

     Source : <0x00010f8c> { ___do_softirq + 0x6c }

  12 Target : <0x00010f80> { ___do_softirq + 0x60 }

     Source : <0x00011098> { _tasklet_action + 0x7c }

  13 Target : <0x00011092> { _tasklet_action + 0x76 }

     Source : <0x0001106e> { _tasklet_action + 0x52 }

  14 Target : <0x0001106c> { _tasklet_action + 0x50 }

     Source : <0x0001aa92> { ___rcu_process_callbacks + 0xb6 }

  15 Target : <0x0001aa8c> { ___rcu_process_callbacks + 0xb0 }

     Source : <0x0001aa22> { ___rcu_process_callbacks + 0x46 }

Stack from 03de7edc:

        03de7ee0 000ca448 002c9dc0 ffffffef 00232fae 00290df0 0000001f 000f121e

        000f1224 002c9dc0 00290d84 002c1a64 002884ac 00290dec 00000000 002c9e70

        00290e28 002c9dc0 00290d7c 002c1a64 00000000 002c9e70 000f44bc 002c9dc0

        00290d7c 002c1a64 00000001 00000000 00000000 00000000 034fb080 00dbe440

        00214f5c 00214f5c 00000000 002bc6fc 002c9dc0 03de6000 00000000 00000000

        002c9dbc 002c9db4 03de6000 0029e464 00000000 00000000 00000000 00000000

 

Call Trace:

[<0029e3dc>] _kernel_init+0x0/0x234

[<00001666>] _kernel_thread_helper+0x6/0xc

 

BF5xx on-chip NAND FLash Controller Driver, Version 1.2 (c) 2007 Analog Devices, Inc.

bf5xx-nand bf5xx-nand.0: page_size=256, data_width=8, wr_dly=3, rd_dly=3

NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)

Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x00000000-0x00400000 : "Linux Kernel"

0x00400000-0x10000000 : "File System"

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@4

bfin-spi bfin-spi.1: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc02300, dma channel@5

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

drivers/usb/serial/usb-serial.c: USB Serial support registered for generic

usbcore: registered new interface driver usbserial_generic

drivers/usb/serial/usb-serial.c: USB Serial Driver core

drivers/usb/serial/usb-serial.c: USB Serial support registered for debug

usbcore: registered new interface driver debug

mice: PS/2 mouse device common for all mice

input: bf54x-keys as /class/input/input0

bf54x-keys: Blackfin BF54x Keypad registered IRQ 76

ad7877 spi0.2: touchscreen, irq 258

input: AD7877 Touchscreen as /class/input/input1

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

i2c /dev entries driver

i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Version 1.8, regs_base@ffc02200

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-04-26 05:58:54 (9957534)

Freeing unused kernel memory: 7276k freed

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_eth0: SMSC911x/921x identified at 0x24000000, IRQ: 175

|_eth0: SMSC911x MAC Address: 00:e0:22:fe:df:29

| |_|\____|/_/\_\       |

   eth0: link down

  dP   .ADDRCONF(NETDEV_UP): eth0: link is not ready

    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            - http://blackfin.uclinux.org/

\    YP"    `| 8P  `.          - http://docs.blackfin.uclinux.org/

/     \.___.d|    .'           - http://www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    - http://www.analog.com/blackfin

 

Have a lot of fun...

 

setting up lan...

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            - http://blackfin.uclinux.org/

\    YP"    `| 8P  `.          - http://docs.blackfin.uclinux.org/

/     \.___.d|    .'           - http://www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    - http://www.analog.com/blackfin

 

Have a lot of fun...

 

init: Booting to single user mode

 

 

BusyBox v1.9.0 (2008-02-15 21:49:26 CET) built-in shell (msh)

Enter 'help' for a list of built-in commands.

 

# eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

 

#

QuoteReplyEditDelete

 

 

2008-02-18 10:21:59     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51204    you need to update your configuration as well ... you cannot set the address/length fields of the physmap configuration option and declare the physmap board resources at the same time

 

pick one

QuoteReplyEditDelete

 

 

2008-02-18 11:35:22     Re: Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51209    Mike,

 

thank you for the quick reply.

 

Could you indicate where I change/pick/set the options you stated? As I did not actively touch anything with physmap (I actually don't even know what it is doing and standing for) I am a bit lost at this point.

 

Regards

Piggebu

QuoteReplyEditDelete

 

 

2008-02-18 11:45:41     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51211    you're talking about a flash device which means it's under the MTD options (memory technology devices) in the kernel configuration menu

QuoteReplyEditDelete

 

 

2008-02-18 12:51:26     Re: Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51212    perfect! thanks once again.

 

The error is gone. However I still have the problem that the system is booting in single user mode and has thus (?) a strange shell (no tab expanding etc) moreover the usb camera I used to connect to is not anymore recognized...

 

If you check my first post the last line states the single user mode and just above there is also some disturbed linux logo and welcome message, maybe this has all to do with the same thing?

 

Regards

Piggebu

QuoteReplyEditDelete

 

 

2008-02-18 13:40:38     Re: Error while booting: kobject_add failed for physmap-flash.0

Robin Getz (UNITED STATES)

Message: 51216    Piggebu:

 

Booting in single user mode normally means something is wrong with your /etc/rc script.

 

-Robin

QuoteReplyEditDelete

 

 

2008-02-19 10:20:07     Re: Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51276    Robin,

 

I checked my rc script as I added there some custom things. I downloaded now the original rc (from trunk/vendors/AnalogDevices/BF548-EZKIT/rc) and recompiled the kernel. But it still boots in single user mode.

 

below the last few lines of the booting sequence:

 

---------------------------------------------------------------------------------------------snip----------------------------------------------------------

Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x00000000-0x00400000 : "Linux Kernel"

0x00400000-0x10000000 : "File System"

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@4

bfin-spi bfin-spi.1: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc02300, dma channel@5

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

drivers/usb/serial/usb-serial.c: USB Serial support registered for generic

usbcore: registered new interface driver usbserial_generic

drivers/usb/serial/usb-serial.c: USB Serial Driver core

drivers/usb/serial/usb-serial.c: USB Serial support registered for debug

usbcore: registered new interface driver debug

mice: PS/2 mouse device common for all mice

input: bf54x-keys as /class/input/input0

bf54x-keys: Blackfin BF54x Keypad registered IRQ 76

ad7877 spi0.2: touchscreen, irq 258

input: AD7877 Touchscreen as /class/input/input1

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

i2c /dev entries driver

i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Version 1.8, regs_base@ffc02200

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-04-27 06:36:07 (10046167)

Freeing unused kernel memory: 7276k freed

mount: cannot read /etc/fstab: No such file or directory

cat: can't open '/etc/motdecho': No such file or directory

cat: can't open '20': No such file or directory

init: Booting to single user mode

 

 

BusyBox v1.9.0 (2008-02-16 18:01:20 CET) built-in shell (msh)

Enter 'help' for a list of built-in commands.

 

#

----------------------------------------------------------------------------------------------------end-------------------------------------

 

 

and here the rc script:

 

hostname blackfin

mount -t proc proc /proc

mount -t ramfs ramfs /var

mount -t sysfs sysfs /sys

mount -t devpts devpts /dev/pts

[ -d /proc/bus/usb ] && mount -t usbfs usbfs /proc/bus/usb

[ -d /sys/kernel/debug ] && mount -t debugfs debugfs /sys/kernel/debug

[ -d /proc/sys/fs/binfmt_misc ] && mount -t binfmt_misc binfmt_misc #/proc/sys/fs/binfmt_misc

[ -d /sys/kernel/security ] && mount -t securityfs securityfs /sys/kernel/security

grep -qs nfsd /proc/filesystems && mount -t nfsd nfsd /proc/fs/nfsd

if [ -e /bin/mdev ] ; then

    echo /bin/mdev 2>/dev/null > /proc/sys/kernel/hotplug

    /bin/mdev -s 2> /dev/null

fi

mkdir /var/tmp /var/log /var/run /var/lock

#dhcpcd &

#ifconfig eth0 10.100.4.251 up

ifconfig lo 127.0.0.1

inetd &

#cat /etc/issue

cat /etc/motd

 

Thanks for any hints!

 

Regards Piggebu

QuoteReplyEditDelete

 

 

2008-02-19 11:59:23     Re: Error while booting: kobject_add failed for physmap-flash.0

Robin Getz (UNITED STATES)

Message: 51284    Piggebu:

 

I think this can be solved with some simple reading.

 

the error message you posted :

>cat: can't open '/etc/motdecho': No such file or directory

>cat: can't open '20': No such file or directory

 

those lines are not in the script you posted. Meaning:

- you are not downloading the proper image to the board

- you did not copy the right /etc/rc file into ./romfs/etc/rc

- you did not rebuild the image properly

- you did copy/paste the error properly

 

After you boot the board that is having the problem, try "cat /etc/rc" and see if things look OK - I suspect they do not.

 

-Robin

QuoteReplyEditDelete

 

 

2008-02-19 12:04:23     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51287    most likely the file is corrupt going by the output you've shown

 

please check it on your host by editing romfs/etc/rc and looking at it in a hex editor

QuoteReplyEditDelete

 

 

2008-02-20 06:44:26     Re: Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51334    Robin,

 

please excuse the silly mistake... I thought I checked the rc in the romfs. But just as a note: I modified the rc script in the vendors directory and while building the image a line

echo 20 > /proc/sys/vm/pagecache_ratio

has been appended. the error was produced because this appending was without making a new line first.

if the last line of the rc script was the command "ls" after building the last line was "lsecho 20 > /proc/sys/vm/pagecache_ratio " instead of two lines:

"ls

echo 20 > /proc/sys/vm/pagecache_ratio "

Maybe this can be improved in the next version?

 

 

Now I can boot in normal user mode. However there are still some things missing compared to an old image version.

 

1) most important:

I can mount the HD of the 548EZ-kit but when I try to access it (ls [mountpoint]) the system hangs.

 

in bootlog.txt you find  the messages during boot and the (right) rc script in rc.txt: I think the problem lies in the line: mount: cannot read /etc/fstab: No such file or directory. But how to solve it?

 

 

2) less important :-) : where is the nice command prompt? booting the old image it gives me a nice "root:~>" as command prompt without having to modify anything... how can I get this again with the recent trunk version?

 

Thanks for the help

regards

Piggebu

 

 

 

PS: how is the philosophy here, appending files or rather post laaaarge messages when posting bootlogs etc?

 

 

bootlog.txt

rc.txt

QuoteReplyEditDelete

 

 

2008-02-20 11:12:50     Re: Error while booting: kobject_add failed for physmap-flash.0

Robin Getz (UNITED STATES)

Message: 51361    Piggebu:

 

You need to fix the error the kernel told you before you mount it.

 

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

 

-Robin

 

QuoteReplyEditDelete

 

 

2008-02-20 12:05:52     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51372    sorry, i dont know what you mean by "improved in the next version" ... if you typed a command wrong, what is there to improve in the dist ?

 

the command prompt is controlled by your busybox shell configuration ... if you disabled the fancy prompt options, then you wont get a fancy prompt

QuoteReplyEditDelete

 

 

2008-02-20 13:17:55     Re: Error while booting: kobject_add failed for physmap-flash.0

Robin Getz (UNITED STATES)

Message: 51381    Mike:

 

I think that the -a in ROMFSINST does exactly that. It appends the exact line, with no newline at the beginning.

 

If the file is:

 

"ls<EOF>"

 

and you append something, you get:

 

"lssomething", rather than "ls<newline>something"

 

-Robin

QuoteReplyEditDelete

 

 

2008-02-20 14:02:30     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51385    files should already end in new lines

QuoteReplyEditDelete

 

 

2008-02-20 14:56:55     Re: Error while booting: kobject_add failed for physmap-flash.0

Robin Getz (UNITED STATES)

Message: 51390    Mike:

 

It is a pretty common thing to do - even thought it is a mistake? I don't think we should add it to all the Makefiles, but we should be able to add it to romfs-inst.sh  - shouldn't we? (add a newline if the file ends in <char><eof>, rather than <newline><eof>)

 

?

 

-Robin

QuoteReplyEditDelete

 

 

2008-02-20 15:31:57     Re: Error while booting: kobject_add failed for physmap-flash.0

Mike Frysinger (UNITED STATES)

Message: 51394    do you know a portable way of detecting the absence of a trailing newline ?

QuoteReplyEditDelete

 

 

2008-02-22 11:20:40     Re: Error while booting: kobject_add failed for physmap-flash.0

Piggebu Piggebu (ANDORRA)

Message: 51509    Mike, Robin

 

Thanks for discussing the suggestion of the thing with the new line.

 

Robin, I tried to eliminate the error/warning appearing in the boot log. The rc file is now fine, no errors.

The warning when I mount the Hard disk still persists. As this gets out of topic in this thread I opened a new one under:

http://blackfin.uclinux.org/gf/project/uclinux-dist/forum/?action=ForumBrowse&forum_id=39&_forum_action=ForumMessageBrowse&thread_id=26035

 

please find there the details of the problem. If you (or anyone else)  could find time to provide some useful hints about that problem I would be thankful.

 

Regards

Piggebu

Attachments

Outcomes