from:"asronche...@libero.it"

Bug#684666: #684666 and #683807

2012-10-11 Thread asronche...@libero.it

[i re-send it here, since the other related bug is marked as archived ]

Hi,
i did some test with other distros (slackware/fedora) and the corruption
problem seems to persist.
Yesterday i was coming back to debian , dumping a dd backup image from an
external WD hard disk, using a fedora usb-live, this way:

dc3dd if=./debian-backup-image of=/dev/sda1 hash=sha256

the partition image is ~2gB and before the end of the copy the system crashed.
(sda1 is on the new SSD disk i bought ~ on May)

so i rebooted fedora and i launched the command again , using a sequence of
Ctrl-Z, 'sync', and  'fg' , each 500mB.
the copy was successful this time.
So i think the problem could be the new ram (8gB) i bought together with the
SSD disk.

So i replaced the hard disk and the ram with the old ones. (normal hd + 4gB
ram. It's the original set of this notebook ).

i rebooted fedora live-usb and i  repeated the operation using as destination
the sda1 partition of the original disk. It went ok with no problem, it copied
2gB in a time, without crashing.

Now i'm trying debian wheezy on this non-SSD hard disk, with bumblebee enabled
for a week (hoping it doesnt crash this time). After that , i'll dump the
debian stable backup on sda1 of this same disk, to see how it is .

If the tests will be successful in the next few days, it could mean that the
problem was caused by some caching problem in the SSD , right?

I still dont understand why the combination of those SSD + 8gB ram caused
problems.

I've just checked my syslog and i see that with this setup (wheezy + non-SSD +
the old 4gB RAM) the AMI BIOS memory corruption message doesnt appear anymore.

i'll upgrade the bug in the next few days with the outcomes of these tests.

ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/16515838.303411349963955192.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-16 Thread asronche...@libero.it

Hi, 
`uptime` is:
 14:56:06 up 5 days, 12:39, 

the combination used for the test was:
non-SSD + 4gB 
(the same stuff that was mounted in the notebook when i bought it almost 2 yrs 
ago)

it works *perfectly* ! 
I fell like i'm in a time machine :) it works well, as it worked until ~May 
2012.

No programs crash, no kernel panic etc..

kernel is 3.2.0-3-amd64  on debian wheezy.

the ramdisk i mounted is only 1gB. 

During these 5 days I never opened the pdf file i was reading this summer (a 
400mB pdf file , 10k pages, i used to copy it in the ramdisk before reading it)

the file is an italian linux guide:

http://a2.pluto.it/a2/a2.pdf

could such a big pdf be the one of the causes of kernel crashes?

anyway, i'll try another combination now:

non-SSD + 8gB

(the 8gB RAM has been tested successfully with memtest86+)

if also this new combination works, then the problem must be in the SSD or in 
some driver handling that SSD.

ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/24656168.2156201350392827358.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-16 Thread asronche...@libero.it

Hi,

