[gentoo-user] libv8 segfault

[gentoo-user] libv8 segfault

[Nilesh Govindrajan]

I tried compiling all versions of chromium (-O3, but it always worked
previously) & v8 (tried -O3 & -O2 too)
but it always segfaults when I try to open the settings page.

CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp
00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]

Quite interestingly, the binary version of chrome works without hitches,
which I don't want to run because I'm a little paranoid about it ;-)
And that also means that there is no hardware fault.

dev-lang/v8-3.15.11.5
www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
beta, but chromium 25 doesn't work either).

Flags:
CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"

Just replace that O3 with O2 for v8.

Anybody knows what's going on here?

-- 
Nilesh Govindarajan
http://nileshgr.com

[gentoo-user] Re: libv8 segfault

[Nilesh Govindrajan]

On Wednesday 23 January 2013 09:22:21 PM IST, Nilesh Govindrajan wrote:
> I tried compiling all versions of chromium (-O3, but it always worked
> previously) & v8 (tried -O3 & -O2 too)
> but it always segfaults when I try to open the settings page.
>
> CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp
> 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
>
> Quite interestingly, the binary version of chrome works without hitches,
> which I don't want to run because I'm a little paranoid about it ;-)
> And that also means that there is no hardware fault.
>
> dev-lang/v8-3.15.11.5
> www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
> beta, but chromium 25 doesn't work either).
>
> Flags:
> CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe"
> CXXFLAGS="${CFLAGS}"
> LDFLAGS="-Wl,-O1 -Wl,--as-needed"
>
> Just replace that O3 with O2 for v8.
>
> Anybody knows what's going on here?
>

Looks like I proved myself wrong. The binary version crashed on 
extensions page with a segfault -_-

--
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] libv8 segfault

[Michael Mol]

On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan <me@nileshgr.com> wrote:
> I tried compiling all versions of chromium (-O3, but it always worked
> previously) & v8 (tried -O3 & -O2 too)
> but it always segfaults when I try to open the settings page.
>
> CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp
> 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
>
> Quite interestingly, the binary version of chrome works without hitches,
> which I don't want to run because I'm a little paranoid about it ;-)
> And that also means that there is no hardware fault.
>
> dev-lang/v8-3.15.11.5
> www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
> beta, but chromium 25 doesn't work either).
>
> Flags:
> CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe"
> CXXFLAGS="${CFLAGS}"
> LDFLAGS="-Wl,-O1 -Wl,--as-needed"
>
> Just replace that O3 with O2 for v8.
>
> Anybody knows what's going on here?

What USE flags are enabled for chromium? You haven't specified that
you're using the custom-cflags USE flag, so whatever's in your global
CFLAGS setting is largely irrelevant.

Also, you don't need to specify --as-needed; that's default, now. I
don't know what those other flags are doing.

Start with revdep-rebuild, see if that fixes it. If not, you probably
ought to re-emerge chromium and its direct dependencies. Given your
recent experience with overclocking and the rather correct warnings
about silent data corruption, you may need to re-emerge a lot more
than that.

--
:wq

Re: [gentoo-user] libv8 segfault

[Nilesh Govindrajan]

On Wednesday 23 January 2013 09:29:22 PM IST, Michael Mol wrote:
> On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan <me@nileshgr.com> wrote:
>> I tried compiling all versions of chromium (-O3, but it always worked
>> previously) & v8 (tried -O3 & -O2 too)
>> but it always segfaults when I try to open the settings page.
>>
>> CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp
>> 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
>>
>> Quite interestingly, the binary version of chrome works without hitches,
>> which I don't want to run because I'm a little paranoid about it ;-)
>> And that also means that there is no hardware fault.
>>
>> dev-lang/v8-3.15.11.5
>> www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
>> beta, but chromium 25 doesn't work either).
>>
>> Flags:
>> CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe"
>> CXXFLAGS="${CFLAGS}"
>> LDFLAGS="-Wl,-O1 -Wl,--as-needed"
>>
>> Just replace that O3 with O2 for v8.
>>
>> Anybody knows what's going on here?
>
> What USE flags are enabled for chromium? You haven't specified that
> you're using the custom-cflags USE flag, so whatever's in your global
> CFLAGS setting is largely irrelevant.
>
> Also, you don't need to specify --as-needed; that's default, now. I
> don't know what those other flags are doing.
>
> Start with revdep-rebuild, see if that fixes it. If not, you probably
> ought to re-emerge chromium and its direct dependencies. Given your
> recent experience with overclocking and the rather correct warnings
> about silent data corruption, you may need to re-emerge a lot more
> than that.
>
> --
> :wq
>

