Processing commands for [EMAIL PROTECTED]:
> tags 379776 + upstream
Bug#379776: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
There were no tags set.
Tags added: upstream
> reassign 379776 linux-2.6
Bug#379776: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Bug reassigned from pa
severity 386821 normal
thanks
On Sun, Sep 10, 2006 at 01:53:15PM +0100, Pedro Celestino dos Reis Rodrigues
wrote:
> After about ten minutes of upload time the kacpid process starts to spend
> around
> 4% of the CPU time.
> The process activity is not permanent. Sometimes it is even zero.
Many o
Same as #360763
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Mon, 11 Sep 2006 02:35:16 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Duplicate
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen
Processing commands for [EMAIL PROTECTED]:
> reassign 334848 nvidia-graphics-drivers
Bug#334848: linux-image-2.6.12-1-686-smp: Installing new kernel breaks X window
system with nvidia drivers
Bug reassigned from package `linux-2.6' to `nvidia-graphics-drivers'.
>
End of message, stopping process
Processing commands for [EMAIL PROTECTED]:
> severity 386916 important
Bug#386916: linux-image-2.6.17-2-686: can't boot up
Severity set to `important' from `important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On 9/11/06, LI Daobing <[EMAIL PROTECTED]> wrote:
On 9/11/06, Steve Langasek <[EMAIL PROTECTED]> wrote:
> Yes, we definitely will need more info, since this kernel is of course
> working for many other users. For starters, we probably want the driver
> your disk normally uses, and the exact erro
Processing commands for [EMAIL PROTECTED]:
> tags 386916 moreinfo
Bug#386916: linux-image-2.6.17-2-686: can't boot up
There were no tags set.
Tags added: moreinfo
> severity 386916 important
Bug#386916: linux-image-2.6.17-2-686: can't boot up
Severity set to `important' from `grave'
> thanks
Sto
On 9/11/06, Steve Langasek <[EMAIL PROTECTED]> wrote:
Yes, we definitely will need more info, since this kernel is of course
working for many other users. For starters, we probably want the driver
your disk normally uses, and the exact error messages printed out at boot
time.
driver maybe is:
tags 386916 moreinfo
severity 386916 important
thanks
On Mon, Sep 11, 2006 at 09:46:07AM +0800, LI Daobing wrote:
> Package: linux-image-2.6.17-2-686
> Version: 2.6.17-8
> Severity: grave
> Justification: renders package unusable
> can't boot up. I stop at find root device, I think the kernel doe
Package: linux-image-2.6.17-2-686
Version: 2.6.17-8
Severity: grave
Justification: renders package unusable
can't boot up. I stop at find root device, I think the kernel does not
detect my disk. It works fine under 2.6.16.
If you need more information, please mail me.
Thanks
-- System Informa
On Fri, Sep 08, 2006 at 08:09:15AM +0200, Sven Luther wrote:
On Fri, Sep 08, 2006 at 01:05:57AM +0200, maximilian attems wrote:
On Thu, 07 Sep 2006, David Härdeman wrote:
> Package: initramfs-tools
> Version: 0.78
> Severity: minor
> Tags: patch
>
> The attached patch adds support for the "vid
Wake on lan seems to work again since 2.6.17,
i.e. I successfully tested:
linux-image-2.6.17-2-686_2.6.17-8_i386.deb
Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: kernel-image-2.6.8-i386
Severity: important
Tags: patch
See bug 384251.
This bug concerne sarge, the probleme is corrected in 2.6.17.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'unstable')
Architecture: i386 (i686
Package: linux-image-2.6.17-2-686
Version: 2.6.17-8
Is there a reason why the modules for active ISDN cards from AVM have
been removed from the binary package? I haven't found any information
regarding this in the changelog. Is this a temporary removal or will
these modules be removed permanently?
On Sun, 2006-09-10 at 09:22 +0200, Elie De Brauwer wrote:
> Yes I know ;-)
>
>
> Update: 2.6.16
>
> We're on the right way, since 2.6.16 a new EXPERIMANTAL device driver
> titled SysKonnect Yukon2 support is available which supports the chipset
> used by the onboard gigabit ethernet !
>
> CO
I'm confirming that I'm seeing the same thing, and I notice the
problem after
1) I've unpacked linux-source-2.6.17.tar.bz2 in /usr/src
2) make menuconfig/xconfig/whathaveyou
3) built a kernel using make-kpkg kernel_image
4) run make-kpkg clean
5) rerun make-kpkg kernel_image
Hope this helps...
T
Your message dated Sun, 10 Sep 2006 16:25:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386823: Add modul kqemu
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your respon
Package: linux-image-2.6.17-2-k7
Version: 2.6.17-8
Hello,
Could you maybe add the kernelmodul 'kqemu' into the current
linux-image? In my opinion, it were a good decision, because qemu is in
the repository and with that modul, it will run better.
Or maybe as a seperate package.
Patrick.
--
Package: linux-image-2.6.16-2-686
Version: 2.6.16-18
Severity: important
After about ten minutes of upload time the kacpid process starts to spend around
4% of the CPU time.
The process activity is not permanent. Sometimes it is even zero.
lsmod output is
Module Size Used by
ra
20 matches
Mail list logo
