| 2008-10-14 12:47:31 |
Christophe Dumez |
bug |
|
|
added bug |
| 2008-10-14 12:52:42 |
Jean-Baptiste Lallement |
linux: status |
New |
Incomplete |
|
| 2008-10-14 12:52:42 |
Jean-Baptiste Lallement |
linux: statusexplanation |
|
Thanks for your report.
This is likely a dup of bug 276990
Can you please provide the following information:
- run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the file lspci-vvnn.log
- run the command "dmesg > dmesg.log" and attach the file dmesg.log
- the output of the command uname -a |
|
| 2008-10-26 10:04:20 |
Christophe Dumez |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci -nnvv output) |
| 2008-10-26 10:04:51 |
Christophe Dumez |
bug |
|
|
added attachment 'dmesg.log' (dmesg output) |
| 2008-10-26 10:11:20 |
Christophe Dumez |
bug |
|
|
added attachment 'dmesg.log' (dmesg after crash and reboot) |
| 2008-10-26 18:08:33 |
Jean-Baptiste Lallement |
linux: status |
Incomplete |
Confirmed |
|
| 2008-10-26 18:08:33 |
Jean-Baptiste Lallement |
linux: statusexplanation |
Thanks for your report.
This is likely a dup of bug 276990
Can you please provide the following information:
- run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the file lspci-vvnn.log
- run the command "dmesg > dmesg.log" and attach the file dmesg.log
- the output of the command uname -a |
Thanks for following up. The information you've provided confirms that this is the same issue. Feel free to add your comment on the other report.
Thanks for your time. |
|
| 2008-10-26 18:08:43 |
Jean-Baptiste Lallement |
marked as duplicate |
|
276990 |
|
