Adrian Bunk wrote:
>> Jeff, Auke, would something like this be acceptable? It makes it very
>> obvious in the driver table which entries are for the PCIE versions that
>> would be handled by the E1000E driver if it is enabled..
>
> I don't like it:
> We should aim at having exactly one driver for
Forward to netdev list.
--- Forwarded message (begin)
Subject: Typo in net/netfilter/xt_iprange.c (git tree)
From: Jiri Moravec <...>
Date: Fri, 01 Feb 2008 15:50:15 +0100
Function iprange_mt4 belong to IPv4 family - AF_INET. Right?
.name = "iprange",
.revision
Peter Teoh wrote:
> In include/linux/init.h, it is documented that all __xxxinitdata
> declaration must not have constant, as show below:
See: http://lkml.org/lkml/2008/1/26/182
There's a fairly major cleanup happening at the moment as you could see from
the mailing list archives for the past wee
Sam Ravnborg wrote:
> --- a/scripts/setlocalversion
> +++ b/scripts/setlocalversion
> @@ -45,3 +45,18 @@ if hgid=`hg id 2>/dev/null`; then
> # All done with mercurial
> exit
> fi
> +
> +# Check for svn and a svn repo.
> +if rev=`svn info 2>/dev/null | grep '^Revision' | awk '{print $NF}'` ; then
>
Sam Ravnborg wrote:
> The apm module were renamed to apm_32 during the merge of 32 and 64 bit
> x86 which is unfortunate.
> As apm is 32 bit specific we like to keep the _32 in the filename
> but the module should be named apm.
>
> Fix this in the Makefile.
> Reported by "A.E.Lawrence" <[EMAIL PRO
On Tuesday 12 February 2008, Greg KH wrote:
> On Tue, Feb 12, 2008 at 09:39:14PM +0100, Frans Pop wrote:
> > On Monday 11 February 2008, Frans Pop wrote:
> > > In general 2.6.25 if looking quite good on my desktop, but there's
> > > one important issue: the s
On Monday 11 February 2008, Frans Pop wrote:
> In general 2.6.25 if looking quite good on my desktop, but there's one
> important issue: the system no longer powers off after shutdown.
> This works fine with 2.6.24.
I was wrong :-(
I'd not really done any real wor under
On Wednesday 13 February 2008, Thomas Gleixner wrote:
> On Tue, 12 Feb 2008, Andrew Morton wrote:
> > On Sun, 10 Feb 2008 14:40:21 +0100 Frans Pop <[EMAIL PROTECTED]> wrote:
> > the hrtimer code is preparing an invalid ktime_t. Note that
> > clockevents_program_event
On Wednesday 13 February 2008, you wrote:
> On Tue, 12 Feb 2008 22:45:09 +0100 Frans Pop <[EMAIL PROTECTED]> wrote:
> > Symptom is that the system shuts down normally and completely, it just
> > does not power off.
>
> I've been struggling with an identically-manif
From: Frans Pop <[EMAIL PROTECTED]>
Allow to specify a custom revision for the generated .deb package
by exporting the environment variable KERNELDEBREVISION.
Signed-off-by: Frans Pop <[EMAIL PROTECTED]>
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index ba6b
On Tuesday 12 February 2008, Greg KH wrote:
> On Tue, Feb 12, 2008 at 09:39:14PM +0100, Frans Pop wrote:
> > On Monday 11 February 2008, Frans Pop wrote:
> > > In general 2.6.25 if looking quite good on my desktop, but there's
> > > one important issue: the s
From: Frans Pop <[EMAIL PROTECTED]>
Hook scripts in the default directory /etc/kernel are also
executed by packages created using make-kpkg (including official
Debian kernels). Allow to specify an alternative hook scripts
directory by exporting the environment variable KERNELDEBHOOK
On Wednesday 13 February 2008, Greg KH wrote:
> > So, just on the off chance, I applied the patch below and bingo, the
> > system powers off again. I doubt this will be the correct solution, but
> > just in case it is, here's my signed off. A comment why the double put
> > is needed would probably
On Wednesday 13 February 2008, Thomas Gleixner wrote:
> can you please apply the following patch ? I really should have
> thought about that, when I fixed the above one.
I still get the bug with this patch. At least I'm now certain it happens
during glibc compilation and that I can reproduce it.
On Thursday 14 February 2008, Thomas Gleixner wrote:
> futex_lock_pi is called with an absolute timeout, which is based on
> CLOCK_REALTIME. Nothing wrong with that, but the clockevents WARN_ON
> might trap over a false positive, when the expiry value is less than
> base->offset. This was intention
On Friday 15 February 2008, Greg KH wrote:
> I swear someone sent this patch in before. Can you try this one below,
> there seems to be an imbalance with kobject_get and _put.
I did remember seeing this patch before [1] and can confirm that it does
indeed fix the issue: with this patch applied t
Daniel Barkalow wrote:
> For some reason I can't see and don't know how to debug, in 2.6.23 on my
> server I don't get the vga console, but only get the dummy console.
Please check if this bug report matches the issue you are seeing:
http://bugzilla.kernel.org/show_bug.cgi?id=9310
Cheers,
FJP
--
Yesterday, after spending quite a few hours over the last days on bisecting
some serious regressions and finding workarounds for them, I thought I
could start using 2.6.25-rc2 as the new kernel for my desktop.
Unfortunately I found that I cannot because it would make my other main
activity - wo
On Sunday 17 February 2008, Daniel Barkalow wrote:
> On Sun, 17 Feb 2008, Frans Pop wrote:
> > Daniel Barkalow wrote:
> > > For some reason I can't see and don't know how to debug, in 2.6.23 on
> > > my server I don't get the vga console, but only get the
Joerg Schilling wrote:
> This fragment is much too short to allow to judge on possible reasons.
> There is a high probability that your problem is caused by the cdrecord
> fork called "wodim".
There is also the 100% certainty that this reply was from a known troll and
should just be ignored.
--
To
On Monday 18 February 2008, Mike Galbraith wrote:
> On Mon, 2008-02-18 at 09:46 +0100, Frans Pop wrote:
> > Joerg Schilling wrote:
> > > This fragment is much too short to allow to judge on possible
> > > reasons. There is a high probability that your problem is caused
Jeff Garzik wrote:
> Two x86-64 boxes here lock up here on 2.6.25-rc2, shortly after boot.
> One running Fedora 8 + X (GNOME) and one a headless file server.
> configs and lspci attached. Unable to capture any splatter so far.
Sounds like it may be http://lkml.org/lkml/2008/2/17/78.
Suggest you
On Sunday 17 February 2008, Adrian Bunk wrote:
> The real problem is that the kernel seems to lack functionality you
> require for doing some work.
Not sure how you reached that conclusion.
> Why does your work on the Debian Installer depend on VirtualBox and
> can't be done with what the kernel
On Sunday 17 February 2008, Arjan van de Ven wrote:
> On Sun, 17 Feb 2008 14:38:51 -0600 Paul Jackson <[EMAIL PROTECTED]> wrote:
> > Adrian wrote:
> > > So let's fix the problem (kernel lacks functionality)
> >
> > That's the problem as understood by Adrian.
> >
> > I hear another problem as well .
On Tuesday 19 February 2008, Adrian Bunk wrote:
> The "or any other emulator" is exactly where my question is directed at.
>
> Xen, KVM or even qemu come into my mind, but considering how loudly you
> complained about a temporary breakage for VirtualBox there must be a
> reason why your work on the
Karl Dahlke wrote:
> Meantime, I pulled the emails out of the headers and pasted them in.
> Hope that reasonably works.
Well, you're still breaking the thread by starting a new one.
Guess when you're implementing reply-to-all, you should also think about
implementing support for In-Reply-To: and
Kernel: vanilla 2.6.24 x86_64 SMP
Environment: Debian unstable
Processor: Intel(R) Pentium(R) D CPU 3.20GHz (dual core)
I've been running this kernel without problems since its release, but
yesterday evening I suddenly got the following error, and this afternoon it
was repeated (below). The syst
On Sunday 10 February 2008, Frans Pop wrote:
> I have no idea yet what triggers it and am unsure if I'll be able to
> reproduce.
I think I know at least _when_ it happens: during compilation of glibc.
This was almost certainly while compiling in the normal amd64 environment:
> P
I'm aware that devfs is being removed in 2.6.13, but this patch may still
interest maintainers of older versions.
I've debugged this problem using kernel version 2.6.8, but a check showed
this code is unchanged in 2.6.12. My system is Debian Sarge.
During boot using an initrd on a system having
(Resending as there were no replies on my first post mid December; issue
is still there with -rc6.)
This is the first time I've seen this error. Last time I used the printer
was with 2.6.24-rc3 and that time this error did not occur.
The error occurs when I start a print job, not when I turn the
On Sunday 06 January 2008, Eric W. Biederman wrote:
> Short of two programs coming in and simultaneously trying to claim
> the parallel port and there being not exclusion in ppdev.c I don't
> have a clue what could cause the reported error.
That could well be the root cause as the full log shows:
(Adding the kernel list back. Any reason you did not send the reply there?)
Sorry for the late reply: Christmas, New Year, the flue, etc.
On Friday 28 December 2007, Zhao Yakui wrote:
> On Mon, 2007-12-24 at 06:12 +0100, Frans Pop wrote:
> > During boot with v2.6.24-rc6-125-g5356
(Mail below was sent to me privately, forwarding to the lists.)
On Mon, 2008-01-07 at 00:48 +0100, Frans Pop wrote:
> (Adding the kernel list back. Any reason you did not send the reply
> there?)
>
> Sorry for the late reply: Christmas, New Year, the flue, etc.
> Thank you
Len Brown wrote:
>> > Well, yes, the warning is actually new as well. Previously your kernel
>> > just silently ignored 8 more mem resources than it does now it seems.
>> >
>> > Given that people are hitting these limits, it might make sense to just
>> > do away with the warning for 2.6.24 again w
Jeff Garzik wrote:
> libata disabling command queueing (aka NCQ) based on some hueristics for
> detection device brokenness that ultimately turned out to be broken.
>
> Remove the broken hueristic and turn NCQ back on for all the wrongfully
> maligned hard drives.
Yay!
--
To unsubscribe from
On Sunday 09 December 2007, Sam Ravnborg wrote:
> This is much better.
Thanks!
A few minor corrections maybe (nitpicks really).
> *** Unable to find the ncurses libraries
> *** or the required header files.
That first line is strangely short like this.
Move "or the" to the first line?
> ***
Alexander Rajula wrote:
> While overclocking an AMD Athlon X2 (2GHz) CPU /proc/cpuinfo reports the
> wrong CPU frequency. I am quite puzzled by this.
> Is this an error in the kernel, or is there something strange going on?
You may want to read some old threads on this list and check if that match
Dave Young wrote:
> I noticed the port number changed to 40 in 2.6.24-rc8, but it's not
> enough for me still.
Same here, though the extreme noise has gone.
>From /proc/ioports and dmesg it looks like I'm short by either 1, or 3 :-(
Cheers,
FJP
--
To unsubscribe from this list: send the line "uns
Andi Kleen wrote:
> My workstation running 2.6.24-rc8 just hung during shutdown with an
> endless (or rather I didn't wait more than a few minutes) loop of
>
> unregister_netdev: waiting for ppp-device to become free. Usage count = 1
Same as http://lkml.org/lkml/2008/1/20/27? See also follow-up t
Hi,
I'm not qualified to comment on the code, but here are some suggestions on
config option and comments.
Cheers,
FJP
Ryo Tsuruta wrote:
> +config DM_BAND
> + tristate "I/O band width control "
s/band width/bandwidth/
(it seems to be used correctly elsewhere, but you may want to double-che
I saw top occasionally displaying % CPU usage for a process. The
first few times it was amarokapp, this last time it was kontact.
Both applications were basically idle.
The "cc1" is a kernel compile (rc9 + CFS :-).
I cannot remember seeing this before, but as I also don't run top that
frequent
On Wednesday 03 October 2007, you wrote:
> Try to capture the i/o log with the following command:
> strace -o top.log top
Thanks for the suggestion.
> This will show for sure whether the kernel gives out incorrect data or
> top misinterprets them.
PID USER PR NI VIRT RES SHR S %CPU %ME
On Wednesday 03 October 2007, you wrote:
> On Wed, 3 Oct 2007, Ilpo Järvinen wrote:
> > On Wed, 3 Oct 2007, Frans Pop wrote:
> > > The only change is in 2 consecutive columns: "2911 502" -> "2912
> > > 500". Is processor usage calculated from
On Wednesday 03 October 2007, you wrote:
> On Wed, Oct 03, 2007 at 09:27:41PM +0200, Frans Pop wrote:
> > On Wednesday 03 October 2007, you wrote:
> > > On Wed, 3 Oct 2007, Ilpo Järvinen wrote:
> > > > On Wed, 3 Oct 2007, Frans Pop wrote:
> > > > >
On Friday 05 October 2007, Chuck Ebbert wrote:
> procfs: Don't read runtime twice when computing task's stime
>
> Current code reads p->se.sum_exec_runtime twice and goes through
> multiple type conversions to calculate stime. Read it once and
> skip some of the conversions.
>
> Signed-off-by: Chuc
t also again shows updates only once every minute. I really
wonder where all the other fluctuations for contact come from with the
alternative code.
It seems to me that this patch would be the best option for 2.6.23.
Tested-by: Frans Pop <[EMAIL PROTECTED]>
-
To unsubscribe from this list: s
On Thursday 20 December 2007, Alan Cox wrote:
> The kernel printk messages are sentences.
I'm afraid that I completely and utterly disagree. Kernel messages are _not_
sentences. The vast majority is not well-formed and does not contain any of
the elements that are required for a proper sentence.
On Wednesday 28 November 2007, Christian Borntraeger wrote:
> This seems to be related to the new network namespace code by Eric
> Biederman (CCed). Can you try the following (untested) patch? I also
> CCed Ursula and Peter as they know the ctc code better than me.
Yes, that fixes it. Boots fine n
Two typos in comments.
Cheers,
FJP
Michael Rubin wrote:
> + * The flush tree organizes the dirtied_when keys with the rb_tree. Any
> + * inodes with a duplicate dirtied_when value are link listed together.
> This + * link list is sorted by the inode's i_flushed_when. When both the
> + * dirited_w
Li Zefan wrote:
> Add a missing '.' in prink information.
> - printk(" no tick device\n");
> + printk(" no tick device.\n");
I wonder if that is correct. CodingStyle says:
Chapter 13: Printing kernel messages
[...]
Kernel messages do no
On Thursday 29 November 2007, Li Zefan wrote:
> Frans Pop wrote:
> > Li Zefan wrote:
> >> Add a missing '.' in prink information.
> >> - printk(" no tick device\n");
> >> + printk(" no tick devic
Paul Rolland wrote:
> Total of 2 processors activated (6919.15 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization [CPU#0 -> CPU#1]:
> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
> Marking TSC unstable
Martin Schwidefsky wrote:
> On Wed, 2007-11-28 at 11:27 +0100, Frans Pop wrote:
>> arch/s390/kernel/built-in.o: In function `cleanup_io_leave_insn':
>> diag.c:(.text+0xc29a): undefined reference to `preempt_schedule_irq'
>> make[2]: *** [.tmp_vmlinux1] Error 1
>
Stefano Brivio wrote:
> It looks like the jiffies counter sometimes jumps back and forth of some
> hundreds seconds in 2.6.24-rc3. I observed that this happens when I use
> the su(1) command, e.g.:
Can you please explain what exactly the problem is here?
Are you perhaps referring to the number be
(Dropped Rafael from CC)
On Sunday 25 November 2007, Bartlomiej Zolnierkiewicz wrote:
> So either something went very very wrong or the oops itself is incorrect.
>
> Please put BUG() before the put_cmd640_reg() above so the next time
> BUG happens we will know which one is it.
I've spent quite a
v2.6.24-rc3-19-g2ffbb83 fails very early in the boot procedure.
2.6.23 compiled with similar config boots fine.
System is running Debian unstable; kernel was compiled using gcc 4.1.2.
Cheers,
Frans Pop
Boot messages for 2.6.24
Command line for kernel: 'root=/dev
(resending as address for port list was incorrect)
v2.6.24-rc3-19-g2ffbb83 fails very early in the boot procedure.
2.6.23 compiled with similar config boots fine.
System is running Debian unstable; kernel was compiled using gcc 4.1.2.
Cheers,
Frans Pop
Boot messages for 2.6.24
Greg KH wrote:
> Based on an original article by Jon Corbet for lwn.net written October 1,
> 2003 and located at http://lwn.net/Articles/51437/
>
> Last updated November 27, 2008
^^^
Wow, that's impressive: both kobjects de-mystified and time travel made
possible!
$ git describe
v2.6.24-rc3-342-g8c27eba
arch/s390/kernel/built-in.o: In function `cleanup_io_leave_insn':
diag.c:(.text+0xc29a): undefined reference to `preempt_schedule_irq'
make[2]: *** [.tmp_vmlinux1] Error 1
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24-rc
On Wednesday 28 November 2007, Christian Borntraeger wrote:
> We have a patch for that in our repository.
> Martin will send that fix with the next bunch of fixes.
Thx.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
On Wednesday 28 November 2007, Christian Borntraeger wrote:
> > arch/s390/kernel/built-in.o: In function `cleanup_io_leave_insn':
> > diag.c:(.text+0xc29a): undefined reference to `preempt_schedule_irq'
> > make[2]: *** [.tmp_vmlinux1] Error 1
>
> We have a patch for that in our repository.
That f
James Kosin wrote:
> Anyone remember the patch / patches done for the 2.6 series that related
> to top reporting > 100% CPU usage?
Do you mean these perhaps?
- 73a2bcb0edb9ffb0b007b3546b430e2c6e415eee
- 9301899be75b464ef097f0b5af7af6d9bd8f68a7
Cheers,
FJP
--
To unsubscribe from this list: send th
After compiling v2.6.24-rc7-163-g1a1b285 (x86_64) yesterday I suddenly see this
error
repeatedly:
kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
kernel: Tx Queue <0>
kernel: TDH
kernel: TDT
kernel: next_to_use
kernel
Wow. That's fast! :-)
On Tuesday 15 January 2008, David Miller wrote:
> From: Frans Pop <[EMAIL PROTECTED]>
>
> > kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
>
> Does this make the problem go away?
I'm compiling a kernel with the patch now.
On Tuesday 15 January 2008, David Miller wrote:
> From: Frans Pop <[EMAIL PROTECTED]>
> > kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
>
> Does this make the problem go away?
Yes, it very much looks like that solves it.
I ran with the patch for 6 hours or
On Wednesday 16 January 2008, David Miller wrote:
> Ok, here is the patch I'll propose to fix this. The goal is to make
> it as simple as possible without regressing the thing we were trying
> to fix.
Looks good to me. Tested with -rc8.
Cheers,
FJP
--
To unsubscribe from this list: send the line
[EMAIL PROTECTED] wrote:
>8472457 Total 30486950 +259% 30342823 +258%
Hmmm. The table for previous versions looked a lot more impressive.
now:8472457 Total+22014493 +259% +21870366 +258%
V2 :7172678 Total+23314404 +325% -147590 -2%
(recalc
On Thursday 17 January 2008, David Miller wrote:
> From: "Brandeburg, Jesse" <[EMAIL PROTECTED]>
>
> > We spent Wednesday trying to reproduce (without the patch) these issues
> > without much luck, and have applied the patch cleanly and will continue
> > testing it. Given the simplicity of the cha
This is the first time I've seen this error. Last time I used the printer
was with 2.6.24-rc3 and that time this error did not occur.
System is Pentium D x86_64 kernel running Debian unstable.
Printer is a HP Photosmart P1100 connected via parallel port.
Not sure who should be CCed on this.
ppd
Glauber de Oliveira Costa wrote:
> What's left in processor_32.h and processor_64.h cannot be cleanly
> integrated. However, it's just a couple of definitions. They are moved
> to processor.h around ifdefs, and the original files are deleted. Note
> that there's much less headers included in the fi
On Tuesday 18 December 2007, Glauber de Oliveira Costa wrote:
> On Dec 18, 2007 6:54 PM, Frans Pop <[EMAIL PROTECTED]> wrote:
> > Glauber de Oliveira Costa wrote:
> > > What's left in processor_32.h and processor_64.h cannot be cleanly
> > > integrated. Howe
Jochen Friedrich wrote:
> +++ b/drivers/net/fec.c
> @@ -23,6 +23,9 @@
> *
> * Bug fixes and cleanup by Philippe De Muyter ([EMAIL PROTECTED])
> * Copyright (c) 2004-2006 Macq Electronique SA.
> + *
> + * This driver is now only used on ColdFire processors. Remove conditional
> + * Powerpc cod
On Friday 25 January 2008, Jochen Friedrich wrote:
> > Jochen Friedrich wrote:
> >> +++ b/drivers/net/fec.c
> >> @@ -23,6 +23,9 @@
> >> *
> >> * Bug fixes and cleanup by Philippe De Muyter ([EMAIL PROTECTED])
> >> * Copyright (c) 2004-2006 Macq Electronique SA.
> >> + *
> >> + * This driver i
> config BLK_DEV_IDE_PMAC
> - bool "Builtin PowerMac IDE support"
> + tristate "Builtin PowerMac IDE support"
This does not seem to make sense: if the option is now tristate, it is no
longer "Builtin", so probably s/Builtin // in the description.
Cheers,
FJP
--
To unsubscribe from th
On Saturday 26 January 2008, Bartlomiej Zolnierkiewicz wrote:
> On Saturday 26 January 2008, Jan Engelhardt wrote:
> > On Jan 26 2008 21:31, Frans Pop wrote:
> > >> config BLK_DEV_IDE_PMAC
> > >> - bool "Builtin PowerMac IDE support"
> >
Frans Pop wrote:
> The help should probably be a bit more verbose as this does not tell
> anybody much who has not already read the documentation.
>
> Maybe something like:
>
> This device-mapper target allows to define how the
> available bandwith of a storage device shoul
test/test type none (rw,bind)
/root/bindtest on /root/test type none (rw,bind)
Cheers,
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sunday 11 November 2007, Frans Pop wrote:
> I'd expected the last command to list "foo", but it shows an empty dir.
> Shouldn't it also show the original contents of test (as they were before
> the first bind mount)?
The problem is of course also that any changes
On Sunday 11 November 2007, Roland Kuhn wrote:
> This mounts the bindtest/ tree on test/ _without_ copying the mount
> points which are found on subtrees.
Right. I guess this is the key point that tripped me up.
> So, you see, test/test/test/a was (as it should) physically created
> in test/tes
On Sunday 11 November 2007, Jan Engelhardt wrote:
> >This mounts the bindtest/ tree on test/ _without_ copying the mount
> >points which are found on subtrees. This is necessary to avoid loops
> >in the filesystem (bind mounts are somewhat like hardlinks on
> >directories, just without the headache
s) by removing the
compat symlinks too early may mean less testing of kernels by people like me.
Cheers,
Frans Pop
P.S. The ARCH=x86 change would not have broken kernel-package as that could
be worked around using its cross-compilation options. And it currently looks
like the old options will be pre
Romano Giannetti wrote:
> This was what I did in my (in the end almost successful) bisecting when
> trying to find the mmc problem (see the thread named "2.6.24-rc1 eat my
> SD card"). This is true in theory, but it has some problem. The "this
> commit does not compile is the easiest and in man git
On Monday 12 November 2007, Sam Ravnborg wrote:
> This revised patchset does the followings things:
> o unify the i386 and x86_64 Kconfig files
> o introduce support for K64BIT to set CONFIG_64BIT on command line
> o introdue support for "make ARCH=x86"
> o degraded ARCH={i386,x86_64} to select bet
Andrey Borzenkov wrote:
> I have lost battery in 2.6.24-rc1. Without CONFIG_ACPI_PROCFS I have
> no /proc/acpi/battery and cannot test netlink interface because right now
> there is no consumer of this.
This is a known issue. Please see:
http://lkml.org/lkml/2007/10/22/110
Cheers,
Frans
Andrey Borzenkov wrote:
> I already have power_supply module, battery depends on it and it is
> autloaded. But I fail to see where I can get battery info in /sys
Ah, yes. I see what you mean now and I can confirm the same regression wrt
missing battery data in /proc for my laptop.
$ cat /proc/acp
Alexey Starikovskiy wrote:
> Andrey Borzenkov wrote:
>> is it in -rc1 or can you point me to the patch (I'd rather avoid having
>> to pull from different git trees). Thank you.
> No, it should be rc1.
>>
>> And what about ACPI_PROCFS case? It still needs attention I believe.
> As you can see, ther
atch.
With 'battery_allow_extract_string_from_integer.patch' all info in /proc is
back and I now also see the new files in /sys/class/power_supply.
The "OEM info" field (line 13 in BAT1/info) is empty, just as it was empty
in 2.6.23 too.
Tested-by: Frans Pop <[EMAIL PROTECTED]>
Ch
Bradley Smith wrote:
> +config I8K
> + tristate "Dell laptop support"
Shouldn't that be config DELL_I8K, or even DELL_INSPIRON_8K?
Cheers,
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
guration files, I decided
to not follow up.
Of course, not honoring 'all' is more obviously a bug than not honoring
'default' for existing interfaces.
I've added a comment to #8519.
Hope this helps,
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linu
I've tried
> reproducing the problem on my UML setup without any success. Let me
> try and grab an x86 box.
Any progress on this issue? I noticed that it's still there in current git.
If a better implementation is not expected any time soon, how about an ACK
on the reversio
On Monday 29 October 2007, Ingo Molnar wrote:
> * Christian Borntraeger <[EMAIL PROTECTED]> wrote:
> > > - return clock_t_to_cputime(utime);
> > > + p->prev_utime = max(p->prev_utime, clock_t_to_cputime(utime));
> > > + return p->prev_utime;
> > > }
> >
> > [...]
> >
> > I dont think it will work.
On Monday 29 October 2007, Balbir Singh wrote:
> We'll also need this additional patch (untested),
OK. Both patches together do the trick. Gave it a nice long test run and got
no more weirdness.
Tested-by: Frans Pop <[EMAIL PROTECTED]>
> but in the long run I think the app
Daniel Drake wrote:
> I have narrowed down the exact command submission which causes those
> nasty messages in dmesg. The function which submits this is named
> "brasero_medium_get_page_2A_write_speed_desc".
Just as an extra data point...
I've compiled the test program an ran it on my ICH7/Pentiu
Chris Holvenstot wrote:
> Since I try to be slightly useful and build as many of the "test" kernel
> images I can I end up rebuilding the VirtualBox kernel driver (open
> source) on an almost daily basis.
>
> I attempted to rebuild the driver today and got the following error
> messages running 2.
he comments in that report indicate that the issue is almost certainly
more related to the (relative?) speed of systems than to x86_64 as an
architecture.
Cheers,
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
don't have).
I also cannot find anything in /etc that could be responsible.
So I wonder what _is_ responsible for trying to load the ipmi modules on my
system and if that shouldn't be avoided.
My system is Debian testing running 2.6.23.
Cheers,
Frans Pop
00:00.0 Host bridge [0600]: In
Geert Uytterhoeven wrote:
> Euh, is these really necessary?
>
> At work I have no problems running depmod on an i386 system for ppc64
> modules after I installed module-init-tools 3.3-pre2 (from Debian).
That's right. I do depmod on i386 and amd64 for _all_ Debian architectures
without any probl
On Sunday 21 October 2007, Dave Jones wrote:
> On Sun, Oct 21, 2007 at 03:34:11PM +0200, Frans Pop wrote:
> > AFAICT from modules.pcimap, ipmi_si should only be loaded for PCI ID
> > [103c:121a] (which I don't have), or for devices with class c0700
> > (which I als
Jeff Chua wrote:
> Just pulled latest linux-2.6, and couldn't get ACPI to detect
> ACPI_BATTERY and ACPI_AC.
>
> It seems ACPI POWER_SUPPLY is still missing.
I had the same problem. It turns out you need to enable
drivers -> Power supply class support
(either built in or as module) to get ACPI
On Monday 22 October 2007, Alexey Starikovskiy wrote:
> Frans Pop wrote:
> > I must say that having these relatively top-level ACPI settings
> > depending on something that is relatively buried away is not very
> > intuitive! Especially not since at first glance you don'
1 - 100 of 133 matches
Mail list logo