this time the test was bad :(

it lasted only 3 hours , then it crashed.

this time the setup was: non-SSD + 8gB.

the crash happened while i was copying a file to another pc, via netcat. The 
file was 3.4gB.

At first the file was transmitted until the end, but when i checked the md5sum 
i've found out it arrived corrupted.

So i re-sended it and before the end of the transmission i had a kernel panic 
(the one with the blinking led).

So i rebooted and tried again to send the file and it worked well, then i 
checked the md5sum and there was no corruption.

so i tried again to retransmit it and i still had no corruption.

All this (the last 2 transmissions) was just after the reboot. Maybe the 
corruption happend only after some hours of PC usage? Maybe after the reboot i 
had no corruption/crash because that retransmission was the only thing i was 
doing (there was no other apps opened , i only used startx to start openbox and 
then i did the transmissions via xfce-terminal so, the reason could be that 
this time i havent used much memory).

I'll now dump this installation partition (sda1) on the SSD, so that i can do 
the next test using the very same installation.

Next test is: SSD + 4gB.

ciao
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/32483394.2227721350407780835.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-22 Thread asronche...@libero.it

Hi,

`uptime ` is:
 02:47:34 up 6 days,  6:23,

and still no problem here.

the combination SSD + 4gB RAM is working great.

The only thing i changed was in /etc/fstab, i used "noatime,discard"  instead 
of "default" in the options column for the /home partition (ext4).

next test will start in the next days, with SSD + 8gB.

I think that probably the problem resides in how my installation is handling 
the 8gB ram.

Are there some special settings that i need to configure when switching from a 
4gB ram to 8gB ram?

ciao
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/33510800.4837651350953701205.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-23 Thread asronche...@libero.it



>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 23-ott-2012 3.02
>A: "asronche...@libero.it"
>Cc: <684...@bugs.debian.org>, 
>Ogg: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, 
working around it.
>
>On Tue, 2012-10-23 at 02:55 +0200, asronche...@libero.it wrote:
>> Hi,
>> 
>> `uptime ` is:
>>  02:47:34 up 6 days,  6:23,
>> 
>> and still no problem here.
>> 
>> the combination SSD + 4gB RAM is working great.
>> 
>> The only thing i changed was in /etc/fstab, i used "noatime,discard"  
instead 
>> of "default" in the options column for the /home partition (ext4).
>> 
>> next test will start in the next days, with SSD + 8gB.
>> 
>> I think that probably the problem resides in how my installation is 
handling 
>> the 8gB ram.
>> 
>> Are there some special settings that i need to configure when switching 
from a 
>> 4gB ram to 8gB ram?
>
>No change should be necessary.
>
>One thing I should have thought of earlier is that a pair of different
>memory modules might not be reliable.  In my personal experience, two
>different modules will often work, but it's generally recommended to use
>a matched set.
>
>Ben.
>
>-- 
>Ben Hutchings
>Humour is the best antidote to reality.
>


Hi,

(i'm still using SSD + 4gB , atm)

thanks for your reply.

dmidecode contains the string "Product Name: K52Jc"

I 've bought the 8gB on crucial.com. The site says that the hw they sell is 
100% compatiple for my notebook.

It works like this: 
i went on their website and then i entered "K52Jc" in the search form and then 
the site presents me all available and compatible upgrades for my notebook 
(K52Jc).
 
It showed me various SSD disks and only one RAM upgrade: 8gB.

According to dmidecode my mobo supports a maximum of 16gB of RAM, but checking 
on asus.com it seems that the notebook only support a max of 8gB.

So i bought and SSD and the 8gB RAM.

I've the 8gB RAM in front of me and i can read on one of the two: "4GB DDR3 - 
1333 (PC3 10600) SODI"


It is very similar to what i can see via dmidecode about the 4gB that are 
mounted at the moment on my notebook:

4gB on dmidecode:


Handle 0x0041, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 4

Handle 0x0042, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0041
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1067 MHz
Manufacturer: Kinston
Serial Number: 923C7BB9
Asset Tag: Unknown
Part Number: ASU1333D3S9DR8/2G 
Rank: Unknown

Handle 0x0043, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x000
Ending Address: 0x0007FFF
Range Size: 2 GB
Physical Device Handle: 0x0042
Memory Array Mapped Address Handle: 0x004B
Partition Row Position: Unknown
Interleave Position: 1
Interleaved Data Depth: 1

Handle 0x0044, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0041
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 1
Type: Unknown
Type Detail: None
Speed: Unknown
Manufacturer: [Empty]
Serial Number: [Empty]
Asset Tag: Unknown
Part Number: [Empty]
Rank: Unknown

Handle 0x0045, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0041
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: DIMM2
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1067 MHz
Manufacturer: Kinston
Serial Number: 923CDEB1
Asset Tag: Unknown
Part Number: ASU1333D3S9DR8/2G 
Rank: Unknown

Handle 0x0046, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x000
Ending Address: 0x0007FFF
Range Size: 2 GB
Physical Device Handle: 0x0045
Memory Array Mapped Address Handle: 0x004B
Partition Row Position: Unknown
Interleave Position: 2
Interleaved Data Depth

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM,

2012-10-26 Thread asronche...@libero.it

Hi,

kernel is 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux,

test with: SSD + 8gB.

nothing crashed for 28 hours. I also managed to copy 3 files (5-8 gB per file) 
to another pc via ethernet and the md5sums were ok. I also did the opposite 
(the other pc already had the known good files before these tests) copying the 
files from that pc to the notebook, md5sum comparison was ok.

So, i thought "Test will pass and the uptime will reach 5 or more days" .. 
no :(

at uptime == ~27 hours i decided to unmount the 1gB ramdisk , to mount a 4gB 
ramdisk.

i then started using it and xfce4-terminal crashed, on the screen this log 
appeared:


Oct 26 20:57:50 --- kernel: [102454.988228] general protection fault:  
[#1] SMP 
Oct 26 20:57:50 --- kernel: [102454.988291] CPU 0 
Oct 26 20:57:50 --- kernel: [102454.988315] Modules linked in: nfnetlink 
usb_storage uas cpufreq_conservative cpufreq_powersave cpufreq_stats bbswitch
(O) cpufreq_userspace uinput ext4 crc16 jbd2 loop snd_hda_codec_hdmi 
snd_hda_codec_conexant joydev arc4 ath9k ath9k_co
mmon ath9k_hw ath uvcvideo mac80211 videodev jmb38x_ms v4l2_compat_ioctl32 
mxm_wmi media coretemp crc32c_intel pcspkr psmouse evdev serio_raw intel_ips 
memstick cfg80211 battery snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_page_alloc snd_seq snd_seq_device snd_tim
er iTCO_wdt ac i915 power_supply iTCO_vendor_support video snd drm_kms_helper 
drm wmi asus_laptop i2c_algo_bit sparse_keymap i2c_core rfkill acpi_cpufreq 
input_polldev soundcore mperf button processor ext3 mbcache jbd sg sr_mod 
sd_mod cdrom crc_t10dif jme mii ahci liba
hci libata scsi_mod sdhci_pci sdhci mmc_core ehci_hcd usbcore usb_common 
thermal thermal_sys [last unloaded: nvidia]
Oct 26 20:57:50 --- kernel: [102454.989347] 
Oct 26 20:57:50 --- kernel: [102454.989366] Pid: 2684, comm: xfce4-terminal 
Tainted: P   O 3.2.0-3-amd64 #1 ASUSTeK Computer Inc. 
K52Jc/K52Jc
Oct 26 20:57:50 --- kernel: [102454.989483] RIP: 0010:[]  
[] do_sys_poll+0x1af/0x347
Oct 26 20:57:50 --- kernel: [102454.989569] RSP: 0018:8802403e9b68  
EFLAGS: 00010286
Oct 26 20:57:50 --- kernel: [102454.989621] RAX: 0145 RBX: 
 RCX: efff817f6fa0
Oct 26 20:57:50 --- kernel: [102454.989690] RDX: 880036d09480 RSI: 
880037080098 RDI: 880036d094b0
Oct 26 20:57:50 --- kernel: [102454.989758] RBP: 7f51a009d160 R08: 
 R09: 88003708
Oct 26 20:57:50 --- kernel: [102454.989826] R10: 88023ebe7510 R11: 
88023ebe7510 R12: 
Oct 26 20:57:50 --- kernel: [102454.989934] R13: 8802403e9e4c R14: 
0001 R15: 8802403e9e08
Oct 26 20:57:50 --- kernel: [102454.990041] FS:  7f519da01960() GS:
88024bc0() knlGS:
Oct 26 20:57:50 --- kernel: [102454.990162] CS:  0010 DS:  ES:  CR0: 
80050033
Oct 26 20:57:50 --- kernel: [102454.990248] CR2: 7f3c7a990181 CR3: 
00023ffcc000 CR4: 06f0
Oct 26 20:57:50 --- kernel: [102454.990355] DR0:  DR1: 
 DR2: 
Oct 26 20:57:50 --- kernel: [102454.990461] DR3:  DR6: 
0ff0 DR7: 0400
Oct 26 20:57:50 --- kernel: [102454.990567] Process xfce4-terminal (pid: 2684, 
threadinfo 8802403e8000, task 88023ebe7510)
Oct 26 20:57:50 --- kernel: [102454.990696] Stack:
Oct 26 20:57:50 --- kernel: [102454.990730]  8802  
0282 8802403e9e74
Oct 26 20:57:50 --- kernel: [102454.990856]  88023ebe7510  
8110717b 0019
Oct 26 20:57:50 --- kernel: [102454.990982]  8802413fa000 88023ebe7510 
 88020009
Oct 26 20:57:50 --- kernel: [102454.991107] Call Trace:
Oct 26 20:57:50 --- kernel: [102454.991153]  [] ? 
poll_freewait+0x97/0x97
Oct 26 20:57:50 --- kernel: [102454.991240]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991322]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991404]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991487]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991570]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991652]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991734]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991817]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991899]  [] ? 
__pollwait+0xce/0xce
Oct 26 20:57:50 --- kernel: [102454.991984]  [] ? 
sys_poll+0x43/0xab
Oct 26 20:57:50 --- kernel: [102454.992066]  [] ? 
system_call_fastpath+0x16/0x1b
Oct 26 20:57:50 --- kernel: [102454.992157] Code: ff 78 7e 48 8d b4 24 ac 03 
00 00 e8 f5 28 ff ff 48 85 c0 48 89 c2 b9 20 00 00 00 74 64 48 8b 48 20 b8 45 
01 00 00 48 85 c9 74 31 <48> 83 79 38 00 74 2a 48 85 db 74 10 66 41 8b 45 04 83 
c8 18 48 
Oct 26 20:57:50 --- kernel: [102454.992691] RIP  [] 
do_sys_poll+0x1af

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-10-27 Thread asronche...@libero.it

Hi,

i was using SSD + 4gB(A)

(A) is the first of the 2 4gB banks.

while browsing the plugin-container crashed many times, like this (from 
syslog):


kernel: [24135.522448] plugin-containe[7418] general protection ip:
7f23ffe8c1a1 sp:7f23fe02da00 error:0 in libflashplayer.so[7f23ff83+117b000]


then i launched xchat and let it run all night to download a big film (1080p, 
so it's ~20gB), but when i woke up i 've found that at ~6 o'clock (after ~10 
hours of xchat usage) xchat crashed:

xchat: *** glibc detected *** xchat: free(): invalid next size (fast): 
0x0172aa30 ***

Now it's 12:18:26 (UTC+2) and uptime is "up 14:29".

There wasnt (not yet) a system-level crash, but i think that those problems 
could be a good reason for me to move to the next test: 4gB(B)

[ with (B) as the second bank of the 2 4gB banks that are part of the 8gB set]

I think that another good test to do after that will be mixing the banks (1 of 
the known good 2*2gB set + 1 of the 2*4gB set), when doing that what is the 
right bank to put in the first slot (the lower one, the one that's the nearest 
to the mobo) , the 2gB or the 4gB one? Or is it the same?


ciao
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/7059977.7092281351333836467.JavaMail.root@wmail79

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-11-01 Thread asronche...@libero.it


Hi,

The second (B) bank of the 8gB set is working fine.

uptime is:
 20:54:53 up 5 days,  9:18,  7 users,  load average: 0.68, 0.56, 0.53

and i had no crashes, and right now i 've just tested also file transfer (via 
tar + nc), to see if i have md5sums inconsistencies and it works good , no data 
has been corrupted . :)

So i think the problem could be in the other bank (A) i unsuccessfully used 
last time.

Now i'm going to memtest it (A) with memtest86+ for some hours, to see if it's 
the root of all the problems.


ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/27615090.8858801351801457093.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-11-03 Thread asronche...@libero.it

Hi,

