From: Yusuke Goda <goda.yusuke@renesas.com>
To: linux-sh@vger.kernel.org
Subject: USB boot problems submission
Date: Mon, 25 Jan 2010 05:46:01 +0000 [thread overview]
Message-ID: <4B5D3019.9080900@renesas.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
Hi Paul san
When I set rootfs in USB memory,
the latest kernel seems to have a problem.
Please refer to log for the error.
(AP3300(ap325rxa) is the same phenomenon, too.)
- NFS boots both boards normally.
- Both boards were confirmed a USB boot in the old kernel.
(2.6.27 and 2.6.31-rc7)
- rootfs is made by Debian and uses the following things.
https://oss.renesas.com/modules/download/index.php?cid=61
"debian-rootfs-20091208.tar.bz2"
Do you recognize this problem?
Thanks,
Goda
[-- Attachment #2: ecovec-usbboot.log --]
[-- Type: text/plain, Size: 8541 bytes --]
## Starting application at 0x89000000 ...
Linux version 2.6.33-rc4 (root@gohda) (gcc version 4.3.4 (Debian 4.3.4-1) ) #10 PREEMPT Mon Jan 25 05:15:59 UTC 2010
Boot params:
... MOUNT_ROOT_RDONLY - 00000000
... RAMDISK_FLAGS - 00000000
... ORIG_ROOT_DEV - 00000000
... LOADER_TYPE - 00000000
... INITRD_START - 00000000
... INITRD_SIZE - 00000000
Booting machvec: R0P7724 (EcoVec)
Node 0: start_pfn = 0x8000, low = 0xf800
Zone PFN ranges:
Normal 0x00008000 -> 0x0000f800
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00008000 -> 0x0000f800
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 30480
Kernel command line: console=tty0, console=ttySC0,115200 root=/dev/sda2 rootdelay=10 mem=120M memchunk.vpu=4m
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
PVR=10300b00 CVR=7144040d PRR=00002200
I-cache : n_ways=4 n_sets=256 way_incr=8192
I-cache : entry_mask=0x00001fe0 alias_mask=0x00001000 n_aliases=2
D-cache : n_ways=4 n_sets=256 way_incr=8192
D-cache : entry_mask=0x00001fe0 alias_mask=0x00001000 n_aliases=2
S-cache : n_ways=4 n_sets=2048 way_incr=65536
S-cache : entry_mask=0x0000ffe0 alias_mask=0x0000f000 n_aliases=16
Memory: 118400k/122880k available (2241k kernel code, 776k data, 108k init)
virtual kernel memory layout:
fixmap : 0xdffd6000 - 0xdffff000 ( 164 kB)
vmalloc : 0xc0000000 - 0xdffd4000 ( 511 MB)
lowmem : 0x88000000 - 0x8f800000 ( 120 MB) (cached)
: 0xa8000000 - 0xc8000000 ( 512 MB) (uncached)
.init : 0x882f4000 - 0x8830f000 ( 108 kB)
.data : 0x88231590 - 0x882f36c0 ( 776 kB)
.text : 0x88001000 - 0x88231590 (2241 kB)
Hierarchical RCU implementation.
NR_IRQS:256 nr_irqs:256
Console: colour dummy device 80x25
console [tty0] enabled
sh_tmu: TMU0 used for clock events
sh_tmu: TMU0 used for periodic clock events
sh_tmu: TMU1 used as clock source
Calibrating delay loop (skipped)... 499.99 BogoMIPS PRESET (lpj=999999)
Mount-cache hash table entries: 512
CPU: SH7724
NET: Registered protocol family 16
vpu: forcing memory chunk size to 0x00400000
sh pinmux: sh7724_pfc handling gpio 0 -> 486
Performance Events: SH-4A support registered
HW Breakpoints: SH-4A UBC support registered
USB1 function is selected
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource TMU1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 231
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 100x30
graphics fb0: registered sh_mobile_lcdc_fb/mainlcd as 800x480 16bpp.
SuperH SCI(F) driver initialized
sh-sci.0: ttySC0 at MMIO 0xffe00000 (irq = 80) is a scif
console [ttySC0] enabled
sh-sci.1: ttySC1 at MMIO 0xffe10000 (irq = 81) is a scif
sh-sci.2: ttySC2 at MMIO 0xffe20000 (irq = 82) is a scif
sh-sci.3: ttySC3 at MMIO 0xa4e30000 (irq = 56) is a scifa
sh-sci.4: ttySC4 at MMIO 0xa4e40000 (irq = 88) is a scifa
sh-sci.5: ttySC5 at MMIO 0xa4e50000 (irq = 109) is a scifa
brd: module loaded
physmap platform flash device: 04000000 at 00000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
RedBoot partition parsing not available
Using physmap partition information
Creating 2 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000500000 : "boot loader"
0x000000500000-0x000004000000 : "free-area"
sh_mii: probed
Base address at 0xa4600000, 00:00:87:6B:BC:B0, IRQ 91.
r8a66597_hcd: driver r8a66597_hcd, 2009-05-26
r8a66597_hcd r8a66597_hcd.0: USB Host Controller
r8a66597_hcd r8a66597_hcd.0: new USB bus registered, assigned bus number 1
r8a66597_hcd r8a66597_hcd.0: irq 65, io base 0xa4d80000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: sh_keysc as /class/input/input0
i2c /dev entries driver
Linux video capture interface: v2.00
camera 0-0: Probing 0-0
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 0
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 0
camera: probe of 0-0 failed with error -12
camera 1-0: Probing 1-0
sh_mobile_ceu sh_mobile_ceu.1: SuperH Mobile CEU driver attached to camera 0
sh_mobile_ceu sh_mobile_ceu.1: SuperH Mobile CEU driver detached from camera 0
camera: probe of 1-0 failed with error -12
camera 1-1: Probing 1-1
sh_mobile_ceu sh_mobile_ceu.1: SuperH Mobile CEU driver attached to camera 1
sh_mobile_ceu sh_mobile_ceu.1: SuperH Mobile CEU driver detached from camera 1
camera: probe of 1-1 failed with error -12
sh_tmu: TMU0 kept as earlytimer
sh_tmu: TMU1 kept as earlytimer
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
heartbeat: version 0.1.2 loaded
TCP cubic registered
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Waiting 10sec before mounting root device...
usb 1-1: new high speed USB device using r8a66597_hcd and address 2
scsi0 : usb-storage 1-1:1.0
scsi 0:0:0:0: Direct-Access I-O DATA USB Flash Disk 3A PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 4014080 512-byte logical blocks: (2.05 GB/1.91 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
EXT3-fs (sda2): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:2.
Freeing unused kernel memory: 108k freed
Kernel panic - not syncing: Attempted to kill init!
Stack: (0x8f01de3c to 0x8f01e000)
de20: 8822dac8
de40: 881190d4 88266d44 8f01de68 88019256 8f0f4580 8f01fd60 8f01def0 8f01acc0
de60: 8f01acc0 882d22f0 8f01acb8 00000000 8f01de4c 00000004 00000001 00000000
de80: 8f01de80 8f01de80 88019840 000000fc 8f0f4580 8f01fd60 8f01def0 00000003
dea0: 00000004 8f01fd60 88022b8e 00000003 8f0f45c0 8f01dfa4 8f01df70 880050aa
dec0: 7b80fd18 8f01dfa4 29583004 00000008 88006464 880070ec 29583004 00000002
dee0: 8f01aef0 8f01acc0 8f104d40 8f104d74 00000004 00000000 00000080 00000000
df00: 00000000 00000000 00000000 00000000 8818ecd4 00000100 8818e700 8f11b4e0
df20: 88013e9a 8f01df30 8f11a8f8 00000001 000000f0 880212ca 00000000 00000000
df40: 8f01acc0 00000004 8f01af08 8f11a8f8 00000001 880213be 7b80fd18 00000001
df60: 00000004 8f0f4580 00000000 8f01acc0 00000003 00000000 88006484 00400034
df80: 8800648e 8800713c 7b80fd18 00400034 29583004 00000008 88006464 880070ec
dfa0: 8f01c000 00000078 00000000 004020c0 00008384 2956fca8 2956fca8 00000000
dfc0: 00000000 29583050 ffffff38 fffffe10 00000008 29583004 00400034 7b80fd18
dfe0: 7b80fd10 295609c0 2955863c 00008000 00000000 000000d8 0000006c ffffffff
Call trace:
[<881190d4>] 0x881190d4
[<88019256>] 0x88019256
[<88019840>] 0x88019840
[<88022b8e>] 0x88022b8e
[<880050aa>] 0x880050aa
[<88006464>] 0x88006464
[<880070ec>] 0x880070ec
[<8818ecd4>] 0x8818ecd4
[<8818e700>] 0x8818e700
[<88013e9a>] 0x88013e9a
[<880212ca>] 0x880212ca
[<880213be>] 0x880213be
[<88006484>] 0x88006484
[<8800648e>] 0x8800648e
[<8800713c>] 0x8800713c
[<88006464>] 0x88006464
[<880070ec>] 0x880070ec
next reply other threads:[~2010-01-25 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 5:46 Yusuke Goda [this message]
2010-01-25 15:20 ` USB boot problems submission Paul Mundt
2010-01-26 8:33 ` Yusuke Goda
2010-01-26 8:54 ` Paul Mundt
2010-01-26 9:24 ` Yusuke Goda
2010-01-26 9:26 ` Paul Mundt
2010-01-26 9:42 ` Yusuke Goda
2010-02-02 7:00 ` Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B5D3019.9080900@renesas.com \
--to=goda.yusuke@renesas.com \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.