2) It is a kernel bug where google-chrome (as well as chromium) plays the mere role of a trigger (and only if the chrome sandbox is used)
3) It is related to the use of
chrome + internet access via mobile phone on usb (i.e. mobile phone attached via usb cable to the computer and ppp).
does not happen when access to the internet is given by wifi or ethernet
Seems to be reproducible by
a) go online with a mobile access
b) start google chrome
c) navigate some pages
d) exit chrome
on d) system locks up.
in the above link at the chromium bug tracker, there is also a screenshot of a kernel log. The bug so far has been discussed there, but the discussion should be taken to the kernel developers, since chrome seems to be just a trigger.
Some news about this bug:
1) It is confirmed by other users, even on other distros. See http:// code.google. com/p/chromium/ issues/ detail? id=54617
2) It is a kernel bug where google-chrome (as well as chromium) plays the mere role of a trigger (and only if the chrome sandbox is used)
3) It is related to the use of
chrome + internet access via mobile phone on usb (i.e. mobile phone attached via usb cable to the computer and ppp).
does not happen when access to the internet is given by wifi or ethernet
Seems to be reproducible by
a) go online with a mobile access
b) start google chrome
c) navigate some pages
d) exit chrome
on d) system locks up.
in the above link at the chromium bug tracker, there is also a screenshot of a kernel log. The bug so far has been discussed there, but the discussion should be taken to the kernel developers, since chrome seems to be just a trigger.