after ~48 hours of memtest86+ (almost 60 tests) , it has founded no errors on 
the 'problematic' RAM (the 4gB ram B of the 8gB set).

I'm now trying again to use that ram to run debian, to see if i have a crash 
also this time.

ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/22561044.9318171351972642373.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-11-03 Thread asronche...@libero.it

Hi,

The 4gB module B of the 8gB set isnt working. 

(B is the one that caused a system crash the last time i used it. It is the 
same that gave me *no* errors when i tested it via memtest86+)

after 4 hours i had a kernel panic: the notebook started a continuos 
'beeep' and on the screen syslog-like messages appeared.
I remember reading something about "swapper" and then at the bottom of the 
screen "kernel panic".

I was downloading a file via iceweasel and watching a movie via IRC/xdcc with 
the command:

nc -v -v -n IP PORT|pv|mplayer -cache 50 -

when suddently all crashed.

the ramdisk was 1gB and the tmpfs mounts (are they ramdisks?) are:
/run (376M)
/run/lock (5M)
/run/shm (752M)

Now i have replaced the module B with the module A* and i'm going to do 
exactly the same things i was doing (a web dwl + an Irc stream opened bia 
mplayer with cache == 500M ) to see if it crash again. 

* (the other 4gB module of the 8gB set, "A" is the one that worked well last 
time i used it alone)


ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1734894.6062461351988376723.JavaMail.defaultUser@defaultHost

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-11-09 Thread asronche...@libero.it


Hi,

with only the working 4gB SODIMM of the 8gB set i've reached a ~ 5days and 
15mins uptime.

Now i'm testing that SODIMM + one 2gB SODIMM from the 4gB set.
This way the ram will amount to ~ 6gB , so i'll be able to understand if my pc 
has some problems when the ram is > 4gB.

P.s.: someone is spamming on bugs.debian.org spoofing my email address:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683177
i 've signaled the spam using the "signal spam" link. I hope this doesnt get 
my email backlisted.
That spam was sent on 8th November. 
On 8th November i've send *no* emails.

ciao,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/4016423.11710681352475623733.JavaMail.defaultUser@defaultHost

Bug#684666: R: Re: Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-11-29 Thread asronche...@libero.it

Hi,

>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 10-nov-2012 19.23
>A: "asronche...@libero.it"
>Ogg: Re: Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS 
may corrupt low RAM, working around it.
>
>On Fri, 2012-11-09 at 16:40 +0100, asronche...@libero.it wrote:
>> Now i'm testing that SODIMM + one 2gB SODIMM from the 4gB set.
>> This way the ram will amount to ~ 6gB , so i'll be able to understand if my 
pc 
>> has some problems when the ram is > 4gB.
>
>Yes, that's a good experiment.

That experiment went well.
After that, i tried another experiment:

I mounted the problematic 4gB SODIMM into a notebook of a friend and he 
borrowed me one of his SODIMM (4gB) and the two laptops worked well.

In this case my laptop was using 2 SODIMM: 
SODIMM A) 4gB (it's the good one of the 8gB set)
SODIMM B) 4gB (it comes from my friend notebook)

so my friend notebook used this set:
SODIMM A) 2gB (it was already there in his notebook)
SODIMM B) 4gB (this is the one that created problems in my notebook)

my friend uses windows 7 and i use debian wheezy.
No problem arised . The two notebook worked good for more than 5 days without 
problems. After the 5 days i stopped the experiment and 
i gave back that SODIMM to my friend.

Conclusions:
1)The problematic SODIMM could be defective in a way that create problems when 
plugged in my notebook. (problem with its pins, maybe)

2)That SODIMM worked well in another notebook and passed long memtesting on my 
notebook. Why doesnt it work on my notebook? 
Why does it create memory corruption problems? This remains a mistery.

3)My notebook has no problem handling RAM amount >4gB, since it was able to 
survive a 5 days uptime with 8gB RAM mounted.

Problem is partially solved, since i can at least mount 6gB RAM on my notebook 
(4gB SODIMM + the old 2gB one )

Ben, thanks for your help but now i'm pretty sure that this is simply an 
hardware problem (since , as i could see , my debian wheezy 
installation had no problems to handle 8gB RAM)

>
>> P.s.: someone is spamming on bugs.debian.org spoofing my email address:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683177
>> i 've signaled the spam using the "signal spam" link. I hope this doesnt 
get 
>> my email backlisted.
>
>No, spam reporting should just result in that single message being
>hidden.
>
>Ben.

it's happend again, i've just seen that another spam email has been sent via 
my email account on 22 november.
I think that's because i usually use Tor to access the webmail. Maybe someone 
owning an exit node sniffed my traffic.
Some spam was sent to some subscription e-mail addresses, the ones with an 
hash in the address. I checked in my webmail 
and i've seen that they're the same mail addresses that were used by bugs.
debian.org to receive my subscription-confirmation.
That 'hash mail address' is the kind of thing someone can only know by using 
my webmail (aka accessing the list of addressess i've communicated with)

Ciao,
Asdrubale

-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/29234664.274371354198097450.JavaMail.defaultUser@defaultHost

Bug#683807: R: Re: Segfault while using mv/"fusermount -u" with sshfs share

2012-08-05 Thread asronche...@libero.it

Hi Jonathan, 
thanks for the information.

Sadly i think i cant reproduce this error. Error like these happens with 
random frequency.

I also had a similar error while reading/copying a file from ramdisk.

Yesterday i was checking an iso file with a torrent (i dumped the iso from a 
dvd to ramdisk) and i was only able to check until 71%. 
At 71% i had a very similar error.

I thought it was something to do with my ram (i recently updated from 4GB 
[2x2G] to 8GB [4x2G] ). Since the ram upgrade my problems started.
I ran memtest86+ for more ~20 hours (or 10 or more passes) and the program 
detected no error.

So yesterday i chat about this on IRC and some users said that the problem 
could have been in the ramdisk. They says that i cant use a 6.8GB ramdisk if my 
ram is only 8GB.
I objected that i was only using 2GB of ramdisk and that system ram usage was 
very low ( circa ~ 1GB ) .

Also i checked my configuration about tmp directories. That config assign a 
maximum total of 20% to tmpfs (like /tmp/ ). So it makes: ~1GB for system ram + 
1.6GB (total)  for various tmp dirs (not much used) + 2GB for the file (iso) on 
the ram.

It has been almost 2 years since i started using ramdisk with my pc. I noticed 
that it creates no problem if i assign a big space to the ramdisk. The only 
problem could start if i use *all* that space && the system is using too much 
ram. At that point, usually the swap partition come in the game and start 
swapping until a system crash.

Since in that case  i'll have a crash anyway , i disabled the swap partition, 
because now i have 8GB ram and it's enough for me , because i dont use much 
ram. 

My ordinary use of the system: evince (pdf files) , vlc (some films 
sometimes), a light and old videogame  (UrbanTerror). When i play with UrT i 
usually close all other apps.

About nvidia: I think i can exclude it as a cause of the malfunction. I use 
bumblebee (v3.0) from the suwako repository , to be able to use my 'nvidia 
optimus' card. On that front i have no problem at all. 
It works very good and all the crashes was not caused by the driver because it 
never crashed while i was using it. It also unload when i dont use it. (i use 
"optirun command" to execute the command with nvidia enabled. When i have no 
application using the card the card is disabled and module nvidia is unloaded.


bye
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/977982.4059981344171104505.JavaMail.defaultUser@defaultHost

Bug#683807: R: Re: Segfault while using mv/"fusermount -u" with sshfs share

2012-08-05 Thread asronche...@libero.it

Sorry, i forgot to answer to this:


>Messaggio originale
>Da: jrnie...@gmail.com
>Data: 5-ago-2012 10.39
>A: "asronche...@libero.it"
>Cc: <683...@bugs.debian.org>
>Ogg: Re: Segfault while using mv/"fusermount -u" with sshfs share
>
>Yeah, that's not good.  Thanks for reporting it.  Am I correct in
>assuming this only happened during one boot and you have not been able
>to make it happen again?



I exclude it could be an ssh server issue, since it happened again with a 
local cp/mv involving a ramdisk.
I think it could be a ram (or ram handling)  issue.

Right now i replaced the ram (8GB) with the old one (4GB) . I'll test the 
system for some days (maybe a week ) and if it doesnt crash i'll then try to 
put the 8GB ram back and see if things change with a ramdisk with < 6.8G space.

thanks.
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/6594566.4061051344171541872.JavaMail.defaultUser@defaultHost

Bug#683807: R: Bug#683807: R: Re: Segfault while using mv/"fusermount -u" with sshfs share

2012-08-05 Thread asronche...@libero.it

Hi Ben,

Yes, i can try. 
I think a week could be enough (crashes happens in a day or two, on my 
notebook). I'll start with tomorrow morning (Monday).

Do i need to uninstall all nvidia and bumblebee stuff and modules (modules: 
bbswitch and nvidia) or will this procedure be enough? 

1) disable bumblebee service and nvidia-kernel, using the rcconf application.
2) blacklist bbswitch via /etc/modprobe.d/blacklist.
4) mount back the 8GB ram (the one i was using when the problem appeared)
5) disable the nvidia card via BIOS (this allow me to use only the Intel 
integrated card. Nvidia card will not be visible by lspci)

