This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen
the bug, click on the current status, under the Status column, and
change the status back
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
is bug https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/107807 a duplicate?
--
3c59x broken on reboot
https://bugs.launchpad.net/bugs/78611
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Well, some days ago I changed the state from Unconfirmed to Confirmed
before reading the rules, so I reverted the change. Sorry.
After stating that the problem occurs exactly on my computer, I tought
that the bug state could be changed to Confirmed, but that change can
only be done by the team.
S
Don't change a bug from Confirmed => Unconfirmed without stating a good
reason.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Confirmed
--
3c59x broken on reboot
https://bugs.launchpad.net/bugs/78611
You received this bug notification because you are a member of Ubunt
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed => Unconfirmed
--
3c59x broken on reboot
https://bugs.launchpad.net/bugs/78611
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
I have installed Feisty final and networking doesn't work properly.
After a while, it stops working and I need to reboot. I've found on
syslog the following messages:
Apr 21 00:02:29 micasa kernel: [ 3848.444000] NETDEV WATCHDOG: eth1: transmit
timed out
Apr 21 00:02:29 micasa kernel: [ 3848.444
Removing milestone. WIll not be fixed for release. Perhaps in an update
though.
** Changed in: linux-source-2.6.20 (Ubuntu)
Target: ubuntu-7.04 => None
--
3c59x broken on reboot
https://bugs.launchpad.net/bugs/78611
You received this bug notification because you are a member of Ubuntu
Bug
More than likely 3c59x or yenta isn't playing nicely with shared
interrupts. You can probably work around this by booting with the
irqpoll kernel command line option.
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Ben Collins => Ubuntu Kernel Team
Status: Needs Info => Confirmed
Is there any other info needed here? Perhaps this bug should be renamed
to something regarding a spurious IRQ on reboot on a Dell C600?
--
3c59x broken on reboot
https://launchpad.net/bugs/78611
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
The problem appears to be here:
[9.016000] irq 11: nobody cared (try booting with the "irqpoll" option)
...
[9.016000] Disabling IRQ #11
It looks like it effects both yenta and 3c59x on my system but it's a
more generic problem than that?
--
3c59x broken on reboot
https://launchpad.net/b
Based on the attachments I just uploaded I think that yenta not being
detected isn't the problem exactly. It's been pretty consistent,
though, that it works when cold-booted but not when rebooted.
** Summary changed:
- yenta sometimes not detected
+ 3c59x broken on reboot
--
3c59x broken on re
12 matches
Mail list logo
