03:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 6
Ubuntu Lucid AMD64 2.6.32-22
The same here:
[ 202.011265] [ cut here ]
[ 202.011278] WARNING: at
/build/buildd/linux-2.6.32/net/sched/sch_generic.c:261
dev_watchdog+0x262/0x270()
[ 202.011281] Hardware name: System Product Name
[ 202.011283] NETDEV WATCHDOG: eth1 (81
Have you tried www.speedtest.net ? Are you able to complete a speed test
?
--
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
So you don't have libflashplayer 9.0.115. I think you have another
problem.
--
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
It's strange, it solved the issue on two gutsy AMD64 machines for me.
Do you see any flash animation or no animation at all ?
Insert about:plugins as URL in Firefox, do you see any info about
flashplugin ?
I see:
Shockwave Flash
Nome file: npwrapper.libflashplayer.so
Shockwave Flash 9.0
This is the patch made by nspluginwrapper author.
It works for me with Ubuntu repository source.
** Attachment added: "npw.gthreads.diff"
http://launchpadlibrarian.net/11055616/npw.gthreads.diff
--
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bu
The issue seems to be present only in SMP/SMT machines, as nspluginwrapper
author told me.
Now I'm testing a Makefile patch. Preliminary results are encouraging.
--
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
You received this bug noti
** Description changed:
Binary package hint: flashplugin-nonfree
Aflter last upgrade of flashplugin-nonfree, Flash apps crash leaving a greyed
rectangle in the page. The issue appears frequently, but sometimes all works
fine.
At this url I obtain a 100% fail: www.speedtest.net
Sometim
Copying libflashplayer.so version 9.0.48 over
/usr/lib/flashplugin-nonfree/libflashplayer.so 9.0.115 solves the issue.
I think this should be a problem of synchronization between nspluginwrapper and
libflshplayer.so.
Now I can definitively confirm that support of Adobe Flash plugin it's
broken i
** Also affects: nspluginwrapper
Importance: Undecided
Status: New
--
Gutsy 64: nspluginwrapper errors with flashplugin-nonfree 9.0.115
https://bugs.launchpad.net/bugs/177856
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Binary package hint: flashplugin-nonfree
Aflter last upgrade of flashplugin-nonfree, Flash apps crash leaving a greyed
rectangle in the page. The issue appears frequently, but sometimes all works
fine.
At this url I obtain a 100% fail: www.speedtest.net
Sometimes I can load
Ubuntu AMD64
Linux cionci 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007
x86_64 GNU/Linux
** Description changed:
Running Netbeans with Compiz active is impossible because Netbeans main
window looks all greyed (like in this bug report:
https://bugs.launchpad.net/ubuntu/+source/sun
Public bug reported:
Running Netbeans with Compiz active is impossible because Netbeans main
window looks all greyed (like in this bug report:
https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/124562 ). It
seems to be a bug related to all Swing windows.
Exporting
export AWT_TOOLKIT="MTool
No news ?
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
** Description changed:
- During boot, long fsck on non-root partitions does not show progress
indicator, otherwise long fsck on root partition does.
+ During boot, long fsck on non-root partitions does no
** Description changed:
- During boot, long fsck on non-root partitions does not show progress
indicator, otherwise long fsck on root partition do.
+ During boot, long fsck on non-root partitions does not show progress
indicator, otherwise long fsck on root partition does.
This could take to t
Public bug reported:
During boot, long fsck on non-root partitions does not show progress indicator,
otherwise long fsck on root partition do.
This could take to think the system is locked.
Edgy upgraded to Feisty, updated daily.
** Affects: Ubuntu
Importance: Undecided
Status: Un
Bug still present in 2.6.20-15.27
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Bug still present in 2.6.20-15.25
Now the system boots always thanks to UUID parameter to kernel, but sometimes
boot with one and sometimes with the other partition order.
Order with SATA as sdc has high probability in a cold boot (from one to three
incorrect boot after the first can occur).
Afte
Works for me
--
MASTER: Computer will not boot after 2.6.20-14.23 kernel upgrade
https://bugs.launchpad.net/bugs/106063
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ub
image the system boots well, but I've the random issue linked below, maybe it's
related to this.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103898
Linux cionci 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686
GNU/Linux
--
System hangs duri
27;s
related to this.
+ https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103898
Linux cionci 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686
GNU/Linux
** Description changed:
Binary package hint: linux-image-2.6.20-14-generic
My system freezes on boot during detectio
.6.20/+bug/103898
Linux cionci 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686
GNU/Linux
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
System hangs during boot on sata_nv, only with linux-image-2.6.20-14.23
https://bugs.launchpad.net/b
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/7317114/dmesg.log
--
System hangs during boot on sata_nv, only with linux-image-2.6.20-14.23
https://bugs.launchpad.net/bugs/106132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Here is where the system hangs
** Attachment added: "DSCF1089.JPG"
http://librarian.launchpad.net/7317112/DSCF1089.JPG
--
System hangs during boot on sata_nv, only with linux-image-2.6.20-14.23
https://bugs.launchpad.net/bugs/106132
You received this bug notification because you are a member
I think you have to fill a new bug report for mdadm.
To see more detailed messages during boot, in grub menu delete quiet line and
delete "quiet splash" from kernel line and then boot.
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received
Your issue could be related to this:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
/proc/partitions when in BusyBox attached .
** Attachment added: "BusyBox_partitions.log"
http://librarian.launchpad.net/7219132/BusyBox_partitions.log
** Attachment removed: "BusyBox_partitions.log"
http://librarian.launchpad.net/7219131/BusyBox_partitions.log
--
Feisty randomly fails
/proc/partitions attached when in BusyBox.
** Attachment added: "BusyBox_partitions.log"
http://librarian.launchpad.net/7219131/BusyBox_partitions.log
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because
I think I've identified the problem.
When the system boot in BusBox I've a wrong disk order and naming.
I attached /proc/partitions in the correct boot case.
SCSI disks are sdb and sdc. SATA disk is sda
Looking in /proc/partitions in BusyBox shows that SCSI disks become sda and sdb
and SATA disk
Thank you ;)
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/7193773/dmesg.log
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Linux cionci 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686
GNU/Linux
But the same issue appears also on 2.6.20-13.
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7193767/lspci-vvnn.log
--
Feisty randomly fails to boot and BusyBox shell sta
Public bug reported:
Binary package hint: update-manager
# sudo update-manager
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes include: the remote app
Here is the picture.
** Attachment added: "DSCF1085.JPG"
http://librarian.launchpad.net/7192169/DSCF1085.JPG
--
Feisty randomly fails to boot and BusyBox shell started
https://bugs.launchpad.net/bugs/103898
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Public bug reported:
My Feisty is up to date, but fails to boot randomly (one or two times every
twenty or so boot). I'll attach a picture later.
Edgy works fine with the same config. I think it's a problem with recognition
of my Adaptec 19160 SCSI controller. Please tell me how can I provide mo
Ok, but I think I've not enough information to create a new bug report,
so I asked here to tell me how to compile a detailed report for this
kind of issue.
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/103177
You received this bug notification because you are a membe
I've the same busybox problem, but with a SCSI system. Look at the picture
attached.
My Feisty (upgraded from Edgy) is up to date. The issue appears randomly.
SCSI subsystem: Adaptec 19160 + 2 x Fujitsu MAS 73GB, no Raid and no LVM
I'll try to give you a more detailed report if you tell me how to
My Feisty is up to date. I've the same BusyBox problem at boot up. Can
you tell me how to track the issue ? I don't have raid but I have a
Adaptec 19160 SCSI controller on which reside the root partition.
--
boot-time race condition initializing md
https://bugs.launchpad.net/bugs/75681
You receiv
39 matches
Mail list logo