thanks,
Asdrubale

>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 5-ago-2012 21.13
>A: "asronche...@libero.it", <683...@bugs.debian.org>
>Cc: 
>Ogg: Bug#683807: R: Re: Segfault while using mv/"fusermount -u" 
with sshfs share
>
>Can you try using the system without bumblebee and nvidia for a while?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/30183311.472281344208492863.JavaMail.defaultUser@defaultHost

Bug#683807: R: Bug#683807: R: Bug#683807: R: Re: Segfault while using mv/"fusermount -u" with sshfs share

2012-08-06 Thread asronche...@libero.it

Hi,

This morning when you sent your message i disabled bumblebee and nvidia, i 
rebooted and then i verified kernel.tainted. 
The value was 0. (ok)

But today,

I suspended-to-ram the notebook and i resumed after 2 minutes. Now , almost 30 
minutes later, iceweasel crashed 3 times,
 each time it crashes just a few seconds after the launch.

I noticed this in the syslog: (time is italian time) :

Aug  6 14:51:45 stan kernel: [37168.409654] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:51:45 stan kernel: [37168.607847] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:51:45 stan kernel: [37168.811535] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:54:55 stan kernel: [37358.716872] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:54:56 stan kernel: [37358.890747] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:54:56 stan kernel: [37359.089789] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:56:01 stan kernel: [37424.221231] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:56:01 stan kernel: [37424.415548] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:56:01 stan kernel: [37424.579289] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:57:07 stan kernel: [37490.289895] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:57:08 stan kernel: [37490.487921] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:57:08 stan kernel: [37490.691978] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:58:05 stan kernel: [37548.337713] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:58:06 stan kernel: [37548.534012] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 14:58:06 stan kernel: [37548.732858] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:02:12 stan kernel: [37794.609294] intel ips :00:1f.6: MCP limit 
exceeded: Avg power 40218, limit 35000
Aug  6 15:04:07 stan kernel: [37909.381592] intel ips :00:1f.6: MCP limit 
exceeded: Avg power 39909, limit 35000
Aug  6 15:05:04 stan kernel: [37966.530669] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:05:05 stan kernel: [37966.716222] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:05:05 stan kernel: [37966.890703] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:13:39 stan kernel: [38479.811089] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:13:39 stan kernel: [38479.966457] NVRM: No NVIDIA graphics adapter 
found!
Aug  6 15:13:39 stan kernel: [38480.148372] NVRM: No NVIDIA graphics adapter 
found!

and kernel was tainted:

kernel.tainted = 4097

so i opted for a complete uninstallation of bumblebee

 apt-get remove bumblebee bumblebee-nvidia
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  bbswitch-dkms libglu1-mesa virtualgl virtualgl-libs virtualgl-libs-ia32
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  bumblebee bumblebee-nvidia
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 222 kB disk space will be freed.
Do you want to continue [Y/n]? 
(Reading database ... 76865 files and directories currently installed.)
Removing bumblebee-nvidia ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in 
auto mode.
update-alternatives: using /usr/lib32/nvidia/libGL.so.1 to provide 
/usr/lib32/libGL.so.1 (ia32-libGL.so.1) in auto mode.
Removing bumblebee ...
[ ok ] Stopping Bumblebee daemon: bumblebeed.
Processing triggers for man-db ...

and then apt-get autoremove

now the "No NVIDIA graphics adapter found!" messages have stopped appearing.

could the bbswitch module itself be the cause of those segfaults?

note: i was connected via wireless when the problem appeared. browser is 
iceweasel 10.0.6 connected via Tor and using torbutton
I had very similar segfaults recently (~ 1 or 2 weeks ago) with transmission-
gtk. Also in that case it was a simple segfault (with "Segmentation Fault" in 
the xfce4-terminal) without any traces about that in the syslog.

i've just rebooted now, uptime was 11 hours.
After the reboot i tried to suspend-to-ram and there're no 'No NVIDIA' 
messages in the syslog this time.

Asdrubale.

>Messaggio originale
>Da: b...@decadent.org.uk
>Data: 6-ago-2012 1.39
>A: "asronche...@libero.it"
>Cc: <683...@bugs.debian.org>
>Ogg: Bug#683807: R: Bug#683807: R: Re: Segfault while using mv/"
fusermount -u" with sshfs share
>
>[Re-sending with the bug address cc'd.]
>
>On Mon, 2012-08-06 at 01:14 +0200, asronche...@libero.it wrote:
>> Hi Ben,
>> 
>> Yes, i can try. 
>> I think a week could be enough (crashes happens in a day or two, on my 
>> notebook). I'll start with tomorrow morning (Monday).
>> 
>> Do i need to uninstall all nvidia and bumblebee stuff and modules 
(modules: 
>> bbswitch and nvidia) or will this procedure b

Bug#683807: taintness

2012-08-06 Thread asronche...@libero.it

an update:

i've found this information:

Documentation/sysctl/kernel.txt

==

tainted:

Non-zero if the kernel has been tainted.  Numeric values, which
can be ORed together:

   1 - A module with a non-GPL license has been loaded, this
   includes modules with no license.
   Set by modutils >= 2.4.9 and module-init-tools.
4096 - An out-of-tree module has been loaded.
==



maybe the non-GPL module was the nvidia module.
I dont know what 'out-of-tree module' means.

anyway, uptime is 14hrs and still no problems :)




>From: "asronche...@libero.it" 
>Date: Mon, 6 Aug 2012 15:54:40 +0200 (CEST)
>
>and kernel was tainted:
>
>kernel.tainted = 4097


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/9484189.4349531344310766893.JavaMail.defaultUser@defaultHost

Bug#683807: good news

2012-08-08 Thread asronche...@libero.it

ok, 
1 day and 7 hours uptime. 

No problems, if i exclude:

1) [at ~ 24hrs uptime] an iceweasel segfault (no message on syslog, the 
browser simply disappeared) that was open since yesterday and problably is 
nothing strange.
2) a vlc crash , *probably* caused by the DVB-T broadcaster, RAI (http://rai.
it). I opened #684313 for that. Runtime was ~24 hours.

So,
I think the problem was related to the bbswitch and nvidia kernel modules (or 
just one of the two).
I'll do some more testing in the next weeks, but i'd like to take a break to 
play Urt now :D

@Ben,
about this:

>I can see that.  However I don't know whether bumblebee is really
>stable.  (It is at least under GPL, so it's possible to check what it's
>doing.)  Also the nvidia module could cause memory corruption that only
>becomes apparent after is is *unloaded*.  <-- 

