Modify

Opened 11 years ago

Closed 9 years ago

#1871 closed defect (worksforme)

kamikaze - ipkg upgrade segfaults on asus wl500g prem

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Kamikaze 7.06
Component: base system Version:
Keywords: Cc:

Description

After installation of Kamikaze 7.06 (openwrt-brcm-2.4-squashfs.trx):

root@OpenWrt:/# ipkg update
Downloading http://downloads.openwrt.org/kamikaze/7.06/brcm-2.4/packages/Packages
dmesgUpdated list of available packages in /usr/lib/ipkg/lists/snapshots
Done.
root@OpenWrt:/# ipkg upgrade
Upgrading base-files-brcm-2.4 on root from 8-7431 to 8-7485...
Downloading http://downloads.openwrt.org/kamikaze/7.06/brcm-2.4/packages/./base-files-brcm-2.4_8-7485_mipsel.ipk
Segmentation fault

Next ipkg upgrade says:
root@OpenWrt:/# ipkg upgrade
Upgrading base-files-brcm-2.4 on root from 8-7431 to 8-7485...
Downloading http://downloads.openwrt.org/kamikaze/7.06/brcm-2.4/packages/./base-files-brcm-2.4_8-7485_mipsel.ipk
... and freezes.

dmesg said after first run of ipkg upgrade:

ASSERTION FAILED: src != NULL at mini_fo.h:394 (fist_copy_attr_times)
Unable to handle kernel paging request at virtual address 00000000, epc == 80064b08, ra == 80064b08
Oops in fault.c::do_page_fault, line 206:
$0 : 00000000 1000fc00 00000049 81ea2000 00000000 00000000 0000001f 81136220
$8 : 00000000 000013a0 000013a0 00001357 801a0000 801a0000 801a0000 ffffffff
$16: 00000000 81eb6170 811f8000 815c58a0 ffffffea fffffff0 81eb60e0 00000000
$24: 00000002 00000002 81ea2000 81ea3e88 00000000 80064b08
Hi : 00000000
Lo : 00000b60
epc : 80064b08 Tainted: P
Status: 1000fc03
Cause : 0000000c
PrId : 00029006
Process ipkg (pid: 1189, stackpage=81ea2000)
Stack: 81eb60e0 801550ec 801550e0 0000018a 8014d0d4 00000000 81e88ad0

81eb6170 811f8000 815c58a0 81eb60e0 fffffff0 10094778 80045ad0 00000000
80044744 8004467c 80044664 815c58a0 815c58a0 811f8000 10094778 1009f478
1023a850 10094778 80045d10 1031c000 81136220 1031b000 1031c000 801f54a0
8105e4a0 811f800f 00000003 00272c85 00000010 00000000 10288230 10288328
7fff7ca0 ...

Call Trace: [<801550ec>] [<801550e0>] [<8014d0d4>] [<80045ad0>] [<80044744>]

[<8004467c>] [<80044664>] [<80045d10>] [<80008a60>] [<8005b9ec>]

Code: 2407018a 0c004d45 afa20010 <a2000000> 8e020058 8e040054 8e030050 aec20058 aec40054

I'm running a stock Kamikaze 7.06 image on Asus WL-500G Premium.

Attachments (0)

Change History (8)

comment:1 follow-up: Changed 11 years ago by anonymous

NEVER USE IPKG UPGRADE.

it's known to cause problems...

comment:2 Changed 11 years ago by mbm

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

comment:3 Changed 11 years ago by petr.stetina@…

But what to use to upgrade modules instead od ipkg upgrade?

comment:4 in reply to: ↑ 1 Changed 10 years ago by brian@…

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to anonymous:

NEVER USE IPKG UPGRADE.

it's known to cause problems...

Another user asked and I am also wondering, if ipkg upgrade causes problems, how do you propose to upgrade packages on an openwrt installation?

comment:5 follow-up: Changed 10 years ago by anonymous

The only way to upgrade is to do a full reflash.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 10 years ago by KanjiMonster

Replying to anonymous:

The only way to upgrade is to do a full reflash.

Thats not correct, I can upgrade packages perfectly fine on an pivoted root (using a recent trunk build).
Although this only applies to "normal" packages, 'base-files' is a special case (perhaps there should be a flag and handling for "non-upgradeable" packages and kernel modules).

Upgrading also works on the internal flash, but is only viable for small packages.

comment:7 in reply to: ↑ 6 Changed 10 years ago by brian@…

Replying to KanjiMonster:

Thats not correct, I can upgrade packages perfectly fine on an pivoted root (using a recent trunk build).

Heh. Your use-case is exactly like mine. I have a Kamikaze based system with a 1G USB flash stick as my pivoted root.

Upgrading also works on the internal flash, but is only viable for small packages.

Yeah. I am currently contemplating how I will do my upgrade given that I have a lot more packages on my USB flash than will fit into a .trx image to be flashed on to the internal flash.

I guess I will have to make the/a pretty standard minimal image, reboot my router without the flash stick (so that the rootfs is on the internal flash again), flash that with mtd, then reboot, installing the flash stick in the process and use "ipkg upgrade" to get the packages on the usb stick upgraded. Then I will have to restore all of the config, which with any hope I have captured into a tarball or something before I start all of this.

BTW: KanjiMonster, what mechanism are you using to have the boot sequence pivot your rootfs in during boot?

comment:8 Changed 9 years ago by nbd

  • Resolution set to worksforme
  • Status changed from reopened to closed

usb access is much more stable in trunk with 2.6.25 - this should have fixed this issue for good.

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.