From: Esben Nielsen <[EMAIL PROTECTED]>
Date: Tue, 6 Sep 2005 20:56:40 +0200 (METDST)
> Andrew and David: I CC'ed you guyes because you took care of it the last
> time :-)
Applied, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
/arcnet/arcnet.c 2005-06-25
> 20:42:46.0 +0200
> +++ linux-2.6.13-gentoo/drivers/net/arcnet/arcnet.c 2005-09-03
> 19:46:54.227846664 +0200
> @@ -597,7 +597,7 @@ static int arcnet_send_packet(struct sk_
> struct ArcProto *proto;
> int txbuf;
&g
Alan Cox wrote:
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
Hello,
I tried to build linux-2.6.13-mm1 with the attached configuration, and
it failed with:
drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
drivers/usb/serial/whiteheat.c:1433:
On Llu, 2005-09-05 at 14:17 +0600, Alexander E. Patrakov wrote:
> Hello,
>
> I tried to build linux-2.6.13-mm1 with the attached configuration, and
> it failed with:
>
> drivers/usb/serial/whiteheat.c: In function `rx_data_softint':
> drivers/usb/serial/whiteheat.c:143
On Tue, Aug 30, 2005 at 01:57:27AM +0200, Ricardo Galli wrote:
> 2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
> begining and the machines is automatically rebooted after a couple of
> minutes.
I've filed a bug at kernel bugzilla so your report won't be lost. See
htt
Greg KH wrote:
> On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
>
>>Linus Torvalds wrote:
>>
>>>There it is.
>>>
>>>The most painful part of 2.6.13 is likely to be the fact that we made x86
>>>use the generic PCI bus setup code for assigning unassigned resources.
>>>That uncove
Hi.
On Fri, 2005-09-02 at 01:15, Eric W. Biederman wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> writes:
>
> > On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
> >> Meelis Roos wrote:
> >> >
> >> > It's OK then - I'm not using any suspend and I had a problem that my
> >> > machine powered down
Nigel Cunningham <[EMAIL PROTECTED]> writes:
> On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
>> Meelis Roos wrote:
>> >
>> > It's OK then - I'm not using any suspend and I had a problem that my
>> > machine powered down instead of reboot. The patch that went into 2.6.13
>> > after rc7 fixed i
On Thu, 2005-09-01 at 22:32, Pierre Ossman wrote:
> Meelis Roos wrote:
> >
> > It's OK then - I'm not using any suspend and I had a problem that my
> > machine powered down instead of reboot. The patch that went into 2.6.13
> > after rc7 fixed it for me. So the current tree is OK for me and if it'
Meelis Roos wrote:
>
> It's OK then - I'm not using any suspend and I had a problem that my
> machine powered down instead of reboot. The patch that went into 2.6.13
> after rc7 fixed it for me. So the current tree is OK for me and if it's
> OK for you too after suspend2 changes then this case can
I've since found that in the suspend2 code, I was working around this
problem before by not calling the prepare method. I've just today
modified the Suspend code so that it calls prepare for all of the
powerdown methods and everything is working fine without reverting the
patch. I guess this is yo
Hi.
On Thu, 2005-09-01 at 16:24, Meelis Roos wrote:
> RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
> RD> I had to guess, I would bet the commit below is what broke you. I'm
> RD> including a patch that reverts it at the end of this email
>
> Nigel, have you tried re
Hi All,
An update of the uClinux (MMU-less) fixups against 2.6.13.
Strait forward merge of the current outstanding patchs from
2.6.12-uc0. A few updates and fixes, but not alot of change in
this one.
http://www.uclinux.org/pub/uClinux/uClinux-2.6.x/linux-2.6.13-uc0.patch.gz
Change log
RD> Well, there aren't many differences between 2.6.13-rc7 and 2.6.13. If
RD> I had to guess, I would bet the commit below is what broke you. I'm
RD> including a patch that reverts it at the end of this email
Nigel, have you tried reverting the patch Roland pointed out? It
probably helps you.
I
On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote:
> Linus Torvalds wrote:
> > There it is.
> >
> > The most painful part of 2.6.13 is likely to be the fact that we made x86
> > use the generic PCI bus setup code for assigning unassigned resources.
> > That uncovered rather a lot o
Hi,
the description of PCI_NAMES is conflicting with its default option (now
N/y/? instead of Y/n/?). Here is a small patch that should remove the
confusion in drivers/pci/Kconfig.
Regards,
Alexandre
Signed-off-by : Alexandre Buisse <[EMAIL PROTECTED]>
--- drivers/pci/Kconfig.old 2005-08-31
Linus Torvalds wrote:
> There it is.
>
> The most painful part of 2.6.13 is likely to be the fact that we made x86
> use the generic PCI bus setup code for assigning unassigned resources.
> That uncovered rather a lot of nasty small details, but should also mean
> that a lot of laptops in parti
This patch enables more new hardware.
ACKed-by: Kylene Hall <[EMAIL PROTECTED]>
Forwarded Message
From: Philipp Matthias Hahn <[EMAIL PROTECTED]>
To: Kylene Hall <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: [tpmdd-devel] [PATCH] linux-2.6.13/drivers/ch
On Maw, 2005-08-30 at 11:21 -0400, linux-os (Dick Johnson) wrote:
> we have been starting at 0x30001000. Now, with
> Linux-2.6.13, I see that PCI/Bus resources are
> being allocated on top of this RAM!!! This should
2.6.13 redoes the bus assignments which might have indeed made mem= d
Hello, more problems are being found with linux-2.6.13
Some imaging systems reserve large amounts of
contiguous DMA RAM (16 megabytes) by booting
with 'mem='. In the subject systems, we boot
with "mem=768m" which makes the first available
RAM at 768 * 1024 * 1024 = 0x300
On Tue, 30 Aug 2005, David Hollis wrote:
> On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> > El Tue, 30 Aug 2005 01:34:25 +0200,
> > Jesper Juhl <[EMAIL PROTECTED]> escribió:
> >
> > > I don't see why we should break a bunch of drivers by doing that.
> > > Much better, in my oppinion, t
On Tue, Aug 30, 2005 at 10:28:37AM -0400, David Hollis wrote:
> On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> > El Tue, 30 Aug 2005 01:34:25 +0200,
> > Jesper Juhl <[EMAIL PROTECTED]> escribió:
> >
> > > I don't see why we should break a bunch of drivers by doing that.
> > > Much bette
On Tue, 2005-08-30 at 01:55 +0200, Diego Calleja wrote:
> El Tue, 30 Aug 2005 01:34:25 +0200,
> Jesper Juhl <[EMAIL PROTECTED]> escribió:
>
> > I don't see why we should break a bunch of drivers by doing that.
> > Much better, in my oppinion, to fix the few remaining drivers still
> > using check_
Changes in "request_mem_region()" ("__request_region()")
now seem to force PCI/Bus alignment upon the requested region.
It appears as though somebody thought this would only used
to reserve address-space on a PCI/Bus.
Linux-2.6.12.5 and all known previous versions back to
linux-2.4.26 worked fi
Le Tuesday 30 August 2005 a 01:08, Stephane Wirtel ecrivait:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
> With a grep on the source code of the last release, I get this result.
>
> drivers/pnp/resource.c:255:
Yes. I did also report it (see http://lkml.org/lkml/2005/8/26/252)
cheers,
Masoud Sharbiani
Lee Revell wrote:
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
> El Tue, 30 Aug 2005 01:34:25 +0200,
> Jesper Juhl <[EMAIL PROTECTED]> escribió:
>
> > I don't see why we should break a bunch of drivers by doing that.
> > Much better, in my oppinion, to fix the few remaining drivers still
> > using check_reg
> There it is.
2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
begining and the machines is automatically rebooted after a couple of
minutes.
The on-screen messages finishes with a few "openpic" messages:
http://mnm.uib.es/gallir/tmp/linux-13-ppc.jpg
I used the same
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl <[EMAIL PROTECTED]> escribió:
> I don't see why we should break a bunch of drivers by doing that.
> Much better, in my oppinion, to fix the few remaining drivers still
> using check_region and *then* kill it. Even unmaintained drivers may
I'd usuall
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
[snip]
>
> /me wonders why check_region has not been killed, it has been
> deprecated for years; killing it would force developers to fix it
> and would help to identify unmaintained drivers...
I don't see why we should break a bunch of drivers
El Tue, 30 Aug 2005 01:14:17 +0200,
Stephane Wirtel <[EMAIL PROTECTED]> escribió:
> Is there a function to replace this deprecated function ?
request_region
> Why is it deprecated ?
>From http://lists.osdl.org/pipermail/kernel-janitors/2004-January/000346.html:
"The reason that check_region() i
On 8/30/05, Stephane Wirtel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
[snip]
>
> Is there a function to replace this deprecated function ?
>
Yes, you just call request_region() and check its
On Tue, 30 Aug 2005, Stephane Wirtel wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
> With a grep on the source code of the last release, I get this result.
>
> drivers/pnp/resource.c:255: if (__check_region
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
> Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
> dual P3 machine
> It works just fine when compiled UP.
> This bug did NOT exist on 2.6.13-rc6 version.
Did you discover this bug with 2.6.13-rc7 before 2.6.13 was re
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled UP.
This bug did NOT exist on 2.6.13-rc6 version.
Through a serial console I captured the following:
---
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
On Mon, 29 Aug 2005, Antonino A. Daplas wrote:
>
> Both, actually, with exactly the same patch. In the long changelog, both
> Steven and Paul are co-signees but only Paul's name appeared in the short
> changelog.
git only has one author field. That's not really technically fundamental
(git c
On Mon, 2005-08-29 at 22:25 +0800, Antonino A. Daplas wrote:
> Nigel Cunningham wrote:
> > Hi.
> >
> > On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> >> On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> >>
> >>> Paul Mackerras:
> >>> Remove race between con_open and con_close
> >>
Nigel Cunningham wrote:
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
Paul Mackerras:
Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl bac
> "Nigel" == Nigel Cunningham <[EMAIL PROTECTED]> writes:
Nigel> Hi. I have a couple of reports of powering off being
Nigel> broken between 2.6.13-rc7 and 2.6.13 :( (One my computer
Nigel> and one a Suspend2 user). I'll happily test patches.
Well, there aren't many differences be
On Fri, Aug 26, 2005 at 09:33:29PM -0700, Deepak Saxena wrote:
> On Aug 25 2005, at 16:04, Erik Mouw was caught saying:
> > On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
> > > I really wanted to release a 2.6.13, but there's been enough changes
> > > while we've been waiting for
Hi.
On Mon, 2005-08-29 at 22:25, Jörn Engel wrote:
> On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
> > On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> > > On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> > >
> > > >
> > > > Paul Mackerras:
> > > > Remove race be
On Mon, 29 August 2005 22:17:30 +1000, Nigel Cunningham wrote:
> On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> > On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
> >
> > >
> > > Paul Mackerras:
> > > Remove race between con_open and con_close
> >
> > Hey, I'm the first to report
Hi.
I have a couple of reports of powering off being broken between
2.6.13-rc7 and 2.6.13 :( (One my computer and one a Suspend2 user). I'll
happily test patches.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
-
To unsubscr
Hi.
On Mon, 2005-08-29 at 20:57, Steven Rostedt wrote:
> On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
>
> >
> > Paul Mackerras:
> > Remove race between con_open and con_close
>
> Hey, I'm the first to report this with the fix and Paul gets the credit?
> I guess I'll crawl back to
On Sun, 2005-08-28 at 17:17 -0700, Linus Torvalds wrote:
>
> Paul Mackerras:
> Remove race between con_open and con_close
Hey, I'm the first to report this with the fix and Paul gets the credit?
I guess I'll crawl back to my little world (RT) where they actually
appreciate me. :-(
;-)
-- St
On Mon, 29 Aug 2005, Jerome Pinot wrote:
>
> Using git in the linus tree:
> $ git-whatchanged v2.6.12..v2.6.13 --pretty=full
It's really much nicer to just do
git log --no-merges v2.6.12..v2.6.13
which gives you a much more readable result.
git-whatchanged is useful if you also want
On Mon, 29 Aug 2005, Jesper Juhl wrote:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
> be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
> the full 2.6.12 -> 2.6.13 ChangeLog up there?
Done.
(Well, it's going to take a while to mirror out).
That'
>On 8/29/05, Linus Torvalds <...> wrote:
>>
>> There it is.
>>
>http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
>be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
>the full 2.6.12 -> 2.6.13 ChangeLog up there?
Using git in the linus tree:
$ git-whatchange
On 8/29/05, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> There it is.
>
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.13 seems to
be the 2.6.13-rc7 -> 2.6.13 final ChangeLog. Any chance we could get
the full 2.6.12 -> 2.6.13 ChangeLog up there?
--
Jesper Juhl <[EMAIL PROTECTED]>
Do
There it is.
The most painful part of 2.6.13 is likely to be the fact that we made x86
use the generic PCI bus setup code for assigning unassigned resources.
That uncovered rather a lot of nasty small details, but should also mean
that a lot of laptops in particular should be able to discover
I hate responding to myself but it's necessary:
>RC7-GIT7 barfed on me after some 20 hours:
complete serial console message before it reset is on:
http://newsgate.newsserver.nl/kernel/
as is config-file.
Hardware: AMD64 running pure-64 debian ony tyan motherboard with opteron
250 cpu
>I Wrote:
>After 53 hours and 31 minutes it crashed.
>dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+05:31)
>reboot system boot 2.6.13-rc7 Wed Aug 24 09:51 (2+05:41)
>
>Prior to this kernel it had been running 2.6.12-mm1 without problems:
>reboot system boot
On Aug 25 2005, at 16:04, Erik Mouw was caught saying:
> On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
> > I really wanted to release a 2.6.13, but there's been enough changes
> > while we've been waiting for other issues to resolve that I think it's
> > best to do a -rc7 first
Richard Henderson wrote:
> Because I use "extern inline" in the proper way. That is, I have both
> inline and out-of-line versions of some routines.
Is there any reason not to just make the out-of-line version explicit?
i.e.:
/* in some .h file: */
static /*(always!)*/inline int
Hello,
It crashes for me right off the bat:
Here is the kernel output:
---
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.13-rc7-git1 root=/dev/hda3 ro console=ttyS0,115200n8
CONSOLE=/dev/ttyS0
[Linux-bzImage, setup=0x1200, size=0x1fe4fa]
savedefault
boot
Linux vers
Danny ter Haar <[EMAIL PROTECTED]> wrote:
>Of course it will probably reboot just after sending this message.
Me and my big mouth...
If there is a god he is making fun of me right now ;-)
After 53 hours and 31 minutes it crashed.
dth pts/1zaphod.dth.net Wed Aug 24 09:54 - crash (2+
& 200 megabitoutgoing network traffic and
sufficient storage to the scsi system.
Of course it will probably reboot just after sending this message.
If it stays up after 5 days of pounding it will get _my_ stamp of
aproval ;-)
--
Linux 2.6.13-rc7 ([EMAIL PROTECTED]) (gcc [can&#x
Sorry. Here's the start of the thread.
Tony
On Tue, 23 Aug 2005 22:08:13 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Antonino A. Daplas:
> intelfb/fbdev: Save info->flags in a local variable
> Sylvain Meyer:
> intelfb: Do not ioremap entire graphics aperture
One of these chan
On Thu, Aug 25, 2005 at 03:16:49PM -0700, Richard Henderson wrote:
> On Thu, Aug 25, 2005 at 08:07:55PM +0100, Al Viro wrote:
> > IMO that's a question to rth: why do we really need to block always_inline
> > on alpha?
>
> Because I use "extern inline" in the proper way. That is, I have both
> in
On Thu, Aug 25, 2005 at 08:07:55PM +0100, Al Viro wrote:
> IMO that's a question to rth: why do we really need to block always_inline
> on alpha?
Because I use "extern inline" in the proper way. That is, I have both
inline and out-of-line versions of some routines. These routines have
their addr
On Thu, Aug 25, 2005 at 11:27:32AM +0400, Alexey Dobriyan wrote:
> Mine is alpha-unknown-linux-gnu-gcc (GCC) 3.4.4 (Gentoo 3.4.4)
>
> > Which place triggers it in your build?
>
> net/ipv4/route.c:3152, call to rt_hash_lock_init().
>
> >From preprocessed source (reformatted):
> --
Sorry but could you re-explain me the problem. Tony, you've only
CC'ed me the end of the story.
Just a correction the options are video=intelfb:accel=0,hwcursor=0
with = and not :
Regards
Sylvain
Sebastian Kaergel a écrit:
On Fri, 26 Aug 2005 00:23:40 +0800
"Antonino A. Daplas" <[
Sebastian Kaergel wrote:
On Fri, 26 Aug 2005 00:23:40 +0800
"Antonino A. Daplas" <[EMAIL PROTECTED]> wrote:
Sebastian Kaergel wrote:
On Tue, 23 Aug 2005 22:08:13 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
Sylvain Meyer:
intelfb: Do not ioremap entire graphics aperture
Probably
On Fri, 26 Aug 2005 00:23:40 +0800
"Antonino A. Daplas" <[EMAIL PROTECTED]> wrote:
> Sebastian Kaergel wrote:
> > On Tue, 23 Aug 2005 22:08:13 -0700 (PDT)
> > Linus Torvalds <[EMAIL PROTECTED]> wrote:
> >
> >> Sylvain Meyer:
> >> intelfb: Do not ioremap entire graphics aperture
>
> Probably th
Sebastian Kaergel wrote:
On Tue, 23 Aug 2005 22:08:13 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
Antonino A. Daplas:
intelfb/fbdev: Save info->flags in a local variable
Sylvain Meyer:
intelfb: Do not ioremap entire graphics aperture
Probably this one. If vram is less than stole
On Tue, 23 Aug 2005 22:08:13 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Antonino A. Daplas:
> intelfb/fbdev: Save info->flags in a local variable
> Sylvain Meyer:
> intelfb: Do not ioremap entire graphics aperture
One of these changes broke intelfb. The same .config from 2.6.13-r
On Thu, 25 Aug 2005, Al Viro wrote:
> On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote:
> > I have been a little out of it for a while on the sun3 stuffs, I'll admit
> > (cursed day job), but I really, really intend to get recent 2.6 running
> > again. Knowing that the rest of m68k is a
On Thu, 25 Aug 2005, Al Viro wrote:
> On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote:
>
> > I have been a little out of it for a while on the sun3 stuffs, I'll admit
> > (cursed day job), but I really, really intend to get recent 2.6 running
> > again. Knowing that the rest of m68k
On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote:
> I have been a little out of it for a while on the sun3 stuffs, I'll admit
> (cursed day job), but I really, really intend to get recent 2.6 running
> again. Knowing that the rest of m68k is at least compiling is a good
> start point.
On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
> I really wanted to release a 2.6.13, but there's been enough changes
> while we've been waiting for other issues to resolve that I think it's
> best to do a -rc7 first.
There's something strange going on with either ACPI or cpufr
On Thu, 25 Aug 2005, Geert Uytterhoeven wrote:
> Can't you use the plain m68k toolchain? I always used a m68k-linux-gcc 3.3.3
> for my uClinux experiments.
>
> > sun3 is seriously broken and I doubt that we'll see any takers for testing
> > 2.6 on those anyway ;-)
Hey, I'm writing this on a sun
On Wed, 24 Aug 2005, Al Viro wrote:
> It does, no (build) regressions. BTW, tree is not far from allmodconfig
> buildable on a bunch of targets now - yesterday pile of fixes was about
> half of the set needed for that. Most of the remaining stuff is for
> m68k (and applies both to Linus' tree and
On Wed, Aug 24, 2005 at 10:38:59PM +0100, Al Viro wrote:
> On Thu, Aug 25, 2005 at 12:13:02AM +0400, Alexey Dobriyan wrote:
> > On Wed, Aug 24, 2005 at 08:15:44PM +0100, Al Viro wrote:
> > > Most of the remaining stuff is for
> > > m68k (and applies both to Linus' tree and m68k CVS); I'll send that
root:sleipner:~# modprobe hotkey
FATAL: Error inserting hotkey
(/lib/modules/2.6.13-rc7/kernel/drivers/acpi/hotkey.ko): No such device
Not that I care, but it at least loaded in -rc6 and created the
/proc/acpi/hotkey directory with its content.
When the revolution comes, the author of acpi-hotke
Hello,
On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
>
> Hullo.
>
> I really wanted to release a 2.6.13, but there's been enough changes
> while we've been waiting for other issues to resolve that I think it's
> best to do a -rc7 first.
>
> Most of the -rc7 changes are pret
On Thu, Aug 25, 2005 at 12:13:02AM +0400, Alexey Dobriyan wrote:
> On Wed, Aug 24, 2005 at 08:15:44PM +0100, Al Viro wrote:
> > Most of the remaining stuff is for
> > m68k (and applies both to Linus' tree and m68k CVS); I'll send that today
> > and if Geert ACKs them, we will be _very_ close to hav
On Thu, Aug 25, 2005 at 12:13:02AM +0400, Alexey Dobriyan wrote:
> > sh64: need kernel headers that would make glibc happy enough
> > to build libc headers for that puppy;
>
> binutils already compiled. Will drop a line. Or file a bug. :-\
By some miracle gcc is also compiled. As of now (
On Wed, Aug 24, 2005 at 08:15:44PM +0100, Al Viro wrote:
> Most of the remaining stuff is for
> m68k (and applies both to Linus' tree and m68k CVS); I'll send that today
> and if Geert ACKs them, we will be _very_ close to having 2.6.13 build
> out of the box on the following set:
> alpha,
Do I un
On Wed, Aug 24, 2005 at 11:43:51AM -0700, Paul Jackson wrote:
> Al Viro wrote:
> > ... breaks ppc64 since there we have node_to_cpumask() done as inlined
> > function, not a macro. So we get __first_cpu(&node_to_cpumask(...),...),
> > with obvious consequences.
>
> I sent a patch for this a few h
Al Viro wrote:
> ... breaks ppc64 since there we have node_to_cpumask() done as inlined
> function, not a macro. So we get __first_cpu(&node_to_cpumask(...),...),
> with obvious consequences.
I sent a patch for this a few hours ago, thanks to Paul Mackerras's report:
[PATCH 2.6.13-rc6] cpu_exc
On Wed, Aug 24, 2005 at 07:43:42AM +0100, Al Viro wrote:
> On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
>
> > cpu_exclusive sched domains on partial nodes temp fix
>
> ... breaks ppc64 since there we have node_to_cpumask() done as inlined
> function, not a macro. So we get _
On Tue, Aug 23, 2005 at 10:08:13PM -0700, Linus Torvalds wrote:
> cpu_exclusive sched domains on partial nodes temp fix
... breaks ppc64 since there we have node_to_cpumask() done as inlined
function, not a macro. So we get __first_cpu(&node_to_cpumask(...),...),
with obvious consequences.
Lo
Hullo.
I really wanted to release a 2.6.13, but there's been enough changes
while we've been waiting for other issues to resolve that I think it's
best to do a -rc7 first.
Most of the -rc7 changes are pretty trivial, either one-liners or
affecting some particular specific driver or unusual c
On Thursday 11 August 2005 11:38, Michael Krufky wrote:
>Gene Heskett wrote:
>>I can also report that teletext decoding has ceased to work
>>here. But I'm not sure what kernel version killed it. Currently
>>running 2.6.13-rc6. But my card is cx88 based, a pcHDTV-3000. But
>>attempting to switch
Gene Heskett wrote:
I can also report that teletext decoding has ceased to work
here. But I'm not sure what kernel version killed it. Currently
running 2.6.13-rc6. But my card is cx88 based, a pcHDTV-3000. But
attempting to switch it on/off doesn't seem to generate any output
indicating it f
Hello Michael!
On Thu, Aug 11, 2005 at 02:37:20PM +0200, [EMAIL PROTECTED] wrote:
> >I got the following OOPS from running "alevtd -F -d -v /dev/vbi0" with
> >my Siemens-DVB-C on a Dual-i686-600. I'm able to reproduce this even
> >running a 2.6.12-rc6 without the nvidia module tainting the kernel.
On Thursday 11 August 2005 08:37, [EMAIL PROTECTED] wrote:
>Hello Philipp,
>
>> I got the following OOPS from running "alevtd -F -d -v /dev/vbi0"
>> with my Siemens-DVB-C on a Dual-i686-600. I'm able to reproduce
>> this even running a 2.6.12-rc6 without the nvidia module tainting
>> the kernel.
>
Hello Philipp,
I got the following OOPS from running "alevtd -F -d -v /dev/vbi0" with
my Siemens-DVB-C on a Dual-i686-600. I'm able to reproduce this even
running a 2.6.12-rc6 without the nvidia module tainting the kernel.
So you're using the analog tuner of the card to watch analog cable tv a
On Thu, Aug 11, 2005 Philipp Matthias Hahn wrote:
> PS: MAINTAINTER lists http://linuxtv.org/developer/dvb.xml which is
> dead.
Thanks for reporting.
---
Fix DVB URL.
Signed-off-by: Johannes Stezenbach <[EMAIL PROTECTED]>
Index: linux-2.6.13-rc6
Hello!
On Sun, Aug 07, 2005 at 11:47:53AM -0700, Linus Torvalds wrote:
> Apart from some reverts and the aic7xxx performance regression fix,
> there's arm and ppc updates, and some PCI resource allocation updates that
> hopefully will reduce the number of machines (especially laptopns) that
> have
Hello!
On Sun, Aug 07, 2005 at 11:47:53AM -0700, Linus Torvalds wrote:
> James and gang found the aic7xxx slowdown that happened after 2.6.12, and
> we'd like to get particular testing that it's fixed, so if you have a
> relevant machine, please do test this.
I just tried 2.6.13-rc6 after my la
Hi James,
Dropped back to 2.6.11.1 and it hung again. I was able to get the
drive back by power cycling it and then doing the scsiadd to drop and
re-add the drive. I then used the bacula 'btape' tool to run some
tests. It seems to be just fine with regular files, but when it hit
EOM, all hell
James> Well, I suspect the tape is hanging the bus, from which no card
James> can recover.
Blech, not going to be fun to fix this sucker.
James> Just to test this, can you try sending a bus reset with sgutils (from
James> the debain package sg3-utils):
James> sg_reset -b /dev/sg3
James> Then r
On Wed, 2005-08-10 at 11:28 -0400, John Stoffel wrote:
> Is there any more info I can provide here for you? dmesg output?
> Here's the latest output from dmesg with the lockup of the drive,
> which takes a power cycle to clear now.
Well, I suspect the tape is hanging the bus, from which no card c
Hi James,
As a test, I dropped back to 2.6.12.1 and the drive hung again last
night while trying to do backups, so I suspect that I might have
controller or tape drive problems of some sort. I'll also try to go
back to 2.6.12-rc6 as well and see how that works out.
My next step is to try and ge
On Tue, 2005-08-09 at 16:12 -0400, John Stoffel wrote:
> Thank you for looking into this with me, I really appreciate it. I'm
> kinda stumped why this suddenly started happening, but it could be
> hardware related of course...
Well ... there's something going on that your posted dmesg's don't see
On Tue, 9 Aug 2005, Bodo Eggert wrote:
> On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
> > On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> > > The wrong values are constant across reboots (see my first mail), and I
> > > have a CRT.
> > >
> > > Can you tell me where the timing values
On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
> On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> > The wrong values are constant across reboots (see my first mail), and I
> > have a CRT.
> >
> > Can you tell me where the timing values are read?
>
> radeon_write_mode() programs the mo
> "James" == James Bottomley <[EMAIL PROTECTED]> writes:
Thank you for looking into this with me, I really appreciate it. I'm
kinda stumped why this suddenly started happening, but it could be
hardware related of course...
James> So basically the problem is on scsi1 with the tape device, whi
On Tue, 2005-08-09 at 15:35 -0400, John Stoffel wrote:
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: COMPAQ Model: HC01841729 Rev: 3208
> Type: Direct-AccessANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: COMPAQ
1 - 100 of 196 matches
Mail list logo
