[Kernel-packages] [Bug 1281930] Re: nVidia on board network card with forcedeth driver freezes systems on AM3+ CPU

2014-02-19 Thread Christopher M. Penalver
Marco Aicardi, thank you for reporting this and helping make Ubuntu better. As 
per https://www.asus.com/Motherboards/M3N78VM/#support, an update to your BIOS 
is available (1801). If you update to this following 
https://help.ubuntu.com/community/BiosUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Thank you for your understanding.

** Description changed:

- I have a Ubuntu 13.10 amd64 system with a nVidia Force3 mainboard with
- nVidia forcedeth-driver network card running on a Phenom X4 965
- processor.
+ The network is completely 1000mbps wired and the main server is a HP
+ Proliant microserver running Ubuntu 13.10 amd64. When the network
+ transfers at 1000mbps, the system becomes unresponsive, and usually
+ freezes for a long time; even sound and mouse freeze. When the data
+ transmission is ended, the system starts running smoothly again.
  
- The network is completely 1000mbps wired and the main server is a HP
- Proliant microserver running Ubuntu 13.10 amd64.
- 
- When the network transfers at 1000mbps, the system becomes unresponsive,
- and usually freezes for a long time; even sound and mouse freeze.
- 
- When the data trasmission is ended, the system starts running smoothly
- again.
- 
- Googling around I found that there was a workaround for similar network
- problems regarding AM3+ CPUs on nForce mainboards, and the problem
- seemed related to a a problem between forcedeth and ACPI.
- 
- The workarounds that suggest removing forcedeth module at start-up and
- reloading with modprobe forcedeth msi=0 msix=0 seem to work on my
- system and I have not had freezes again.
- 
- I attach debug info requested by penalvch.
+ WORKAROUND: emoving forcedeth module at start-up and reloading with:
+ modprobe forcedeth msi=0 msix=0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.25
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2544 F pulseaudio
   /dev/snd/pcmC0D0p:   marco  2544 F...m pulseaudio
  Date: Wed Feb 19 07:36:12 2014
  HibernationDevice: RESUME=UUID=c0261cd6-eee5-4be4-9834-71126c5a4243
  InstallationDate: Installed on 2014-01-04 (45 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  IwConfig:
   tun0  no wireless extensions.
  
   eth0  no wireless extensions.
  
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcFB:
  
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=7ece1425-d919-4b89-a053-5411564177a8 ro quiet splash 
libata.force=noncq
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
  
  dmi.bios.date: 04/13/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd04/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Tags added: bios-outdated-1801

** Summary changed:

- nVidia on board network card with forcedeth driver freezes systems on AM3+ CPU
+ 10de:0760 [Asus M3N78-VM] nVidia on board network card with forcedeth driver 
freezes system

** Changed in: linux (Ubuntu)
   Importance: Undecided = Low

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1281930

Title:
  10de:0760 [Asus M3N78-VM] nVidia on board network card with forcedeth
  driver freezes system

Status in “linux” package in Ubuntu:
  

[Kernel-packages] [Bug 1281930] Re: nVidia on board network card with forcedeth driver freezes systems on AM3+ CPU

2014-02-18 Thread Marco Aicardi
** Description changed:

  I have a Ubuntu 13.10 amd64 system with a nVidia Force3 mainboard with
  nVidia forcedeth-driver network card running on a Phenom X4 965
  processor.
  
  The network is completely 1000mbps wired and the main server is a HP
  Proliant microserver running Ubuntu 13.10 amd64.
  
- When the network transfer at 1000mbps, the system becomes unresponsive,
+ When the network transfers at 1000mbps, the system becomes unresponsive,
  and usually freezes for a long time; even sound and mouse freeze.
  
- When the data trasmissione is ended, the system starts running smoothly
+ When the data trasmission is ended, the system starts running smoothly
  again.
  
  Googling around I found that there was a workaround for similar network
  problems regarding AM3+ CPUs on nForce mainboards, and the problem
  seemed related to a a problem between forcedeth and ACPI.
  
  The workarounds that suggest removing forcedeth module at start-up and
  reloading with modprobe forcedeth msi=0 msix=0 seem to work on my
  system and I have not had freezes again.
  
  I attach debug info requested by penalvch.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-15-generic 3.11.0-15.25
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  marco  2544 F pulseaudio
-  /dev/snd/pcmC0D0p:   marco  2544 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  marco  2544 F pulseaudio
+  /dev/snd/pcmC0D0p:   marco  2544 F...m pulseaudio
  Date: Wed Feb 19 07:36:12 2014
  HibernationDevice: RESUME=UUID=c0261cd6-eee5-4be4-9834-71126c5a4243
  InstallationDate: Installed on 2014-01-04 (45 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  IwConfig:
-  tun0  no wireless extensions.
-  
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  tun0  no wireless extensions.
+ 
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=7ece1425-d919-4b89-a053-5411564177a8 ro quiet splash 
libata.force=noncq
  RelatedPackageVersions:
-  linux-restricted-modules-3.11.0-15-generic N/A
-  linux-backports-modules-3.11.0-15-generic  N/A
-  linux-firmware 1.116
+  linux-restricted-modules-3.11.0-15-generic N/A
+  linux-backports-modules-3.11.0-15-generic  N/A
+  linux-firmware 1.116
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
-  
+ 
  dmi.bios.date: 04/13/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd04/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1281930

Title:
  nVidia on board network card with forcedeth driver freezes systems on
  AM3+ CPU

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have a Ubuntu 13.10 amd64 system with a nVidia Force3 mainboard with
  nVidia forcedeth-driver network card running on a Phenom X4 965
  processor.

  The network is completely 1000mbps wired and the main server is a HP
  Proliant microserver running Ubuntu 13.10 amd64.

  When the network transfers at 1000mbps, the system becomes
  unresponsive, and usually freezes for a long time; even sound and
  mouse freeze.

  When the data trasmission is ended, the system starts running smoothly
  again.

  Googling around I found that there was a workaround for similar
  network problems regarding AM3+ CPUs on nForce mainboards, and the
  problem seemed related to a a problem between forcedeth and ACPI.

  The workarounds that suggest removing forcedeth module at start-up and
  reloading with modprobe forcedeth msi=0 msix=0 seem to work on my
  system and I have not had freezes again.

  I