Probably this is neither an nvidia driver bug. Maybe it's caused by the 
"optimus" technology.
As you said, bumblebee is not perfect. Maybe for my pc the only option is to 
keep it in 'nvidia mode' and when i want to switch to 'powersave-mode' i'll 
need to reboot with bumblebee and nvidia uninstalled.


So what if i try to boot the system, immediatly load the nvidia driver and i 
always keep it loaded? (lock bbswitch or bumblebee so that there is no switch 
at all)
All the crashes will stop occuring?


Thanks,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/31649434.70126135483071.JavaMail.defaultUser@defaultHost

Bug#683807: vlc crash, syslog message found

2012-08-08 Thread asronche...@libero.it

sorry, i didnt noticed that a message in syslog had appeared when the crash 
happened.

the message was:

Aug  8 13:31:02 --- kernel: [91908.859969] vlc[12411] general protection ip:
7f727fb1c428 sp:7f7287cacc50 error:0 in libts_plugin.so[7f727fb18000+14000]

so i can say that the crash happened exactly 20 minutes after the launch of 
the vlc command.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2205714.5159201344457309861.JavaMail.defaultUser@defaultHost

Bug#683807: the mouse

2012-08-08 Thread asronche...@libero.it

Sorry, i forgot what i think could be the most important thing:

Could this memory corruption problems be caused by a peripheral like an usb 
mouse?

in the previous message i included also some USB logs from the syslog 
regarding the usb mouse. It seems like it countinue being disconnected and then 
reconnected but i never touched it. I only plugged it on 21 o'clock (syslog 
time) and also i noticed that  'was not an MTP device' each time.

I had another mouse some month ago and when i plugged it the syslog showed the 
"not an MTP device" message. So i edited  /lib/udev/rules.d/69-libmtp.rules 
inserting a line for that mouse, including its idVendor and the string GOTO="
libmtp_rules_end".
After a while that mouse went dead (no red light anymore. It is like 'burned' 
)

Could a mouse cause a system crash ?


Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/101190.5173391344462361172.JavaMail.defaultUser@defaultHost

Bug#683807: mv ok after reboot

2012-08-08 Thread asronche...@libero.it

i'm sorry of the 'splitted brainstorming' with all these messages, but :

- after the reboot the mv command successfully moved the 3GB file from the 
client to the server (so i can exclude hardware problem related to hard disk on 
the client and/or the server)
- about the sr0 thing ("ata2:") i wasnt using the cd/dvd reader and that drive 
was empty. Just to exclude it as a cause is there a way to block it at boot 
level? (some commandline option in grub  ? )

- about the two crashes of some hours ago (vlc and iceweasel): i think these 
are *not* related to this bug. I think vlc crashed because of bad broadcasting 
from the tv station and iceweasel crashed because of some buggy webpage i left 
open (3 tabs with italian newspapers pages, heavy filled with javascript 
stuff).

- i'm going to reinstall bumblebee now to test for some days with the 
'automatic unload of driver' feature *disabled*, to understand if it is more 
stable or not.

- after that i'm going to do a test again with all bumblebee/nvidia  stuff 
uninstalled and with cd/dvd drive disabled.


thanks,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/8100781.5175361344463385459.JavaMail.defaultUser@defaultHost

Bug#683807: report with nvidia driver always loaded

2012-08-10 Thread asronche...@libero.it

Hi,

i changed bumblebee config to disable the use of bbswitch module. 
Atm uptime is 33 hours.
I only had some consecutive crashes of iceweasel yesterday. But right now 
everything seems to be working good.

here is my new bumblebee config:


# Configuration file for Bumblebee. Values should **not** be put between 
quotes

## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=true
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when 
Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia

## Client options. Will take effect on the next optirun executed.
[optirun]
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false


# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
#   switcheroo - vga_switcheroo method, use at your own risk
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
Module=nvidia
PMMethod=none
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:
/usr/lib/nvidia:/usr/lib32/nvidia
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau


I changed PMMethod to "none"  (bbswitch disabled and driver always on) and 
KeepUnusedXServer to "true".


bye,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/9092580.5461441344583739060.JavaMail.defaultUser@defaultHost

Bug#683807: bluetooth module loaded without hardware ?!? and then sys crash

2012-08-10 Thread asronche...@libero.it

Another crash (this time with nvidia module loaded), after 37 hours uptime.

It crashed irreparably at 16:03 (UTC). I had some previous faults with 
tranmission-gtk some hours before the system crash.
At (UTC) 11 and 13 o'clock transmission client crashed, 4 times in total:

Aug 10 13:04:51 *** kernel: [131998.170623] transmission-gt[13100] general 
protection ip:7ff69a2a19b6 sp:7ff6920fe7a0 error:0 in libc-2.13.so
[7ff69a229000+17d000]
Aug 10 13:07:39 *** kernel: [132165.956531] transmission-gt[13424]: segfault 
at 5 ip 7fe3bd9486e7 sp 7fff2dc47180 error 4 in transmission-gtk
[7fe3bd8ec000+bb000]
Aug 10 13:08:51 *** kernel: [132238.350504] transmission-gt[13439] general 
protection ip:7f7730a900e5 sp:7fff93945cb8 error:0 in libcairo.so.2.11200.2
[7f7730a2d000+f4000]
Aug 10 15:03:25 *** kernel: [139098.715300] transmission-gt[13464] general 
protection ip:7f76590fcdf9 sp:7fff1d9e9660 error:0 in libgobject-2.0.so.0.3200.3
[7f76590cc000+4e000]

Then i noticed that the 'gran finale' crash started creating syslog messages 
at 13:45 (UTC). It went on for hours, here is the first lines:

Aug 10 15:45:22 stan kernel: [141610.647648] INFO: rcu_sched detected stall on 
CPU 1 (t=15000 jiffies)
Aug 10 15:45:22 stan kernel: [141610.647689] sending NMI to all CPUs:
Aug 10 15:45:22 stan kernel: [141610.647694] NMI backtrace for cpu 2
Aug 10 15:45:22 stan kernel: [141610.647697] CPU 2 
Aug 10 15:45:22 stan kernel: [141610.647699] Modules linked in: bluetooth 
crc16 msr cpufreq_stats joydev fuse usbhid hid ip6table_filter ip6_tables 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter 
ip_tables x_tables uinput loop snd_hda_codec_hdmi snd_hda_codec_conexant nvidia
(P) mxm_wmi arc4 intel_ips coretemp pcspkr psmouse crc32c_intel serio_raw evdev 
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm ath9k snd_page_alloc ath9k_common 
snd_seq jmb38x_ms snd_seq_device ath9k_hw snd_timer iTCO_wdt i915 memstick 
iTCO_vendor_support ath snd mac80211 drm_kms_helper drm video battery cfg80211 
wmi i2c_algo_bit soundcore asus_laptop ac sparse_keymap power_supply rfkill 
acpi_cpufreq i2c_core input_polldev mperf button processor ext3 mbcache jbd 
sd_mod crc_t10dif sr_mod cdrom sdhci_pci sdhci mmc_core jme thermal mii 
thermal_sys ahci libahci ehci_hcd libata usbcore usb_common scsi_mod [last 
unloaded: joydev]
Aug 10 15:45:22 stan kernel: [141610.647782] 
Aug 10 15:45:22 stan kernel: [141610.647785] Pid: 0, comm: swapper/2 Tainted: 
P   O 3.2.0-3-amd64 #1 ASUSTeK Computer Inc. K52Jc/K52Jc
Aug 10 15:45:22 stan kernel: [141610.647790] RIP: 0010:[]  
[] tick_check_idle+0x25/0x97
Aug 10 15:45:22 stan kernel: [141610.647801] RSP: 0018:88024bc83f68  
EFLAGS: 0002
Aug 10 15:45:22 stan kernel: [141610.647804] RAX: 0002 RBX: 
88024bc8eab0 RCX: 880242dd7610
Aug 10 15:45:22 stan kernel: [141610.647806] RDX: 88024bc93740 RSI: 
0002 RDI: 0002
Aug 10 15:45:22 stan kernel: [141610.647809] RBP:  R08: 
 R09: 0f6a
