Bug#445957: linux-source-2.6.22: creating a snapshot hangs the system
On Tue, Oct 09, 2007 at 01:04:33PM +0200, Thomas Kotzian wrote:
Package: linux-source-2.6.22
Version: 2.6.22-4
Severity: grave
Justification: causes non-serious data loss
This bug does not appear to directly cause data loss.
when i create a snapshot with for example
lvcreate -s -L 3g -n snap_var_lv /dev/system_vg/var_lv
the command hangs, is uninterruptable and the system is frozen.
I'm using 2.6.22 and frequently use LVM snapshotting. This bug is not
reproducible for me.
tested with linux-image-2.6.22-amd64, linux-image-2.6.22-486 and some
systems linux-image-2.6.21-{amd64,486} works perfectly.
It's not clear to me from this comment whether you tested each of these
kernels on the same system. How much free space do you have on the VG where
you're snapshotting?
Are you using lvm version 1 or 2? I distantly recall an issue of this sort
occurring when trying to snapshot a version 1 LV with current tools, but I'm
not sure if the current userspace tools in unstable support version 1
metadata at all.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#419475: linux-image-2.6.18-4-k7: erroneous behaviour of Realtek 8139, network practically unusable
Processing commands for [EMAIL PROTECTED]: reassign 419475 linux-2.6 Bug#419475: linux-image-2.6.18-4-k7: erroneous behaviour of Realtek 8139, network practically unusable Warning: Unknown package 'linux-image-2.6.18-4-k7' Bug reassigned from package `linux-image-2.6.18-4-k7' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444395: marked as done (linux-2.6 [etch] - w83793 support)
Your message dated Wed, 10 Oct 2007 07:56:16 + with message-id [EMAIL PROTECTED] and subject line Bug#444395: fixed in fai-kernels 1.17+etch.16 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-14 Severity: important Please add support for w83793. The sources from .22 builds fine. Bastian -- The sight of death frightens them [Earthers]. -- Kras the Klingon, Friday's Child, stardate 3497.2 ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.16 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.16.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.16.dsc fai-kernels_1.17+etch.16.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.16.tar.gz fai-kernels_1.17+etch.16_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.16_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 9 Oct 2007 21:30:29 -0600 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.16 Distribution: stable Urgency: high Maintainer: Holger Levsen [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 444395 Changes: fai-kernels (1.17+etch.16) stable; urgency=high . * Non-maintainer upload. * Rebuild against linux-source-2.6.18 (2.6.18.dfsg.1-16) [ Bastian Blank ] * Add support for w83793 sensor chips. (closes: #444395) . [ dann frazier ] * Merge in changes from 2.6.18.dfsg.1-13etch4. Files: 2854c0ab372345bf63bada421fcc46d3 725 admin extra fai-kernels_1.17+etch.16.dsc 45676a316e6f557a3dc519ea217eb0d3 54676 admin extra fai-kernels_1.17+etch.16.tar.gz e2aa7070a57afb84096e4a0564bef439 5501830 admin extra fai-kernels_1.17+etch.16_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHDFlMhuANDBmkLRkRAlUJAJsEy4rKlHJFLkKBJmP4lxgIKHR89wCfbreO MhH3HGaXkszbi0IuKJjLuNk= =xAVR -END PGP SIGNATURE- ---End Message---
Bug#444395: marked as done (linux-2.6 [etch] - w83793 support)
Your message dated Wed, 10 Oct 2007 07:56:17 + with message-id [EMAIL PROTECTED] and subject line Bug#444395: fixed in user-mode-linux 2.6.18-1um-2etch.16 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-2.6 Version: 2.6.18.dfsg.1-14 Severity: important Please add support for w83793. The sources from .22 builds fine. Bastian -- The sight of death frightens them [Earthers]. -- Kras the Klingon, Friday's Child, stardate 3497.2 ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.16 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.16.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.16.diff.gz user-mode-linux_2.6.18-1um-2etch.16.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.16.dsc user-mode-linux_2.6.18-1um-2etch.16_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.16_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 9 Oct 2007 22:07:16 -0600 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.16 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: user-mode-linux - User-mode Linux (kernel) Closes: 444395 Changes: user-mode-linux (2.6.18-1um-2etch.16) stable; urgency=high . * Non-maintainer upload. * Rebuild against linux-source-2.6.18 (2.6.18.dfsg.1-16) [ Bastian Blank ] * Add support for w83793 sensor chips. (closes: #444395) . [ dann frazier ] * Merge in changes from 2.6.18.dfsg.1-13etch4. Files: 5ed1db19ca108a715e9abf0b5f2809ef 877 misc extra user-mode-linux_2.6.18-1um-2etch.16.dsc ff13cd64edd45799e5014f1fac8085dc 14674 misc extra user-mode-linux_2.6.18-1um-2etch.16.diff.gz 1c230708f9d80f6dd316265d4a98e766 25581646 misc extra user-mode-linux_2.6.18-1um-2etch.16_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHDFlehuANDBmkLRkRAs63AJwMGvlUFSplVRQNEBDZX/22+aK53QCgl0VK dfvzsgWVUwLbNvDZn26WqV0= =jT3t -END PGP SIGNATURE- ---End Message---
Bug#445957: linux-source-2.6.22: creating a snapshot hangs the system
Thank you very much, I was wondering the same thing since I posted it. I'm 17 and a newbie so I wasn't very sure. I have some doubts regarding this stuff, but this isn't the place to discuss them. Hopefully this bug will soon be history. -- Sisir Koppaka 1st Year Undergraduate Student Dept. of Mechanical Engineering IIT Kharagpur India
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reassign 412698 kqemu Bug#412698: should depend on kqemu-common Bug reassigned from package `kqemu-modules-2.6.18-4-686' to `kqemu'. reassign 418516 kqemu Bug#418516: /dev/kqemu is not created automatically when loading module kqemu Bug reassigned from package `kqemu-modules-2.6.18-4-686' to `kqemu'. close 434060 Bug#434060: kqemu-modules-2.6-686: Out of sync with kernel version 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Jacopo [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cannot install kernel headers package
On martedì 9 ottobre 2007, Thiemo Seufer wrote: My question is: how can I correctly make a cross-system (Ubuntu/Debian) kernel compilation/installation? Any help will be highly appreciated! Build inside an etch chroot. Thiemo Do you mean I have to make a local copy of the whole Debian file system on the Ubuntu machine and compile there? Many thanks, Federico
Bug#446073: CVE-2007-3843 possible spoofing of CIFS traffic
Package: linux-2.6 Severity: important Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) id was published for linux-2.6. CVE-2007-3843[0]: | The Linux kernel before 2.6.23-rc1 checks the wrong global variable | for the CIFS sec mount option, which might allow remote attackers to | spoof CIFS network traffic that the client configured for security | signatures, as demonstrated by lack of signing despite sec=ntlmv2i in | a SetupAndX request. If you fix this vulnerability please also include the CVE id in your changelog entry. For further information: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3843 Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpn3YECGy5xd.pgp Description: PGP signature
Bug#405232: include rt2400/rt2500/rt2570/rt2x00
What is the status of this, should/can I include the drivers into linux-modules-extra-2.6 now? Regards, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446148: linux-image-2.6.18-5-xen-amd64: domU panic with swiotlb=force
Package: linux-image-2.6.18-5-xen-amd64
Version: 2.6.18.dfsg.1-13etch4
Severity: normal
Using swiotlb=force panics the kernel realy quick:
Bootdata ok (command line is root=/dev/sda1 ro swiotlb=force)
Linux version 2.6.18-5-xen-amd64 (Debian 2.6.18.dfsg.1-13etch4)
([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Tue Oct 2 21:48:12 UTC 2007
BIOS-provided physical RAM map:
Xen: - 35a0 (usable)
No mptable found.
Built 1 zonelists. Total pages: 219648
Kernel command line: root=/dev/sda1 ro swiotlb=force
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 1800.061 MHz processor.
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
--- [cut here ] - [please bite here ] -
Kernel BUG at lib/../arch/i386/kernel/swiotlb.c:162
invalid opcode: [1] SMP
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.18-5-xen-amd64 #1
RIP: e030:[8030c7f8] [8030c7f8]
swiotlb_init_with_default_size+0xa0/0x19e
RSP: e02b:804dbf40 EFLAGS: 00010282
RAX: fff4 RBX: RCX: 0006
RDX: ff578000 RSI: RDI:
RBP: 0400 R08: 1000 R09: 80522040
R10: R11: R12:
R13: R14: R15:
FS: () GS:804c4000()
knlGS:
CS: e033 DS: ES:
Process swapper (pid: 0, threadinfo 804da000, task
8044bce0)
Stack: 0800
8026e280
804ecf2a 0800
Call Trace:
[8026e280] pci_swiotlb_init+0x9/0x2d
[804ecf2a] mem_init+0x5e/0x233
[804e36ea] start_kernel+0x189/0x21a
[804e320d] _sinittext+0x20d/0x213
Code: 0f 0b 68 e1 36 41 80 c2 a2 00 48 83 eb 80 48 8b 05 bb 20 24
RIP [8030c7f8]
swiotlb_init_with_default_size+0xa0/0x19e
RSP 804dbf40
0Kernel panic - not syncing: Attempted to kill the idle task!
I was hoping this would fix the problem that usblp cannot allocate write
buffers for an USB connected printer.
But alas, this doesn't even produce a working domU.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-xen-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-5-xen-amd64 depends on:
ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii initramf 0.85h tools for generating an initramfs
ii linux-mo 2.6.18.dfsg.1-13etch4 Linux 2.6.18 modules on AMD64
linux-image-2.6.18-5-xen-amd64 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#446028: ITP: tg3dfsg -- firmware free Broadcom Tigon3 network driver
Faidon Liambotis wrote: Robert Edmonds wrote: Any modification to the tg3 driver to produce a GR 2006-004 compliant driver would have to diverge from the kernel team's patch acceptance guidelines[0] since upstream is intransigent[1] on making tg3 firmware-free or firmware-optional. The kernel team does not appear to be interested in maintaining such a driver, and it appears future linux kernel source packages will be patched[2] to simply remove the blobs of firmware (I don't know why the driver isn't simply removed entirely since the result does not compile). This seems totally inappropriate. If the driver includes non-free firmwares these should be removed or split up from the driver source, not remove the driver entirely. If what you say is right, the driver *works* for most of the hardware without non-free blobs. Therefore, I can't understand how removing the driver serves our users. That is why I said appear, since I hope that the kernel team has plans for the driver beyond simply eliding it. (I'd like to point out that the equivalent FreeBSD if_bge driver has no firmware blobs.) Any rationale behind that decision? I feel like I'm arguing for something completely obvious... The only rationale for removing the *firmware* is compliance with GR 2006-004... -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Bug#446028: ITP: tg3dfsg -- firmware free Broadcom Tigon3 network driver
Robert Edmonds wrote: Any modification to the tg3 driver to produce a GR 2006-004 compliant driver would have to diverge from the kernel team's patch acceptance guidelines[0] since upstream is intransigent[1] on making tg3 firmware-free or firmware-optional. The kernel team does not appear to be interested in maintaining such a driver, and it appears future linux kernel source packages will be patched[2] to simply remove the blobs of firmware (I don't know why the driver isn't simply removed entirely since the result does not compile). This seems totally inappropriate. If the driver includes non-free firmwares these should be removed or split up from the driver source, not remove the driver entirely. If what you say is right, the driver *works* for most of the hardware without non-free blobs. Therefore, I can't understand how removing the driver serves our users. Any rationale behind that decision? I feel like I'm arguing for something completely obvious... Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: LET:account,password,shop,did you forget?,are you forget?,why are are forget?,damn you forget}
http://{_clean_domains}
Review our values below to inquire how much you can save.
Our reduction:
VI- $1.88 -AGRA SOFT
VIA- per pill $1.79 -GRA
CIAL- $2.69 -IS
CI- $3.93 -ALIS SOFT
And thats not all. Full list on
http://{_clean_domains}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293718: LET:account,password,shop,did you forget?,are you forget?,why are are forget?,damn you forget}
http://{_clean_domains}
Look at our prices below to see how much you can save.
Our reduction:
CIAL- $2.69 -IS
VIAG- per pill $1.79 -RA
VIAG- 1.88$ per pill -RA SOFT
CIA- $3.93 per pill -LIS SOFT
And thats not all. More on
http://{_clean_domains}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#446028: ITP: tg3dfsg -- firmware free Broadcom Tigon3 network driver
On Thu, Oct 11, 2007 at 12:44:54AM +0200, Bastian Blank wrote:
None, at least from my point of view. Just someone have to do it. (See
[EMAIL PROTECTED] on d-kernel.)
The attached patch should apply on the pruned version.
Bastian
--
We have found all life forms in the galaxy are capable of superior
development.
-- Kirk, The Gamesters of Triskelion, stardate 3211.7
--- tg3.c.orig 2007-10-10 16:13:59.0 +0200
+++ tg3.c 2007-10-11 01:01:49.0 +0200
@@ -5124,11 +5124,6 @@
}
-#define RX_CPU_SCRATCH_BASE0x3
-#define RX_CPU_SCRATCH_SIZE0x04000
-#define TX_CPU_SCRATCH_BASE0x34000
-#define TX_CPU_SCRATCH_SIZE0x04000
-
/* tp-lock is held. */
static int tg3_halt_cpu(struct tg3 *tp, u32 offset)
{
@@ -5177,205 +5172,6 @@
return 0;
}
-struct fw_info {
- unsigned int text_base;
- unsigned int text_len;
- const u32 *text_data;
- unsigned int rodata_base;
- unsigned int rodata_len;
- const u32 *rodata_data;
- unsigned int data_base;
- unsigned int data_len;
- const u32 *data_data;
-};
-
-/* tp-lock is held. */
-static int tg3_load_firmware_cpu(struct tg3 *tp, u32 cpu_base, u32
cpu_scratch_base,
-int cpu_scratch_size, struct fw_info *info)
-{
- int err, lock_err, i;
- void (*write_op)(struct tg3 *, u32, u32);
-
- if (cpu_base == TX_CPU_BASE
- (tp-tg3_flags2 TG3_FLG2_5705_PLUS)) {
- printk(KERN_ERR PFX tg3_load_firmware_cpu: Trying to load
- TX cpu firmware on %s which is 5705.\n,
- tp-dev-name);
- return -EINVAL;
- }
-
- if (tp-tg3_flags2 TG3_FLG2_5705_PLUS)
- write_op = tg3_write_mem;
- else
- write_op = tg3_write_indirect_reg32;
-
- /* It is possible that bootcode is still loading at this point.
-* Get the nvram lock first before halting the cpu.
-*/
- lock_err = tg3_nvram_lock(tp);
- err = tg3_halt_cpu(tp, cpu_base);
- if (!lock_err)
- tg3_nvram_unlock(tp);
- if (err)
- goto out;
-
- for (i = 0; i cpu_scratch_size; i += sizeof(u32))
- write_op(tp, cpu_scratch_base + i, 0);
- tw32(cpu_base + CPU_STATE, 0x);
- tw32(cpu_base + CPU_MODE, tr32(cpu_base+CPU_MODE)|CPU_MODE_HALT);
- for (i = 0; i (info-text_len / sizeof(u32)); i++)
- write_op(tp, (cpu_scratch_base +
- (info-text_base 0x) +
- (i * sizeof(u32))),
-(info-text_data ?
- info-text_data[i] : 0));
- for (i = 0; i (info-rodata_len / sizeof(u32)); i++)
- write_op(tp, (cpu_scratch_base +
- (info-rodata_base 0x) +
- (i * sizeof(u32))),
-(info-rodata_data ?
- info-rodata_data[i] : 0));
- for (i = 0; i (info-data_len / sizeof(u32)); i++)
- write_op(tp, (cpu_scratch_base +
- (info-data_base 0x) +
- (i * sizeof(u32))),
-(info-data_data ?
- info-data_data[i] : 0));
-
- err = 0;
-
-out:
- return err;
-}
-
-/* tp-lock is held. */
-static int tg3_load_5701_a0_firmware_fix(struct tg3 *tp)
-{
- struct fw_info info;
- int err, i;
-
- info.text_base = TG3_FW_TEXT_ADDR;
- info.text_len = TG3_FW_TEXT_LEN;
- info.text_data = tg3FwText[0];
- info.rodata_base = TG3_FW_RODATA_ADDR;
- info.rodata_len = TG3_FW_RODATA_LEN;
- info.rodata_data = tg3FwRodata[0];
- info.data_base = TG3_FW_DATA_ADDR;
- info.data_len = TG3_FW_DATA_LEN;
- info.data_data = NULL;
-
- err = tg3_load_firmware_cpu(tp, RX_CPU_BASE,
- RX_CPU_SCRATCH_BASE, RX_CPU_SCRATCH_SIZE,
- info);
- if (err)
- return err;
-
- err = tg3_load_firmware_cpu(tp, TX_CPU_BASE,
- TX_CPU_SCRATCH_BASE, TX_CPU_SCRATCH_SIZE,
- info);
- if (err)
- return err;
-
- /* Now startup only the RX cpu. */
- tw32(RX_CPU_BASE + CPU_STATE, 0x);
- tw32_f(RX_CPU_BASE + CPU_PC,TG3_FW_TEXT_ADDR);
-
- for (i = 0; i 5; i++) {
- if (tr32(RX_CPU_BASE + CPU_PC) == TG3_FW_TEXT_ADDR)
- break;
- tw32(RX_CPU_BASE + CPU_STATE, 0x);
- tw32(RX_CPU_BASE + CPU_MODE, CPU_MODE_HALT);
- tw32_f(RX_CPU_BASE + CPU_PC,TG3_FW_TEXT_ADDR);
- udelay(1000);
- }
- if (i = 5) {
- printk(KERN_ERR PFX tg3_load_firmware fails for %s
- to set
Re: Bug#446028: ITP: tg3dfsg -- firmware free Broadcom Tigon3 network driver
On Thu, Oct 11, 2007 at 01:04:56AM +0200, Bastian Blank wrote: On Thu, Oct 11, 2007 at 12:44:54AM +0200, Bastian Blank wrote: None, at least from my point of view. Just someone have to do it. (See [EMAIL PROTECTED] on d-kernel.) The attached patch should apply on the pruned version. Bastian where is the request_firmware() usage? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#446028: ITP: tg3dfsg -- firmware free Broadcom Tigon3 network driver
On 2007-10-10, Bastian Blank [EMAIL PROTECTED] wrote:
The attached patch should apply on the pruned version.
Applies but does not compile:
tg3.c: In function âtg3_reset_hwâ:
tg3.c:5399: error: âTG3_TSO5_FW_TEXT_LENâ undeclared (first use in this
function)
tg3.c:5399: error: (Each undeclared identifier is reported only once
tg3.c:5399: error: for each function it appears in.)
tg3.c:5400: error: âTG3_TSO5_FW_RODATA_LENâ undeclared (first use in this
function)
tg3.c:5401: error: âTG3_TSO5_FW_DATA_LENâ undeclared (first use in this
function)
tg3.c:5402: error: âTG3_TSO5_FW_SBSS_LENâ undeclared (first use in this
function)
tg3.c:5403: error: âTG3_TSO5_FW_BSS_LENâ undeclared (first use in this
function)
The offending code is:
/* Initialize MBUF/DESC pool. */
if (tp-tg3_flags2 TG3_FLG2_5750_PLUS) {
/* Do nothing. */
} else if (GET_ASIC_REV(tp-pci_chip_rev_id) != ASIC_REV_5705) {
[...]
}
else if (tp-tg3_flags2 TG3_FLG2_TSO_CAPABLE) {
int fw_len;
fw_len = (TG3_TSO5_FW_TEXT_LEN +
TG3_TSO5_FW_RODATA_LEN +
TG3_TSO5_FW_DATA_LEN +
TG3_TSO5_FW_SBSS_LEN +
TG3_TSO5_FW_BSS_LEN);
fw_len = (fw_len + (0x80 - 1)) ~(0x80 - 1);
tw32(BUFMGR_MB_POOL_ADDR,
NIC_SRAM_MBUF_POOL_BASE5705 + fw_len);
tw32(BUFMGR_MB_POOL_SIZE,
NIC_SRAM_MBUF_POOL_SIZE5705 - fw_len - 0xa00);
}
--
Robert Edmonds
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