I didn't merge anything while I was playing with overclocking. 
custom-cflags is enabled.
I found the LDFLAGS on Gentoo Wiki as safe LDFLAGS for optimal 
performance.

--
Nilesh Govindarajan
http://nileshgr.com

Re: [gentoo-user] libv8 segfault

[Michael Mol]

On Wed, Jan 23, 2013 at 11:07 AM, Nilesh Govindrajan <me@nileshgr.com> wrote:
> On Wednesday 23 January 2013 09:29:22 PM IST, Michael Mol wrote:
>> On Wed, Jan 23, 2013 at 10:52 AM, Nilesh Govindrajan <me@nileshgr.com> wrote:
>>> I tried compiling all versions of chromium (-O3, but it always worked
>>> previously) & v8 (tried -O3 & -O2 too)
>>> but it always segfaults when I try to open the settings page.
>>>
>>> CrRendererMain[6059]: segfault at 500000000 ip 00007f0d0834970c sp
>>> 00007fff71d91a60 error 4 in libv8.so.3.15.11[7f0d08181000+45d000]
>>>
>>> Quite interestingly, the binary version of chrome works without hitches,
>>> which I don't want to run because I'm a little paranoid about it ;-)
>>> And that also means that there is no hardware fault.
>>>
>>> dev-lang/v8-3.15.11.5
>>> www-client/chromium-24.0.1312.56 (I'm at present using the google chrome
>>> beta, but chromium 25 doesn't work either).
>>>
>>> Flags:
>>> CFLAGS="-O3 -march=core2 -mtune=core2 -msse -msse2 -mssse3 -mmmx -pipe"
>>> CXXFLAGS="${CFLAGS}"
>>> LDFLAGS="-Wl,-O1 -Wl,--as-needed"
>>>
>>> Just replace that O3 with O2 for v8.
>>>
>>> Anybody knows what's going on here?
>>
>> What USE flags are enabled for chromium? You haven't specified that
>> you're using the custom-cflags USE flag, so whatever's in your global
>> CFLAGS setting is largely irrelevant.
>>
>> Also, you don't need to specify --as-needed; that's default, now. I
>> don't know what those other flags are doing.
>>
>> Start with revdep-rebuild, see if that fixes it. If not, you probably
>> ought to re-emerge chromium and its direct dependencies. Given your
>> recent experience with overclocking and the rather correct warnings
>> about silent data corruption, you may need to re-emerge a lot more
>> than that.
>>
>> --
>> :wq
>>
>
> I didn't merge anything while I was playing with overclocking.
> custom-cflags is enabled.
> I found the LDFLAGS on Gentoo Wiki as safe LDFLAGS for optimal
> performance.

Well, then that wiki page is out of date. :)

--
:wq

Re: [gentoo-user] libv8 segfault

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

>
> I didn't merge anything while I was playing with overclocking.
> custom-cflags is enabled.
>

Disable custom-cflags and try again. You shouldn't expect things to work
when that's on. You may get lucky at times, but youre not getting lucky now.