Aug 10 15:45:22 stan kernel: [141610.647812] R10: 88023ed45510 R11: 
880242dd8000 R12: 0002
Aug 10 15:45:22 stan kernel: [141610.647814] R13: 0ad7 R14: 
12a9005392f8c6dc R15: 0002
Aug 10 15:45:22 stan kernel: [141610.647818] FS:  () GS:
88024bc8() knlGS:
Aug 10 15:45:22 stan kernel: [141610.647821] CS:  0010 DS:  ES:  CR0: 
8005003b
Aug 10 15:45:22 stan kernel: [141610.647823] CR2: 7fca65a74161 CR3: 
01605000 CR4: 06e0
Aug 10 15:45:22 stan kernel: [141610.647826] DR0:  DR1: 
 DR2: 
Aug 10 15:45:22 stan kernel: [141610.647829] DR3:  DR6: 
0ff0 DR7: 0400
Aug 10 15:45:22 stan kernel: [141610.647832] Process swapper/2 (pid: 0, 
threadinfo 880242dd8000, task 880242dd7610)
Aug 10 15:45:22 stan kernel: [141610.647834] Stack:
Aug 10 15:45:22 stan kernel: [141610.647836]  0002 
 88024bc99d70 8104c0fa
Aug 10 15:45:22 stan kernel: [141610.647841]  dc80 
810241c0 0f6a 0008
Aug 10 15:45:22 stan kernel: [141610.647845]  0003 
8135065e 880242dd9dd8   0003
Aug 10 15:45:22 stan kernel: [141610.647850] Call Trace:
Aug 10 15:45:22 stan kernel: [141610.647852]   
Aug 10 15:45:22 stan kernel: [141610.647859]  [] ? 
irq_enter+0x3c/0x56
Aug 10 15:45:22 stan kernel: [141610.647866]  [] ? 
smp_apic_timer_interrupt+0x2c/0x82
Aug 10 15:45:22 stan kernel: [141610.647872]  [] ? 
apic_timer_interrupt+0x6e/0x80
Aug 10 15:45:22 stan kernel: [141610.647874]   
Aug 10 15:45:22 stan kernel: [141610.647879]  [] ? 
intel_idle+0xea/0x118
Aug 10 15:45:22 stan kernel: [141610.647882]  [] ? 
intel_idle+0xc9/0x118
Aug 10 15:45:22 stan kernel: [141610.647889]  [] ? 
cpuidle_idle_call+0xec/0x179
Aug 10

Bug#683807: keyboard thing

2012-08-10 Thread asronche...@libero.it

there has to be something strange about the usb devices i use.

The last system freeze (10 or 20 mins ago) i wasnt able to reboot via 
AltGr+Print+B using the notebook keyboard, but when i unplugged the other 
keyboard (usb) and pressed again those keys it immediately rebooted.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/32148693.983591344615807124.JavaMail.defaultUser@defaultHost

Bug#684666: linux-image-2.6.32-5-amd64: general protection fault: 0000 [#1] SMP "Xorg Not Tainted"

2012-08-12 Thread asronche...@libero.it

Package: linux-2.6
Version: 2.6.32-45
Justification: breaks the whole system
Severity: critical

*** Please type your report below this line ***
System crashed , screen image was freezed (no way to use Ctrl+Alt+F1) and the 
only thing to do was to reboot via AltGr+Print+B.

Running applications were: Vlc, Iceweasel, Evince. 
System freezed while i was using vlc.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:00:17 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=7ce2c7e7-2851-411a-91c4-
37a2e2a3ba1a ro quiet vga=0x031b

** Not tainted

