Modify

Opened 8 years ago

Closed 8 years ago

#7213 closed defect (fixed)

Slow Boot After Enabling WAN on IXP4XX with Backfire (but not trunk)

Reported by: ledwards@… Owned by: developers
Priority: normal Milestone: Backfire 10.03.1
Component: base system Version: Backfire 10.03
Keywords: Slow Boot IXP4XX Backfire WAN Cc:

Description

I built Backfire 10.03 from SVN for my MI424WR (IXP4XX). The first boot takes about 20 - 25 seconds (as expected). By default, there is no WAN interface, only LAN (eth0). After adding the WAN interface (eth1), subsequent start-ups take an additional 2 minutes... during this time clients often time-out and must be manually connected after the system finally comes up.

Reviewing the system log after a slow boot shows that the system waits for 2 minutes while it is trying to retrieve the eth1 firmware (see attached syslog @ 16:58:03 - 17:00:03). There is also an associated error: "ifconfig: SIOCSIFFLAGS: No such file or directory".

Curiously, running a trunk build with the exact same configuration does not produce the same problem... it boots up normally in about 25 seconds.

I have experienced this problem with the tagged Backfire release and with the latest Backfire. The attached log files are from Backfire 10.03, r21061.

Please see attached files.

Attachments (4)

dmesg (6.7 KB) - added by ledwards@… 8 years ago.
dmesg
syslog (29.7 KB) - added by ledwards@… 8 years ago.
system log
packages (5.6 KB) - added by ledwards@… 8 years ago.
installed packages (opkg list-installed)
build.config (17.1 KB) - added by ledwards@… 8 years ago.
configuration used for build (filtered out commented lines, sorted)

Download all attachments as: .zip

Change History (11)

Changed 8 years ago by ledwards@…

dmesg

Changed 8 years ago by ledwards@…

system log

Changed 8 years ago by ledwards@…

installed packages (opkg list-installed)

Changed 8 years ago by ledwards@…

configuration used for build (filtered out commented lines, sorted)

comment:1 Changed 8 years ago by thess@…

I noticed this some time ago and had traced it down to having QOS as part of the config. I forgot about this problem as I had removed QOS from my system configs as I did not want to use it anyway.

This may or may not be the same issue, but I hope this helps diagnose/fix the problem.

/ted

comment:2 Changed 8 years ago by ledwards@…

I tried removing QoS (via opkg remove qos-scripts), but it had no effect on my problem.

However, I didn't get the multiple "RTNETLINK answers: No such file or directory" log message without QoS... but that's another issue I think.

comment:3 Changed 8 years ago by ledwards@…

I think this issue may be related to UDHCPC. The following line from my system log is exactly after the 2 minute wait:

Apr 20 17:00:02 OpenWrt user.info sysinit: udhcpc (v1.15.3) started

From this, it looks like the wait may be occurring while UDHCPC is starting.

Also, I am not experiencing this problem with the latest trunk. In comparing Backfire with trunk, it looks like trunk is using UDHCPC v1.16.1, whereas Backfire uses v1.15.3.

The trunk build works fine. It starts up quickly, doesn't request the NPE-B firmware 3 times and doesn't display the "ifconfig: SIOCSIFFLAGS" error.

comment:4 follow-up: Changed 8 years ago by jow

The commits r20679 - r20684 in trunk could have solved this issue

comment:5 in reply to: ↑ 4 Changed 8 years ago by anonymous

Replying to jow:

The commits r20679 - r20684 in trunk could have solved this issue

Are these changes going to be backported to Backfire? Trunk works fine, Backfire does not.

comment:6 Changed 8 years ago by ledwards@…

Backfire r21112 - r21113 resolved this issue. Thanks jow.

comment:7 Changed 8 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.