[-- Attachment #2: Type: text/html, Size: 546 bytes --]

[gentoo-user] /proc/net/wirelesslessness

[☈king]

[-- Attachment #1: Type: text/plain, Size: 3645 bytes --]

I'm trying to build a kernel with this Atheros AR9287 wifi card. I had it working last week and rebuilt the kernel without saving my config, now I'm kind of stuck.

The most immediate problem I see is that I have /proc/net/wireless, even though when I boot with SystemRescueCD it comes up fine.

Thanks in advance!  (Here's the info I have, feel free to query for more):


- iwconfig wlan0 # On the bad boot

wlan0  No wireless extensions

- dmesg | grep -i ath # Same both boots (except for timestamps)

[    9.852491] ath: phy0: ASPM enabled: 0x42
[    9.852495] ath: EEPROM regdomain: 0x65
[    9.852496] ath: EEPROM indicates we should expect a direct regpair map
[    9.852498] ath: Country alpha2 being used: 00
[    9.852499] ath: Regpair used: 0x65
[    9.853587] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[    9.853716] Registered led device: ath9k-phy0
[    9.853720] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xffffc90010720000, irq=17

- lspci -v | perl -ne 'print if /^03/../^$/' # Same on both boots

03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e034
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at c0500000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
	Capabilities: [170] Power Budgeting <?>
	Kernel driver in use: ath9k
	Kernel modules: ath9k

- lsmod # on the SystemRescueCD

arc4                   12390  2
ath9k                 102072  0
mac80211              350410  1 ath9k
ath9k_common           12681  1 ath9k
coretemp               12440  0
ath9k_hw              335435  2 ath9k,ath9k_common
ath                    21059  3 ath9k,ath9k_common,ath9k_hw
crc32c_intel           12440  0
ghash_clmulni_intel    12526  0
cfg80211              133830  3 ath9k,mac80211,ath
acer_wmi               28774  0
tpm_tis                16533  0
microcode              20802  0
tpm                    17694  1 tpm_tis
tpm_bios               12440  1 tpm
i2c_i801               16533  0
sparse_keymap          12655  1 acer_wmi
joydev                 16535  0
rfkill                 17293  2 cfg80211,acer_wmi
iTCO_wdt               16533  0
iTCO_vendor_support    12639  1 iTCO_wdt
raid10                 32929  0
raid456                53467  0
async_raid6_recov      12457  1 raid456
async_pq               12534  2 raid456,async_raid6_recov
raid6_pq               82586  2 async_raid6_recov,async_pq
async_xor              12452  3 raid456,async_raid6_recov,async_pq
xor                    12425  1 async_xor
async_memcpy           12388  2 raid456,async_raid6_recov
async_tx               12624  5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
raid1                  28846  0
raid0                  16515  0
multipath              12390  0
linear                 12390  0
radeon                723200  0
ttm                    54081  1 radeon
i915                  349881  2
drm_kms_helper         26341  2 radeon,i915
usb_storage            46993  1
drm                   183602  5 radeon,ttm,i915,drm_kms_helper
atl1c                  30162  0
i2c_algo_bit           12477  2 radeon,i915
i2c_core               22125  6 i2c_i801,radeon,i915,drm_kms_helper,drm,i2c_algo_bit
video                  16668  2 acer_wmi,i915
wmi                    16837  1 acer_wmi




[-- Attachment #2: Type: text/html, Size: 3918 bytes --]

Re: [gentoo-user] /proc/net/wirelesslessness

[Paul Hartman]

On Wed, Jan 23, 2013 at 11:25 AM, ☈king <rkingmob@sharpsaw.org> wrote:
> I'm trying to build a kernel with this Atheros AR9287 wifi card. I had it
> working last week and rebuilt the kernel without saving my config, now I'm
> kind of stuck. The most immediate problem I see is that I have
> /proc/net/wireless, even though when I boot with SystemRescueCD it comes up
> fine. Thanks in advance! (Here's the info I have, feel free to query for
> more): - iwconfig wlan0 # On the bad boot wlan0 No wireless extensions

Do you have CONFIG_WIRELESS_EXT=y ?

If you can boot your old (working) kernel you may have /proc/config.gz
where you can extract the kernel config (gzip -dc /proc/config.gz)

similarly you can do the same from your boot CD environment and use it
as a starting point for customizing.

Re: [gentoo-user] /proc/net/wirelesslessness

[☈king]

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

On 1/23/13 11:25 AM, ☈king wrote:
> - iwconfig wlan0 # On the bad boot
>
Turns out that this was my main problem: iwconfig and iwlist are 
deprecated in favor of iw.

I just updated my wifi script to use iw instead, and everything is 
working well.

Thanks!
-☈

[-- Attachment #2: Type: text/html, Size: 777 bytes --]

Re: [gentoo-user] /proc/net/wirelesslessness

[rking (Clumsily Typing via Phone)]

[-- Attachment #1: Type: text/plain, Size: 226 bytes --]

> Do you have CONFIG_WIRELESS_EXT=y ? 

No, I sure don't. Looking at this list of conditions that are required to enable that setting is quite impressive/daunting. I'm not sure which I should enable. I'll work on it.

-RK




[-- Attachment #2: Type: text/html, Size: 503 bytes --]