Package: linux-image-2.6.18-4-k7
Version: 2.6.18.dfsg.1-12
In the past I have usually compiled my own kernel, mainly out of
interest. However, I don't really have time for that anymore, and
would like to switch to a precompiled kernel.
My PC has an Adaptec 29160N with a single hard disk attached
Hi Andi,
On Tue, Apr 03, 2007 at 12:37:09AM +0200, Andi Kleen wrote:
> On Tuesday 03 April 2007 00:29:16 dann frazier wrote:
> > hey Andi,
> > Debian is looking at patching our kernel to disable the hw iommu on
> > nvidia chipsets for the data corruption bug that's been discussed on
> > lkml[1].
On Tue, Apr 03, 2007 at 12:37:09AM +0200, Andi Kleen wrote:
> On Tuesday 03 April 2007 00:29:16 dann frazier wrote:
> > hey Andi,
> > Debian is looking at patching our kernel to disable the hw iommu on
> > nvidia chipsets for the data corruption bug that's been discussed on
> > lkml[1].
>
> It w
On Tuesday 03 April 2007 00:29:16 dann frazier wrote:
> hey Andi,
> Debian is looking at patching our kernel to disable the hw iommu on
> nvidia chipsets for the data corruption bug that's been discussed on
> lkml[1].
It would be better if you waited until the official solution. The
hardware deb
hey Andi,
Debian is looking at patching our kernel to disable the hw iommu on
nvidia chipsets for the data corruption bug that's been discussed on
lkml[1]. As far as I can tell there isn't an upstream solution yet, but
Steve Langasek has proposed the following patch which seems to work
for one of
> From: Olivier Berger
> Newsgroups: gmane.linux.debian.devel.kernel
> Subject: Bug#417333: FYI, may be have similar problem on another type of HW
> Date: Mon, 02 Apr 2007 13:35:28 +0200
>
> Hi.
>
> FYI, I entered a report (#417333) for a problem which show traces
> similar to that one...
Well, i
On Monday 02 April 2007 13:41, maximilian attems wrote:
> On Mon, Apr 02, 2007 at 01:25:19PM +0200, Jan Wagner wrote:
> > On Monday 02 April 2007 12:54, you wrote:
> > > On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote:
> > > > "rm /initrd.img /vmlinuz" fixed it for me, but it seems no ge
On Mon, Apr 02, 2007 at 01:25:19PM +0200, Jan Wagner wrote:
> On Monday 02 April 2007 12:54, you wrote:
> > On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote:
> > > "rm /initrd.img /vmlinuz" fixed it for me, but it seems no general
> > > solution.
> >
> > never saw that error, please try t
Hi.
FYI, I entered a report (#417333) for a problem which show traces
similar to that one...
I'm not sure though it's solved in latest kernel version.
Hope this helps,
Best regards,
--
Olivier BERGER <[EMAIL PROTECTED]>
Ingénieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-I
Processing commands for [EMAIL PROTECTED]:
> submitter 417333 [EMAIL PROTECTED]
Bug#417333: linux-image-2.6.18-4-686: kernel panic in tcp_tso_segment on Dell
PE650
Changed Bug submitter from [EMAIL PROTECTED] to [EMAIL PROTECTED]
> quit
Stopping processing here.
Please contact me if you need as
On Monday 02 April 2007 12:54, you wrote:
> On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote:
> > "rm /initrd.img /vmlinuz" fixed it for me, but it seems no general
> > solution.
>
> never saw that error, please try to reprduce:
> apt-get --reinstall install linux-image-2.6.18-4-686
As w
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Severity: important
On a Dell PowerEdge 650 server, I got kernel panics with testing kernel
2.6.18.dfsg.1-11.
I copied the output displayed on the console, which gives something like this :
[<...>] dst_output
[<...>] ip_queue
Package: linux-2.6
Severity: important
UTF-8 is the default charset since Debian Etch. The default charset of
kernel's vfat filesystem is ISO-8859-1. Therefore, when vfat or ntfs
filesystem is mounted, kernel assumes that system's charset is
ISO-8859-1 if not told otherwise. Wouldn't UTF-8 be bett
On Mon, Apr 02, 2007 at 10:58:56AM +0200, Jan Wagner wrote:
> # LANG=C aptitude upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading extended state information
> Initializing package states... Done
> Reading task descriptions... Done
> Building tag database... Done
>
The previous package version was:
2.6.18.dfsg.1-11
With kind regards, Jan.
--
Never write mail to <[EMAIL PROTECTED]>, you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GIT d-- s+: a- C+++ UL P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G
On Mon, Apr 02, 2007 at 02:15:55AM -0700, Steve Langasek wrote:
> # Automatically generated email from bts, devscripts version 2.10.1
> severity 417278 important
> tags 417278 unreproducible
I had the same problem here, when updating some of our machines this
morning (all with the -k7 flavor). Str
On Sun, Apr 01, 2007 at 11:51:17PM +, Oleg Verych wrote:
> 01-04-2007, maximilian attems:
>
> > so next step would be to upload 2.6.20 into unstable.
> > announcing upload for tuesday.
> > please tell if you have some patches needing to go into.
>
> 2.6.20.5 is planned on the same day:
>
> |
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.1
> severity 417278 important
Bug#417278: Failed to symbolic-link boot/initrd.img-2.6.18-4-686 to initrd.img.
Severity set to `important' from `serious'
> tags 417278 unreproducible
Bug#
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Severity: serious
--- Please enter the report below this line. ---
Latest kernel package does not install correctly:
# LANG=C aptitude upgrade
Reading package lists... Done
Building dependency tree... Done
Reading extended state inform
19 matches
Mail list logo
