On Sat, Aug 14, 2004 at 07:37:27PM -0600, dann frazier wrote:
On Sat, Aug 14, 2004 at 12:28:59PM -0600, dann frazier wrote:
On Fri, Aug 13, 2004 at 03:08:45PM +0100, Matthew Wilcox wrote:
I think you're mistaken. The known bug in the DV scsi core was fixed
9 weeks ago (according to
On Thu, Aug 19, 2004 at 09:40:47PM -0600, dann frazier wrote:
James took a look at my test box, and has submitted[1] a fix upstream.
So, this means we no longer need drivers-scsi-sym53c8xx_revert.dpatch.
I know that the proper way to update a patch in kernel-source is to add
another patch -
On Fri, Aug 20, 2004 at 07:25:06AM +0200, Christoph Hellwig wrote:
On Thu, Aug 19, 2004 at 09:40:47PM -0600, dann frazier wrote:
James took a look at my test box, and has submitted[1] a fix upstream
On Fri, Aug 20, 2004 at 02:43:46AM +0300, Shaul Karl wrote:
On Wed, Aug 18, 2004 at 12:16:04AM +0200, Christoph Hellwig wrote:
On Wed, Aug 18, 2004 at 01:13:08AM +0300, Shaul Karl wrote:
On Tue, Aug 17, 2004 at 04:02:32PM +0200, Christoph Hellwig wrote:
On Tue, Aug 17, 2004 at 02:17:11PM
On Thu, Aug 19, 2004 at 10:02:13PM -0400, Debian Installer wrote:
Rejected: kernel-image-2.4-586tsc_2.4.26-6_i386.deb: old version (2.4.27-1)
in unstable = new version (2.4.26-6) targeted at unstable.
Rejected: kernel-image-2.4-686_2.4.26-6_i386.deb: old version (2.4.27-1) in
unstable =
* Sven Luther wrote:
Who uploaded 2.4.27 packages to unstable forgeting to rename them to
2.4.27 ones ?
Nobody... these are dummy packages which depend on the latest 2.4
kernel packages available, and don't have the exact kernel version in
their package name.
Norbert
Package: kernel-image-2.6.8-1-k7
Severity: normal
Hi!
I have a NFORCE2 based Athlon board installed and can't use the Debian -k7
Kernels since 2.6.7 because I get a lockup during boot:
hda: dma_timer_expiry: dma status 0x64
hda: DMA interrupt recovery
hda: lost interrupt
I have a vanilla
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: normal
On a later boot it looks like my / on raid5 is rebuilding, I'm not sure if
it was during this boot also.
Is this an oops and scheduling while atomic debug?
NET: Registered protocol family 10
Disabled Privacy Extensions on
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: important
I'm trying to upgrade this system from a custom 2.6.3+patches kernel and I
ran into this problem.
Let me know if you need any more info.
EXT3 FS on md1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-1
Severity: minor
/lib/modules/2.6.8-powerpc/ contains a invalid symbolic link source to
/home/hch/kernel-patch-powerpc-2.6.8/tmp/kernel-source-2.6.8-powerpc
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990,
Sven Luther wrote:
On Fri, Aug 20, 2004 at 12:07:57PM +0200, Eugen Dedu wrote:
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-1
Severity: minor
/lib/modules/2.6.8-powerpc/ contains a invalid symbolic link source to
/home/hch/kernel-patch-powerpc-2.6.8/tmp/kernel-source-2.6.8-powerpc
This is
On Fri, Aug 20, 2004 at 12:07:57PM +0200, Eugen Dedu wrote:
Package: kernel-image-2.6.8-powerpc
Version: 2.6.8-1
Severity: minor
/lib/modules/2.6.8-powerpc/ contains a invalid symbolic link source to
/home/hch/kernel-patch-powerpc-2.6.8/tmp/kernel-source-2.6.8-powerpc
This is a
Processing commands for [EMAIL PROTECTED]:
reassign 266564 kernel
Bug#266564: two network cards problem
Bug reassigned from package `hotplug' to `kernel'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Processing commands for [EMAIL PROTECTED]:
reassign 259031 kernel
Bug#259031: ioctl FBIOGET_CON2FBMAP: Invalid argument on
CONFIG_FRAMEBUFFER_CONSOLE=m kernel
Bug reassigned from package `jfbterm' to `kernel'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: normal
With an IBM T41p, I ran into this problem. I was trying to get the
machine to sleep unsuccessfully with:
echo mem /sys/power/state
several times, but the machine was unable to go to sleep (see next bug
report). Eventually,
Package: kernel-image-2.6.7-1-686
Version: 2.6.7-2
Severity: normal
Attempting to put an IBM T41p to sleep does not work. The following
chunk of kernel log shows why:
Aug 20 03:10:09 localhost kernel: e1000: eth0: e1000_watchdog: NIC Link
is Up 100 Mbps Full D
uplex
Aug 20 03:10:12 localhost
Package: kernel
Version: 2.6.8-1-amd64
On unstable, pure64.
Upon boot, the hardware is recognised, wether
- the 10/100 LAN, driver forcedeth
- the 1000 LAN, driver e1000
Through DHCP the network is correctly setup. The after a variable, though
short time (from 30 sec to 3 min) the
* Christoph Hellwig ([EMAIL PROTECTED]) wrote:
On Thu, Aug 19, 2004 at 06:37:13PM -0400, Bharath Ramesh wrote:
I have 2.6.7 kernel on my Compaq laptop. I compiled the ndiswrapper
downloading from sourcforge. But whenever I try to run ifup on my device
I get a Kernel Panic. I am attaching
I know, this is upstream problem, but drm (especialy most interested for me
radeon.o) module is quite obsolete and ususable in my case. I use omnibook
laptop and only with quite new radeon.o ( 1.9) module works suspending
(standard apm option). Ok, you can say use 2.6.* but in 2.6 suspending
On Fri, Aug 20, 2004 at 01:53:55PM -0500, Manoj Srivastava wrote:
On Fri, 20 Aug 2004 13:39:54 +0200, Eugen Dedu
[EMAIL PROTECTED] said:
Sven Luther wrote:
On Fri, Aug 20, 2004 at 12:07:57PM +0200, Eugen Dedu wrote:
Package: kernel-image-2.6.8-powerpc Version: 2.6.8-1 Severity:
minor
On Fri, 20 Aug 2004 08:40:26 +0200, Philipp Kolmann wrote:
Package: kernel-image-2.6.8-1-k7
Severity: normal
Hi!
I have a NFORCE2 based Athlon board installed and can't use the Debian -k7
Kernels since 2.6.7 because I get a lockup during boot:
hda: dma_timer_expiry: dma status 0x64
Hi,
Sorry for the premature bug report, but it looks like the problem was
caused by a 32-bit PCI SCSI card in a 64-bit slot.
I'll leave it to your discretion on closing these bugs.
Mike
dann frazier wrote:
We need to come to an agreement about which kernel-source we will ship
for sarge. According to http://wiki.debian.net/index.cgi?DebianKernel,
everyone w/ 2.4.26 has 2.4.27 except for powerpc (sparc is building).
2.4.26 has had more testing time - its used in d-i RC1.
On Fri, Aug 20, 2004 at 10:20:17AM +0900, Horms wrote:
tags 266882 + woody security
Security Team, what is going on with respect to updating 2.4.18 in
woody? There are numerous CAN entries outstanding.
Joey has been working on it, and I have sent him what patches I had
been able to collect.
* Jan-Jaap van der Heijden wrote:
With a stock 2.6.6-1-generic kernel it crashes as soon as it
initilizes the SCSI controller.
Can you please try the 2.6.7 packages, and report if they fix your
problem (I suppose so)?
http://people.debian.org/~nobse/kernel-image-2.6.7-alpha/
2.6.7 doesn't lock up
I had an up-to-date installation of Debian unstable
running the 2.4.26 kernel with reiserfs 3.6 on a
Maxtor 6Y080L0 IDE drive, PIIX4 chipset (Dell OptiPlex
GX1).
I decided to give a try to the 2.6.8 kernel but it
hung displaying the NVIDIA logo. After a few tries and
hard reboots I found that the
On Fri, Aug 20, 2004 at 02:29:50PM -0700, Mike Fedyk wrote:
Hi,
Sorry for the premature bug report, but it looks like the problem was
caused by a 32-bit PCI SCSI card in a 64-bit slot.
32-bit PCI cards should work without problems in 64-bit slots, though.
--
Next the statesmen will invent
Matthew Wilcox wrote:
On Fri, Aug 20, 2004 at 02:29:50PM -0700, Mike Fedyk wrote:
Hi,
Sorry for the premature bug report, but it looks like the problem was
caused by a 32-bit PCI SCSI card in a 64-bit slot.
32-bit PCI cards should work without problems in 64-bit slots, though.
That's what
28 matches
Mail list logo
