Bug#684666: R: Re: Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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 +01

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

Bug#683177: someone is spamming spoofing my mail address

i've noticed in my mailbox that someone is spoofing my email address to send spam to bugs.debian.org the previous message on this page (the one containing a link to some seo website) was sent yesterday but I've sent no mail yesterday. (i wasnt even connected to the net) today, reading my mailb

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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 syslo

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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-bugs-dist-r

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

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

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

Bug#684666: R: Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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-

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

Bug#684666: #684666 and #683807

[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, t

Bug#683807: AMI BIOS detected: BIOS may corrupt low RAM, working around 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

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

#x27;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: >

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

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.net

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

>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 l

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

>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 ,

Bug#684516: still loads with no reason

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-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb

Bug#683807: no way :(

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 i

Bug#683807: near to be SOLVED ?

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 t

Bug#684666: corrupted transmisison

>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! anywa

Bug#683807: bbswitch

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 a

Bug#684666: same hardware as in #683807

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-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

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 UNSUBSCR

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

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 wer

Bug#684516: kernel loads bluetooth module, without reason (no HW)

Package: base Severity: important Dear Maintainer, as i noticed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683807#85 The kernel loads the bluetooth module also if i have no bluetooth hardware on this notebook. kernel is 3.2.0-3-amd64 #1 SMP x86_64 and i'm using debian wheezy bye,

Bug#683807: keyboard thing

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

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

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 *** ker

Bug#683807: report with nvidia driver always loaded

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

Bug#683807: mv ok after reboot

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 wasn

Bug#683807: the mouse

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 the

Bug#683807: vlc crash, syslog message found

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 ex

Bug#683807: good news

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:/

Bug#684313: vlc crash while playing DVB-T udp multicast (stream generated elsewhere on the LAN via mumudvb)

Package: vlc Version: 2.0.2-2 Severity: normal Dear Maintainer, I use mumudvb on my LAN when i want to watch DVB-T television. I start "mumudvb -stdc some_dvbt-mux-configuration" on the other pc and i use this pc (a notebook) to view the udp multicast stream via vlc. The command i use is: "vlc

Bug#683807: taintness

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-bugs-dist-requ...@lists.debia

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

27; 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&qu

Bug#683177: sorry, wrong email

i'm sorry for my previous mail message , i was trying to subscribe to this bug but i used a wrong address (i 've forgot the "-subscribe@" ) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683177:

-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

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"

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

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

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

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

Bug#683748: WARNING: at /kernel/net/sched/sch_generic.c

Package: src Version: 3.2.21-3 Severity: normal -Crash while playing a video file with mplayer via sshfs- Dear Maintainer, I was using mplayer to play a video file in fullscreen mode. The file was located on another pc on my LAN. The directory used was shared via sshfs. Some seconds later the b