** Kernel log:
[2.265648] usb 1-1.2: Manufacturer: Sonix Technology Co., Ltd.
[2.265729] usb 1-1.2: configuration #1 chosen from 1 choice
[2.280851] udev[519]: starting version 164
[2.295374] Linux video capture interface: v2.00
[2.299516] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (13d3:5130)
[2.30] input: USB 2.0 Camera as /devices/pci:00/:00:1a.
0/usb1/1-1/1-1.2/1-1.2:1.0/input/input2
[2.306699] usbcore: registered new interface driver uvcvideo
[2.306703] USB Video Class driver (v0.1.0)
[2.330153] ACPI: SSDT ba798918 003E9 (v01  PmRef  Cpu0Ist 3000 
INTL 20051117)
[2.330966] ACPI: SSDT ba796698 005E5 (v01  PmRef  Cpu0Cst 3001 
INTL 20051117)
[2.332128] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:
00/input/input3
[2.346560] input: PC Speaker as /devices/platform/pcspkr/input/input4
[2.352300] ACPI: AC Adapter [AC0] (on-line)
[2.364280] ACPI: Lid Switch [LID]
[2.364338] asus_laptop: Asus Laptop Support version 0.42
[2.396613] ACPI: Battery Slot [BAT0] (battery present)
[2.402388] asus_laptop: BSTS called, 0xe800 returned
[2.403893] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:
00/input/input5
[2.403907] ACPI: Sleep Button [SLPB]
[2.403971] input: Asus Laptop extra buttons as 
/devices/virtual/input/input6
[2.404180] cfg80211: Using static regulatory domain info
[2.404182] cfg80211: Regulatory domain: US
[2.404184]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)
[2.404187]  (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm)
[2.404190]  (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[2.404193]  (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[2.404196]  (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[2.404199]  (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[2.404201]  (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm)
[2.404212] cfg80211: Calling CRDA for country: US
[2.408665] Monitor-Mwait will be used to enter C-1 state
[2.410958] asus_laptop: Brightness ignored, must be controlled by ACPI 
video driver
[2.413075] Monitor-Mwait will be used to enter C-2 state
[2.413190] processor LNXCPU:00: registered as cooling_device0
[2.413280] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:
00/input/input7
[2.413329] ACPI: Power Button [PWRF]
[2.414215] ACPI: SSDT ba797a98 00303 (v01  PmRefApIst 3000 
INTL 20051117)
[2.415005] ACPI: SSDT ba795d98 00119 (v01  PmRefApCst 3000 
INTL 20051117)
[2.423262] processor LNXCPU:01: registered as cooling_device1
[2.425448] jmb38x_ms :03:00.3: PCI INT B -> GSI 18 (level, low) -> IRQ 
18
[2.425457] jmb38x_ms :03:00.3: setting latency timer to 64
[2.426772] processor LNXCPU:02: registered as cooling_device2
[2.429681] processor LNXCPU:03: registered as cooling_device3
[2.447979] ath9k :02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[2.447996] ath9k :02:00.0: setting latency timer to 64
[2.489264]   alloc irq_desc for 22 on node -1
[2.489268]   alloc kstat_irqs on node -1
[2.489277] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 
22
[2.489354] HDA Intel :00:1b.0: setting latency timer to 64
[2.498087] ath: EEPROM regdomain: 0x60
[2.498091] ath: EEPROM indicates we should expect a direct regpair map
[2.498097] ath: Country alpha2 being used: 00
[2.498100] ath: Regpair used: 0x60
[2.519788] [drm] Initialized drm 1.1.0 20060810
[2.525423] phy0: Selected rate control algorithm 'ath9k_rate_control'
[2.525976] Registered led device: ath9k-phy0::radio
[2.525988] Registered led device: ath9k-phy0::assoc
[2.526004] Registered led device: ath9k-phy0::tx
[2.526016] Registered led device: ath9k-phy0::rx
[2.526037] phy0: Atheros AR9285 MAC/BB Rev:2 AR5133 RF Rev:e0: 
mem=0xc90011a4, irq=17
[2.594030] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[2.594036] i915 :00:02.0: setting latency timer to 64
[2.612126]   alloc irq_desc for 28 on node -1
[2.612130]   alloc kstat_irqs on node -1
[2.61

Bug#683807: the same notebook crashes also when i use stable

2012-08-12 Thread asronche...@libero.it

I tested the system with a debian stable installation i made on another 
partition.
The hardware is exactly the same. No nvidia, no bbswitch, and also no usb 
hardware.

It crashed after 6 hours of uptime: #684666 http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=684666

Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/21101681.2279541344790455403.JavaMail.defaultUser@defaultHost

Bug#684666: same hardware as in #683807

2012-08-12 Thread asronche...@libero.it

The hardware used is the same as in the bug #683807.
kernel not tainted and no usb was used.

Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/24261007.2279691344790575747.JavaMail.defaultUser@defaultHost

Bug#683807: bbswitch

2012-08-13 Thread asronche...@libero.it

Hi Ben,

I've seen the title has changed.

The first title (segfault while using mv ... ) was chaotic , i know. 
But "bbswitch causes instability" is not a correct title.

Indeed i tried:

a) use with nvidia driver + bbswitch . This lead to a crash.

b) i tried uninstalling nvidia stuff, bbswitch and bumblebee (aka normal 
system. It's like a fresh installation). It crashed.

c) i tried reinstalling bumblebee but disabling bbswitch (aka always use 
nvidia driver without the auto-remove-driver feature known as bbswitch). It 
crashed again.

then, 

d) i tried to use debian stable (i installed it on another partition on the 
very same hard disk). It still crashes.

So i think the problem is *not* bbswitch. The problem must be something 
hardware related. My notebook (Asus K52jc) must have some bad supported piece 
of hardware, i think that the problem is in some module(s).
This/these module/s is/are part of either 3.2.x kernels and 2.6.x kernels.

Atm this notebook is almost inusable :(
I really appreciate your activity here, please tell me if more information is 
needed to find where the bug is.

Thanks,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/32369776.1075821344864775821.JavaMail.defaultUser@defaultHost

Bug#684666: corrupted transmisison

2012-08-13 Thread asronche...@libero.it

>Ben Hutchings - Date: Sun, 12 Aug 2012 21:02:42 +0100
>'Breaks the whole system' does not mean the system crashed; please see
>.


Sorry, i'm a noob of the bug system (i started to submit bugs only recently).
Thanks for the link!

anyway, i see that 'Important' is related to new hardware:

"important

We include lack of support for new hardware that is generally available.
"

is my notebook considered new hardware? I bought it on late 2010 but it came
to the market in the first months of 2010.

also, as i said, this bug is related (the same) to the one in 683807. This bug
causes data corruption in memory and *communications*, as in 'grave':

"grave: ...or causes data loss...

We exclude loss of data in memory due to a crash. Only corruption of data
in storage or communication, or silent failure to write data, qualifies.
"

I had the very same errors with sshfs while copying data from this notebook to
the sshfs server.

Last night (i'm still using stable) i had that ssh error (with disconnection)
. I couldnt copy a file to the sshfs shared directory. So i used nc to 
transmit
the file and then i noticed that the md5sum of the origin and the one at the
destination was different (aka corrupted transmission).  The original file was
*not* on a ramdisk. It was on the hard disk (SSD).
I upgraded the hardisk some months ago. I bought an SSD disk. Could it be the
cause of the problem? Is there some special setting i have to use to correctly
use SSD on debian? Or is a simple 'mount and than reboot' enough ?

Thanks,
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/3542937.1397731344873119144.JavaMail.defaultUser@defaultHost

Bug#683807: near to be SOLVED ?

2012-08-18 Thread asronche...@libero.it

Hi,

i tried blacklisting iTCO_wdt and iTCO_vendor_support modules.

uptime is 2 days and 4 hours. Promblem, at the moment, seems solved.

i only had one problem moving a 5GB directory from the client to the sshfs 
server.: connection drop, again.
After that, i remounted that share and i repeated the mv command. While 
copying i unplugged the LAN cable and plugged it back in.
The moving of the 5GB was *successful* and i managed to do it with *no* *need* 
to reboot !!

the system is going well,
i think the problem was related to those two modules. As i 've read on some 
modprobe.d default files in an older pc it seems that iTCO_wdt could be cause 
of instability.
So i created blacklist.conf with:

blacklist iTCO_wdt
blacklist iTCO_vendor_support


During the uptime i only had 2 crashes of iceweasel, but it seems they were 
caused by some plugins/extensions.

i'll keep this bug updated.

Ciao
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/32726326.6904951345305605125.JavaMail.defaultUser@defaultHost

Bug#683807: no way :(

2012-08-19 Thread asronche...@libero.it

Hi.

New session, 21 hours uptime. Crash happened while copying a file via sshfs 
from client (this notebook ) to sshfs server. This time i had a kernel panic, 
with caps-lock led blinking and the hardreset via button as the only way to 
reboot.

Message appeared on the screen was about a WARNING in smp.c

Another anomaly is the fact that the line about 'modules linked in' contained 
also the bluetooth module. 
As cited in this bug ---> http://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=684516 the bluetooth module load itself with no reason. I dont have a 
bluetooth device on the notebook, and the command "apt-get remove bluetooth" 
gives this result:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package 'bluetooth' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.




bye

Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/8867183.2345231345390134568.JavaMail.defaultUser@defaultHost

Bug#684516: still loads with no reason

2012-08-19 Thread asronche...@libero.it

Hi Ben,

as i said in #683807 ,
the bluetooth package was removed via "apt-get remove" but the bluetooth 
module still loads with no reason.

bye
Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/26366302.2345801345390394120.JavaMail.defaultUser@defaultHost

Bug#684516: R: Re: Bug#684516: still loads with no reason

2012-08-19 Thread asronche...@libero.it



>Messaggio originale
>Da: jrnie...@gmail.com
>Data: 19-ago-2012 19.27
>A: "asronche...@libero.it"
>Cc: <684...@bugs.debian.org>
>Ogg: Re: Bug#684516: still loads with no reason
>
>asronche...@libero.it wrote:
>
>> as i said in #683807 ,
>> the bluetooth package was removed via "apt-get remove" but the bluetooth 
>> module still loads with no reason.
>
>The bluetooth support packages in userspace have names containing
>"bluez", not bluetooth.  (Though I have no idea whether they
>trigger autoloading of the bluetooth module or if it's udev's
>responsibility.)
>
>Hope that helps,
>Jonathan
>

Thanks for the advice. I checked via aptitude but i have already removed the 
bluez package.

aptitude search bluez
c   
bluez   

- Bluetooth tools and 
daemons   
pB  bluez-
alsa
  
- Bluetooth ALSA 
support 
   
p   bluez-
audio   
  
- Transitional 
package 
 
p   bluez-
compat  
  
- BlueZ 3.x compatibility 
binaries  
pi  bluez-
cups
  
- Bluetooth printer driver for 
CUPS 
p   bluez-
dbg 
  
- Bluetooth tools and daemons (with debugging 
symbols)  
p   bluez-
firmware
  
- Firmware for Bluetooth 
devices
pB  bluez-
gstreamer   
  
- Bluetooth GStreamer 
support   
p   bluez-
hcidump 
  
- Analyses Bluetooth HCI 
packets
p   bluez-pcmcia-
support- 
PCMCIA support files for BlueZ 2.0 Bluetooth 
tools
p   bluez-
tools   
  
- Set of tools to manage Bluetooth devices for 
linux
p   bluez-
utils   
  
- Transitional 
package 
 
p   python-
bluez   
 
- Python wrappers around BlueZ for rapid bluetooth 
development  
v   python2.6-
bluez 
-   

v   python2.7-bluez   




Ben Hutchings @ Sun, 19 Aug 2012 17:56:35 +0100
>Not a bug; please stop pursuing this irrelevant detail.

How can you think that it's not a bug?

1) I dont have bluetooth devices attached to this notebook.
2) I followed your advice and i removed the bluetooth package
3) today i had a kernel panic and the error message appeared on the the screen 
showed a list of loaded modulse. The first module of that list was indeed the 
bluetooth module.


Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/28779826.2756611345398110312.JavaMail.defaultUser@defaultHost

Bug#684516: R: Bug#684516: bluetooth loaded for UNKNOWN reason

2012-08-20 Thread asronche...@libero.it



>Messaggio originale
>Da: stapp...@stappers.nl
>Data: 19-ago-2012 21.51
>A: "asronche...@libero.it"
>Cc: <684...@bugs.debian.org>
>Ogg: Bug#684516: bluetooth loaded for UNKNOWN reason
>My advice is to research what causes the bluetooth module be loaded.
>
>I would start with checking udev rules.

udev rules are the default ones of a fresh squeeze installation and i 've 
found no strange.bluetooth stuff in them. (and also i never touched udev 
default config files).

>
>Thing I would NOT do, is yelling: Nobody listens to me!

Hey! there's no need to start trolling >:|

I was just pointing the FACT that the problem is *not* caused by the 
bluetooth/bluez packages.

Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/23486237.7521121345495724973.JavaMail.defaultUser@defaultHost

Bug#683807: #684807 , iptables config, sysctl.conf, rc.local

2012-08-23 Thread asronche...@libero.it

Hi,
just to be more precise, i include here my iptable config, sysctl.conf, and i 
list the rc.local stuff.
Is it possible that i did some mess in some of these files and that caused the 
crashes that follow me in many systems (wheezy, stable).


Iptables firewall config:

#!/bin/sh

sysctl net.netfilter.nf_conntrack_acct=1

# Variables

IPTABLES=/sbin/iptables

WAN_IFACE="ath0 eth0"

if [ "$1" = "start" ]; then
echo "Starting Firewall"

# Flush Current Rules
$IPTABLES -F
$IPTABLES -X  # delete all user-defined chains

echo 1 > /proc/sys/net/ipv4/tcp_syncookies # DoS Protection
echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts # Disable responding 
to ping broadcasts
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter # disable spoofing on all 
interfaces


# Set Default Rules for Chains

$IPTABLES -P INPUT DROP  # Drop every packet from the outside
$IPTABLES -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT  # Allow 
requested INPUTS

# Accept local requests
$IPTABLES -P OUTPUT ACCEPT

# Drop since NAT protocol is not required 
$IPTABLES -P FORWARD DROP

#allow src==dst==lo
$IPTABLES -A INPUT -i lo -d 127.0.0.1  -j ACCEPT
$IPTABLES -A OUTPUT -o lo -s 127.0.0.1  -j ACCEPT

$IPTABLES -A INPUT -p tcp -m tcp --dport 6000 -j DROP
$IPTABLES -A OUTPUT -p tcp -m tcp --sport 6000 -j DROP



cat /root/stop6 |ip6tables-restore

# Section to open desired ports

# Open Ports for SSH and HTTP
#$IPTABLES -A INPUT -i $WAN_IFACE -p TCP --destination-port 22 -j ACCEPT

#$IPTABLES -A INPUT -i $WAN_IFACE -p TCP --destination-port 80 -j ACCEPT

elif [ "$1" = "stop" ]; then
echo "Firewall Halted"
$IPTABLES -F 
$IPTABLES -X
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P FORWARD DROP
$IPTABLES -A INPUT -p tcp -m tcp --dport 6000 -j DROP
$IPTABLES -A OUTPUT -p tcp -m tcp --sport 6000 -j DROP

elif [ "$1" = "status" ]; then
$IPTABLES -L -v -n

else
echo "usage: $0 start|stop|status"
fi
#iptables -A INPUT -p tcp -m tcp --dport 6000 -j DROP;iptables -A OUTPUT -p 
tcp -m tcp --sport 6000 -j DROP

-





/etc/sysctl.conf:

#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additonal system variables
# See sysctl.conf (5) for information.
#

#kernel.domainname = example.com

# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3

##3
# Functions previously found in netbase
#

# Uncomment the next two lines to enable Spoof protection (reverse-path 
filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1

# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1

# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1

# Uncomment the next line to enable packet forwarding for IPv6
#  Enabling this option disables Stateless Address Autoconfiguration
#  based on Router Advertisements for this host
#net.ipv6.conf.all.forwarding=1


###
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Do not accept IP source route packets (we are not a router)
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#
# Log Martian Packets
net.ipv4.conf.all.log_martians = 1
#




net.ipv4.conf.default.accept_source_route = 0
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv4.ip_default_ttl = 128
net.ipv4.conf.eth0.accept_source_route = 0
net.ipv4.conf.wlan0.accept_source_route = 0 
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1
net.ipv6.conf.wlan0.disable_ipv6 = 1

--



/etc/rc.config call some scripts to set the firewall,  bring eth0 up, it 
removes two modules (the cam and the joystik modules), remove the dhcp-fail 
network (169.254.0.0/16), mount the ramdisk (1 GB) and then call ethtool to fix 
the "UDP checksum fail" issue of my net card:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
#

Bug#684516: R: Re: Regarding: Bug#684516: bluetooth loaded for UNKNOWN reason

2012-08-25 Thread asronche...@libero.it

Hi,
thanks for your advice. I'm going to test this in a week or two. (i'll restore 
a backup image , via dd)
At the moment i installed another distro on this pc, to understand if the 
problem is hardware related.

