maemo.org - Talk - [Announce] kernel-power stable v49 in Extras-Testing

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - [Announce] kernel-power stable v49 in Extras-Testing (https://talk.maemo.org/showthread.php?t=71879)

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by kent_autistic (Post 1166136)

previously on v42, today i updated to v49 in extras-testing. everything seems to be ok except i am unable to watch flash videos on microb...

The black screen is usually a symptom of the content actually using flash 10+ features, so not visible to flash =< 9.

Just to clarify:
- how long ago did you try to view these videos before installing kp49, i.e. could the provider have changed flash version since you last visited?
- did you install anything other than kp49 itself, what about settings package etc?

What happens when you remove flash-tweak?
If msg appears "need flash10+", try reinstalling. Any improvement?

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by demolition (Post 1166146)

i was watching lots of flash vids on different sites before updating. anyway, for some reason its working again. thanks brotha

Re: [Announce] kernel-power stable v49 in Extras-Testing

Hello,

just installed pali's latest build of KP49pre50- it runs stable here except one issue: when I try to load the bleeding edge wifi drivers I get the error-message:

Code:

Error while loading kernel modules

ifconfig: SIOCGIFFLAGS: No such device

Error while starting wlan0 interface

Drivers were not loaded

That is the only issue I had so far- the rest runs rock-stable up to 950MHz.
Thanks to all involved!

CU Michael

Re: [Announce] kernel-power stable v49 in Extras-Testing

Hi! last pre50 build has some problems. I got (at least) 2 times kernel segfault and n900 rebooted.

In syslog is nothing logged, so only mtd2 log is usefull. Here is:

Code:

[92737.347869] Unable to handle kernel paging request at virtual address 65727453

[92737.347900] pgd = c534c000

[92737.347930] [65727453] *pgd=00000000

[92737.347961] Internal error: Oops: 5 [#1] PREEMPT

[92737.347961] Modules linked in: pn_pep ext4 jbd2 vfat fat sd_mod scsi_mod iphb rfcomm sco bnep l2cap panic_info_buff omaplfb pvrsrvkm bridgedriver g_file_storage ipv6 uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp phonet cmt_speech joydev mailbox_mach mac80211 smc91x mii omap_ssi crc7 hci_h4p mailbox nokia_av cfg80211 tsc2005 bluetooth fmtx_si4713 ad5820 adp1653 smia_sensor videodev v4l1_compat compat_ioctl32 smiaregs tsl2563 v4l2_int_device lis302dl leds_twl4030_vibra ext3 jbd mbcache twl4030_wdt omap_wdt rtc_twl4030 rtc_core omap_hsmmc mmc_block mmc_core leds_lp5523 led_class [last unloaded: wl12xx]

[92737.348297] CPU: 0    Not tainted  (2.6.28.10-power49+pre50 #1)

[92737.348327] PC is at kmem_cache_alloc+0x30/0x84

[92737.348358] LR is at sk_prot_alloc+0x2c/0x120

[92737.348388] pc : [<c00b7f10>]    lr : [<c0218ca4>]    psr: 200000d3

[92737.348388] sp : c9d19e28  ip : c9d19e50  fp : c9d19e4c

[92737.348419] r10: 00000017  r9 : c9353480  r8 : c03d520c

[92737.348419] r7 : 000000d0  r6 : 00000190  r5 : 65727453  r4 : a0000053

[92737.348449] r3 : 00000000  r2 : 00000001  r1 : 000000d0  r0 : cf075b40

[92737.348480] Flags: nzCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment user

[92737.348480] Control: 10c5387d  Table: 8534c018  DAC: 00000015

[92737.348510] Process fmtxd (pid: 5393, stack limit = 0xc9d182e8)

[92737.348510] Stack: (0xc9d19e28 to 0xc9d1a000)

[92737.348541] 9e20:                   40000053 cc0781c0 000002db c039641c 000080d0 cf075b40 

[92737.348571] 9e40: c9d19e6c c9d19e50 c0218ca4 c00b7eec 000002db c039641c 00000001 00000000 

[92737.348632] 9e60: c9d19e8c c9d19e70 c021a49c c0218c84 000002db bec5337a c03d307c 00000000 

[92737.348663] 9e80: c9d19eb4 c9d19e90 c028596c c021a484 00000802 bec5337a 0000006e cc0a8380 

[92737.348693] 9ea0: c002dac4 c9353480 c9d19efc c9d19eb8 c0287118 c0285920 c9d19ee4 c9d19ec8 

[92737.348754] 9ec0: c9d19f00 00000000 fffffff4 0000006e c9d19f00 c9353480 bec5337a 0000006e 

[92737.348785] 9ee0: c9d19f00 c002dac4 c9d18000 00000000 c9d19fa4 c9d19f00 c0217838 c0287090 

[92737.348846] 9f00: 762f0001 722f7261 6e2f6e75 2f646373 6b636f73 00007465 00000000 00000000 

[92737.348876] 9f20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 

[92737.348907] 9f40: 00000000 000a0000 00000000 10280000 c7940000 0000fff1 391c0000 7000bec5 

[92737.348968] 9f60: 00444052 00000000 b7d00000 cc00401a c9d19fa4 c9d19f80 c00ca6c8 c00be920 

[92737.348999] 9f80: 00000000 00000000 40527000 00000002 ffffffff 0000011b 00000000 c9d19fa8 

[92737.349029] 9fa0: c002d940 c02177d0 40527000 00000002 00000006 bec5337a 0000006e 00000000 

[92737.349090] 9fc0: 40527000 00000002 ffffffff 0000011b bec534ce bec53460 00000000 bec533fc 

[92737.349121] 9fe0: 00000006 bec53378 404fa1bc 404c83fc 40000050 00000006 00000000 00000000 

[92737.349151] Backtrace: 

[92737.349182] [<c00b7ee0>] (kmem_cache_alloc+0x0/0x84) from [<c0218ca4>] (sk_prot_alloc+0x2c/0x120)

[92737.349212]  r7:cf075b40 r6:000080d0 r5:c039641c r4:000002db

[92737.349243] [<c0218c78>] (sk_prot_alloc+0x0/0x120) from [<c021a49c>] (sk_alloc+0x24/0x50)

[92737.349304]  r7:00000000 r6:00000001 r5:c039641c r4:000002db

[92737.349304] [<c021a478>] (sk_alloc+0x0/0x50) from [<c028596c>] (unix_create1+0x58/0x148)

[92737.349365]  r7:00000000 r6:c03d307c r5:bec5337a r4:000002db

[92737.349395] [<c0285914>] (unix_create1+0x0/0x148) from [<c0287118>] (unix_stream_connect+0x94/0x4c4)

[92737.349426]  r9:c9353480 r8:c002dac4 r7:cc0a8380 r6:0000006e r5:bec5337a

[92737.349456] r4:00000802

[92737.349487] [<c0287084>] (unix_stream_connect+0x0/0x4c4) from [<c0217838>] (sys_connect+0x74/0x98)

[92737.349517] [<c02177c4>] (sys_connect+0x0/0x98) from [<c002d940>] (ret_fast_syscall+0x0/0x2c)

[92737.349548]  r7:0000011b r6:ffffffff r5:00000002 r4:40527000

[9273K*

Who has same problem?

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by magic_doc (Post 1166330)

Hello,

just installed pali's latest build of KP49pre50- it runs stable here except one issue: when I try to load the bleeding edge wifi drivers I get the error-message:

Code:

Error while loading kernel modules

ifconfig: SIOCGIFFLAGS: No such device

Error while starting wlan0 interface

Drivers were not loaded

That is the only issue I had so far- the rest runs rock-stable up to 950MHz.
Thanks to all involved!

CU Michael

same here...

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by magic_doc (Post 1166330)

Hello,

just installed pali's latest build of KP49pre50- it runs stable here except one issue: when I try to load the bleeding edge wifi drivers I get the error-message:

Code:

Error while loading kernel modules

ifconfig: SIOCGIFFLAGS: No such device

Error while starting wlan0 interface

Drivers were not loaded

That is the only issue I had so far- the rest runs rock-stable up to 950MHz.
Thanks to all involved!

CU Michael

This is because that wifi driver is compiled against old kernel-power. For proper working each module must be compiled against actual kernel version. But there was nothing changed in wifi stack, so packet injection wifi driver worked. But now in kernel power are some changes (disabled mesh, ...) and binary wl1251 packet injection driver is incompatible with last kernel-power...

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by pali (Post 1166337)

Hi! last pre50 build has some problems. I got (at least) 2 times kernel segfault and n900 rebooted.

In syslog is nothing logged, so only mtd2 log is usefull. Here is:

Code:

[92737.348297] CPU: 0    Not tainted  (2.6.28.10-power49+pre50 #1)

[92737.348327] PC is at kmem_cache_alloc+0x30/0x84

[92737.348358] LR is at sk_prot_alloc+0x2c/0x120

[92737.348510] Process fmtxd (pid: 5393, stack limit = 0xc9d182e8)

Who has same problem?

I've not had any reboots, so it looks like the wifi issue is fixed.

From the mtd2 log I'm guessing you're using the fm transmitter? Death in kmem_cache_alloc is never good, very hard to debug, since it may not have anything to do with user-land operations going on at the time. :(

I'll enable fm transmitter and see if I can cause it to duplicate, to see if it's related at all. Is there anything else you were doing at the time that caused it to reboot that you can think of?

Re: [Announce] kernel-power stable v49 in Extras-Testing

N900 rebooted when screen was locked and I not used it for more minutes. I only heard vibra engine and then Nokia hands video.

Last syslog output is:

Code:

Feb 17 17:04:47 Pali-Nokia-N900 fmtxd[5387]: GLIB WARNING ** default - No marshaller for signature of signal 'Condition'

Feb 17 17:04:47 Pali-Nokia-N900 fmtxd[5387]: GLIB WARNING ** default - fmtxd Could not set FM tx power level: Operation not permitted

Feb 17 17:05:48 Pali-Nokia-N900 fmtxd[5389]: GLIB WARNING ** default - No marshaller for signature of signal 'Condition'

Feb 17 17:05:48 Pali-Nokia-N900 fmtxd[5389]: GLIB WARNING ** default - fmtxd Could not set FM tx power level: Operation not permitted

Feb 17 17:06:49 Pali-Nokia-N900 fmtxd[5391]: GLIB WARNING ** default - No marshaller for signature of signal 'Condition'

Feb 17 17:06:49 Pali-Nokia-N900 fmtxd[5391]: GLIB WARNING ** default - fmtxd Could not set FM tx power level: Operation not permitted

and I not used FM transmitter.

Re: [Announce] kernel-power stable v49 in Extras-Testing

I created patch which do not report -EPERM when some app (e.g. fmtxd) try to change power level when fm transmitter is locked:
https://garage.maemo.org/plugins/ggi...c02b15f3f813ed

At least it could disable stupid fmtxd syslog messages...

Re: [Announce] kernel-power stable v49 in Extras-Testing

Quote:

Originally Posted by pali (Post 1166353)

N900 rebooted when screen was locked and I not used it for more minutes. I only heard vibra engine and then Nokia hands video.

and I not used FM transmitter.

Well, looks like I'm getting the same errors in syslog, and was under K49 as well. I had gotten random reboots under K49, but that was wifi related. Once I removed the wifi AP for work (which is the only place it happened) it stopped doing it. But in those the opps clearly pointed at the wifi driver. This one is pointing at the kmem_cache_alloc call.

One thing I find odd though, why is fmtxd running on your system at all? On my N900, the only time that runs is when FM has been enabled and it's actively transmitting audio. By default it runs at start up but goes away on it's own after a short delay. So the fact that it was even running implies to me that something was trying to activate it?