Forwarding this:
https://groups.google.com/group/open-iscsi/browse_thread/thread/7b44b4b57f01eb70?hl=en#
Since I'm not sure how long it takes google groups to update, i'll go
ahead and paste the patch here as well below.
If you apply the first patch from the above link, the second patch below
Processing commands for cont...@bugs.debian.org:
> tags 691122 + pending
Bug #691122 [src:linux] Please add LVDS patch for the Zotac ZBOX SD ID13
Ignoring request to alter tags of bug #691122 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistan
Processing commands for cont...@bugs.debian.org:
> tags 690956 + pending
Bug #690956 [src:linux] linux-image-3.2.0-3-686-pae: e1000 vlan not working
Ignoring request to alter tags of bug #690956 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assis
Processing commands for cont...@bugs.debian.org:
> tags 689159 + pending
Bug #689159 [src:linux] Please add 8021q vlan kernel support for d-i
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
689159: http://bugs.debian.org/cgi-bin/bugreport.cgi
Processing commands for cont...@bugs.debian.org:
> # See
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/tags/v3.2.33
> tags 691122 fixed-upstream
Bug #691122 [src:linux] Please add LVDS patch for the Zotac ZBOX SD ID13
Added tag(s) fixed-upstream.
> thanks
S
Processing commands for cont...@bugs.debian.org:
> affects 689159 + debian-installer
Bug #689159 [src:linux] Please add 8021q vlan kernel support for d-i
Added indication that 689159 affects debian-installer
> --
Stopping processing here.
Please contact me if you need assistance.
--
689159: http
On Tue, Oct 30, 2012 at 04:40:00PM -0700, Jonathan Nieder wrote:
> Luis Mochan wrote:
>
> > I guess you want this is the relevant output of grep:
> > /etc/initramfs-tools/modules:uvesafb
> > /etc/modprobe.d/uvesafb.conf:options uvesafb mode_option=1280x1024-32
> > scroll=ywrap
>
> Actual
Janne Boman wrote:
> ouput attached.
Thanks.
Can you reproduce this using nouveau instead of nvidia? (Testing this
would require disabling uvesafb temporarily.)
If it works with nouveau, we can pass this on to the maintainers of
the nvidia proprietary driver. If it fails with nouveau, too, th
Hi,
ouput attached.
On Wed, Oct 31, 2012 at 8:54 PM, Jonathan Nieder wrote:
> reassign 691902 src:linux 3.2.23-1
> quit
>
> Hi Janne,
>
> Janne Boman wrote:
>
>> Selecting "Shutdown" from Gnome, issuing "shutdown -h now", "poweroff"
>> or "halt" from command line all result in the same behavior:
Processing commands for cont...@bugs.debian.org:
> reassign 691902 src:linux 3.2.23-1
Bug #691902 [linux-image-3.2.0-3-amd64] Unable to shutdown Debian Wheezy via
normal means
Bug reassigned from package 'linux-image-3.2.0-3-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #
reassign 691902 src:linux 3.2.23-1
quit
Hi Janne,
Janne Boman wrote:
> Selecting "Shutdown" from Gnome, issuing "shutdown -h now", "poweroff"
> or "halt" from command line all result in the same behavior: shutdown
> followed by a restart.
> The only way to shutdown my system is to issue "halt -p
From: Ben Hutchings
Date: Sun, 21 Oct 2012 19:23:52 +0100
Since commit c7f404b ('vfs: new superblock methods to override
/proc/*/mount{s,info}'), nfs_path() is used to generate the mounted
device name reported back to userland.
nfs_path() always generates a trailing slash when the given dentry i
On Sun, 2012-10-21 at 17:01 -0700, Jonathan Nieder wrote:
> (cc-ing Laurent in case he wants to test. Laurent, a "git am"-ready
> patch is at [1])
> Ben Hutchings wrote:
>
> > Since commit c7f404b ('vfs: new superblock methods to override
> > /proc/*/mount{s,info}'), nfs_path() is used to genera
On Wed, 2012-10-31 at 12:15 +0400, jaakov jaakov wrote:
> Thank you for a fast reply.
>
> > Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
> Attached.
[...]
This shows some warnings about a USB 3 device, and failure to recognise
the sound device configuration. I wouldn'
On Wed, 2012-10-31 at 12:15 +0400, jaakov jaakov wrote:
> Thank you for a fast reply.
>
> > Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
> Attached.
>
> > 'grave' would mean the package is broken for most users, which it isn't.
>
> The official description of grave fr
On Wed, 2012-10-31 at 09:19 +0200, Janne Boman wrote:
> Package: linux-image-3.2.0-3-amd64
> Severity: Important
>
> Dear maintainters,
> I'm unable to shutdown my system via normal means. The system
> completes the shutdown process, all hardware lights are off, but then
> somehow it restarts.
>
Processing commands for cont...@bugs.debian.org:
> tags 691902 + moreinfo
Bug #691902 [linux-image-3.2.0-3-amd64] Unable to shutdown Debian Wheezy via
normal means
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
691902: http://bugs.debian.o
Please beg my pardon for multiple email copies: an error on my side.
Jaakov.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1351672824.91441.9458.54...@saddam4.ramb
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom th
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom th
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom the
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom the
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom th
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom th
Thank you for a fast reply.
Can you provide a kernel log for a successful boot (/var/log/dmesg.log)?
Attached.
'grave' would mean the package is broken for most users, which it isn't.
The official description of grave from
http://www.debian.org/Bugs/Developer.html
does not say for whom th
Package: linux-image-3.2.0-3-amd64
Severity: Important
Dear maintainters,
I'm unable to shutdown my system via normal means. The system
completes the shutdown process, all hardware lights are off, but then
somehow it restarts.
Selecting "Shutdown" from Gnome, issuing "shutdown -h now", "poweroff"
26 matches
Mail list logo