indeed, it could be a simple hardware problem on this asus notebook, like a 
buggy mobo for example.

#683807 made me think that.
indeed , the strange thing: nobody posted a message like: "hey i have that 
problem too!" . 

After the test with the other distro, i'll restore debian on this pc.

btw, what do you mean with 'ramdisk' ? is that 'initramfs' ? if i remove that 
file, will the system be still bootable?
(sorry, i still am not an expert about the linux boot stuff)

bye
Asdrubale

>Messaggio originale
>Da: stapp...@stappers.nl
>Data: 25-ago-2012 19.59
>A: "asronche...@libero.it"
>Cc: 
>Ogg: Re: Regarding: Bug#684516: bluetooth loaded for UNKNOWN reason
>
>On Thu, Aug 23, 2012 at 09:46:07AM +0200, asronche...@libero.it wrote:
>> Da: stapp...@stappers.nl
>> Data: 20-ago-2012 22.56
>> >
>> >My advice is to research what causes the bluetooth module to be loaded.
>> >
>>
>> that was the reason for me to open this bug report.
>> was it such a simple task i'd already solved it by myself.
>
>Nobody said it would be easy.
>
>
>Another approach to the challenge:
>
>Remove the bluetooth module from /lib/modules and the initial ramdisk,
>so that the computer hasn't any more the module.
>
>You might get an error message from what tries to load bluetooth.
>Yes, I assume that the computer boots.
>
>No load error on bluetooth only a problem,
>when the crash is gone.
>
>
>What I'm trying to say:
>
>* focus on the problem^Wchallenge
>* no limits  ( so removing the bt module, is not beyond a limit )
>* do not wait for other
>
>
>Groeten
>Geert Stappers
>-- 
>> And is there a policy on top-posting vs. bottom-posting?
>Yes.
>

-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/15174664.8471961345921650702.JavaMail.defaultUser@defaultHost

Bug#683807: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

2012-08-28 Thread asronche...@libero.it

Hi, 
i've found this in a syslog on my debian stable installation /var/log 
directory:

Aug 21 17:11:35 *** kernel: [0.00] AMI BIOS detected: BIOS may corrupt 
low RAM, working around it.

Could this message indicate the root of all these corruption/instability 
problems?
And what could it mean? My bios is corrupted and it is also corrupting memory?

Asdrubale


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/12473533.8948551346143647789.JavaMail.defaultUser@defaultHost

37 matches

Mail list logo